Importing Approved Vendors from Zip

What it does

When a vendor request in Zip reaches the status you've configured, the integration adds that vendor as a system in your MineOS inventory — matching it to an existing catalog entry where possible, or creating a new one if no match is found.
If the vendor already exists in your inventory, you're notified instead of a duplicate being created.
You'll get a Slack message and/or email letting you know whether a new system was added, a match already existed, or something went wrong.
Optionally, you can have the integration pull in additional vendor, request, or purchase order details from Zip to improve matching accuracy.

Connections you need to configure

The only connection you need to set up is Slack, via an Incoming Webhook URL that notifications get posted to. Leave this unset if you don't want Slack notifications.

The integration also relies on a few other connections behind the scenes. These are pre-configured and don't require any setup on your end.

There's no separate on/off toggle for notifications — you enable a channel simply by filling in its field:

Add a Slack webhook URL to enable Slack notifications.
Add a "To Email" address to enable email notifications.
Leave either field blank to skip that channel.

Configuration variables reference

Zip connection

Key	Default	Notes
`Zip Base URL`		Base URL for Zip API calls.
`Zip API Key`	(empty)	Your Zip API key.
`ZipHQ Event`	`Request Status`	The Zip event that should trigger this integration.

Notifications

Key	Default	Notes
`Slack Connection`	(placeholder)	Incoming Webhook URL. Leave as-is to disable Slack notifications.
`To Email`	`Email Address to Notify`	Set to a real address to enable email notifications; leave as-is to disable them.

Notifications

Key	Default	Notes
`Attributes`	3 entries: `Vendor Attributes`, `Request Attributes`, `Purchase Order Attributes` (all blank)	Optional: comma-separated attribute names from Zip you’d like considered when matching a vendor to your catalog.

Setting up the webhook in ZipHQ

Zip's webhook and API settings live within your organization's own Zip account (log into Zip, click the ? icon, then API Documentation), so exact steps may vary by plan. At a high level:

Get the webhook URL for this integration — provided once it's deployed.
Register that URL in Zip as a webhook endpoint, subscribed to the event that fires when a request's status changes (commonly a "Request Status" style event).
Confirm the event name Zip sends matches the ZipHQ Event configuration variable (default: Request Status) — update the variable if your Zip workspace uses a different name.
Get a Zip API key with read access to requests, vendors, and purchase orders, and enter it as Zip API Key.
Test with a request that has a vendor attached to confirm notifications come through as expected.

If you can't locate the webhook management screen in your Zip account, Zip's Help Center (docs.ziphq.com) has an Integrations section pointing to the gated API docs for your plan.

Quick configuration checklist

[ ] Set Zip Base URL and Zip API Key
[ ] Confirm/adjust ZipHQ Event to match what Zip actually sends
[ ] Register the webhook URL in Zip and subscribe it to the right event
[ ] Set To Email and/or the Slack Connection webhook URL (leave the other unset if you only want one channel)
[ ] Fill in Attributes if you want extra vendor/request/PO fields considered
[ ] Send a test request through and confirm the Slack/email notification looks right