Browse help topics

Connect Zapier or Make

In this article: Turn a compliance event into a row, a task, or a message in whatever you already use.

Applies to Pro plan

Neither needs code. Both work the same way: they give you a URL, you paste it into a webhook endpoint here, and events start arriving as triggers you can build on.

Zapier

  1. Create a Catch Hook trigger

    Create a Zap with Webhooks by Zapier → Catch Hook as the trigger. Zapier gives you a URL.

  2. Add the URL here

    In TrackMyVendor: Settings → Integrations → Webhook Endpoints. Paste the URL, label it "Zapier", tick the events you want, save.

  3. Send it a real event

    Back in Zapier, test the trigger. Cause a real event — add a contractor if you subscribed to contractor.created — so Zapier sees the actual payload shape rather than a guess.

  4. Build the action

    Add your action: a Google Sheets row, a Slack message, an Asana task, an email.

Make

Identical shape: a Custom webhook module gives you a URL, you add it here, and you run the scenario once against a real event so Make learns the data structure.

Make is usually the better choice when one event needs to fan out into several actions, or when you want conditional routing — it's more capable at branching and cheaper at volume.

Worth building

  • A shared sheet that mirrors compliance status, for people who won't log in.
  • A task in your PM tool whenever a contractor turns Non-Compliant.
  • A site-access check — flag it when someone scheduled for tomorrow has an expired certificate.
  • An accounting nudge on contractor.w9_missing, before year-end rather than during it.

Tip

Start with one event and one action. Subscribing to all five on day one produces a lot of traffic and makes a broken scenario much harder to diagnose.

Longer walkthroughs: Zapier · Make

Related articles

Didn't find what you were looking for?

Send us the question — a person answers, usually the same working day.

Contact support