How do I connect TrackMyVendor to Make for contractor compliance?

In Make, create a new scenario and add a Webhooks → Custom webhook module as the trigger. Make generates a unique webhook URL. In TrackMyVendor's Settings → Integrations → Webhook Endpoints, paste the Make URL and select which contractor compliance events to subscribe to. Click 'Determine data structure' in Make, then trigger a test event from TrackMyVendor — Make auto-maps every payload field. Add action modules (Slack, Gmail, Google Sheets, etc.) and activate the scenario.

What contractor compliance events can I use in Make scenarios?

TrackMyVendor sends five event types: contractor.created (new contractor added), contractor.compliance_changed (status changes), contractor.license_expiring (license entering a 90/60/30/7-day window), contractor.coi_expiring (COI insurance expiration alert), and contractor.w9_missing (W-9 no longer on file). Use Make's Filter module to route different events to different action modules within the same scenario.

How is the Make integration different from Zapier for contractor compliance?

Both use TrackMyVendor's outbound webhooks as the trigger. The main difference is the automation builder: Zapier is step-by-step (one trigger → one action per Zap), while Make's visual canvas lets you branch a single webhook into multiple parallel paths — for example, one webhook firing both a Slack message and a Google Sheets row update in the same scenario. Make's Filter module is also more powerful for routing different event types within a single scenario.

Make contractor compliance integration

Make Contractor Compliance Integration (formerly Integromat)

Build Make scenarios that route COI expiry, license lapses, and W-9 alerts to any tool your team uses

TrackMyVendor monitors subcontractor COIs, trade licenses, and W-9 documents and sends a webhook every time something changes or approaches expiration. Connect it to Make's visual canvas and route each compliance event to Slack, Gmail, Google Sheets, Monday.com, and 1,500+ apps — with branching logic that Zapier can't match.

Start free — build your first scenario in 10 minutes Step-by-step setup guide →

No credit card required · Free for first 25 subs

Make scenario blueprint — contractor compliance automation

This is the recommended scenario structure for teams that want to handle all five TrackMyVendor events in a single Make scenario with branching logic.

TrackMyVendor → Make Scenario Blueprint

TRIGGER Webhooks → Custom webhook (receives all TrackMyVendor events)

│

ROUTER Tools → Router (branches by event type)

├──

contractor.coi_expiring → Slack: post to #compliance

├──

contractor.license_expiring → Asana: create task with due date

├──

contractor.w9_missing → Gmail: send reminder to accounting

├──

contractor.created → Google Sheets: append to roster

└──

contractor.compliance_changed → Monday.com: update board status

Unlike Zapier, Make's router module lets you handle all five event types in a single scenario — one webhook endpoint in TrackMyVendor, one scenario in Make, five parallel action paths.

Make scenario recipes for contractor compliance

Each of these is a standalone scenario. Start with the one that matches your biggest current pain point.

contractor.coi_expiring Slack

Post to #compliance with vendor name, expiration date, and days remaining

Your PM team sees expiring COIs in the channel where they already work — no dashboard check required.

Fields: vendor_name · expiration_date · days_left · window

contractor.license_expiring Asana + Slack (two modules, one scenario)

Create an Asana task with the expiration date as due date AND post a Slack alert — two actions from one webhook

Make's canvas lets you add two action modules after the same trigger. One webhook from TrackMyVendor fires both.

Fields: vendor_name · expiration_date · days_left · window

contractor.w9_missing Gmail

Send a formatted reminder email to your accounting team with vendor name and a link to TrackMyVendor

W-9 gaps create IRS exposure at year-end. Routing the alert directly to accounting ensures the right person acts on it.

Fields: vendor_id · vendor_name

contractor.created Google Sheets + HubSpot (parallel modules)

Append a row to your contractor master roster AND create a HubSpot contact — simultaneously

Make can write to two apps in parallel from one trigger. No need for two separate scenarios.

Fields: vendor_name · vendor_id · organization_id · created_at

contractor.compliance_changed Monday.com

Update the sub's board item status column and add a note showing which document triggered the change

Project boards reflect compliance state in real time — project managers see hold status without asking the compliance team.

Fields: vendor_name · from · to

What Make receives from TrackMyVendor

When you click "Determine data structure" in Make and trigger a test event from TrackMyVendor, Make auto-maps every field as a draggable variable. Here is a license expiration payload:

{
  "event": "contractor.license_expiring",
  "created_at": "2026-05-08T14:00:00Z",
  "data": {
    "vendor_id": 42,
    "vendor_name": "Apex Electrical LLC",
    "organization_id": 7,
    "expiration_date": "2026-06-15",
    "days_left": 38,
    "window": "60d"
  }
}

Make tip: use a Filter module to branch by event type

Add a Filter module between the webhook and each action. Set the condition to event = contractor.coi_expiring for one branch and event = contractor.license_expiring for another. This lets one webhook endpoint in TrackMyVendor drive multiple parallel paths in a single scenario — one of Make's key advantages over Zapier for compliance workflows.

Frequently asked questions

How do I connect TrackMyVendor to Make (Integromat)?

In Make, create a new scenario and add a Webhooks → Custom webhook module as the trigger. Make generates a unique webhook URL. In TrackMyVendor's Settings → Integrations → Webhook Endpoints, paste the URL and select which events to subscribe to. Click 'Determine data structure' in Make, trigger a test event from TrackMyVendor, and Make auto-maps every field. Add action modules and activate the scenario.

How is Make different from Zapier for Integromat subcontractor compliance?

Both use TrackMyVendor's webhooks as the trigger. The key difference is Make's visual canvas: a single scenario can branch one webhook into multiple parallel action paths using a Router module — for example, posting to Slack AND creating a Google Sheets row from one event. Zapier handles this with multi-step Zaps on paid plans; Make's router is available on all plans.

Does TrackMyVendor have a native Make app?

No. TrackMyVendor uses standard outbound webhooks, which connect to Make through the built-in Webhooks → Custom webhook module. This is available on all Make plans including the free tier.

What Make plan do I need for contractor compliance scenarios?

Make's free tier includes 1,000 operations per month. Each webhook delivery counts as one operation, and each action module counts as another. A scenario with one webhook trigger and two action modules uses 3 operations per event. For teams with 50+ subs getting weekly compliance events, the Core plan ($10.59/month, 10,000 operations) is typically sufficient.

Can I share my Make contractor compliance scenario blueprint with my team?

Yes. Make lets you export a scenario as a JSON blueprint file that teammates can import into their own Make accounts. You can also share scenario templates via Make's community. If you build a useful TrackMyVendor compliance scenario, the Make community forum is a good place to publish it — Make users actively search for compliance and document management blueprints.

Your Make scenario is 10 minutes away

TrackMyVendor handles the compliance monitoring. Make routes every event to exactly where your team needs it.

Start free — first 25 subs included Step-by-step setup guide

No credit card required

Make Contractor Compliance Integration (formerly Integromat)

Build Make scenarios that route COI expiry, license lapses, and W-9 alerts to any tool your team uses

Make scenario blueprint — contractor compliance automation

Make scenario recipes for contractor compliance

What Make receives from TrackMyVendor

Frequently asked questions

Your Make scenario is 10 minutes away

Explore More

Contractor Compliance Automation

Zapier Contractor Compliance

Alerts and Reminders

AI COI Parsing

License Verification

Vendor Self-Service

General Contractor Compliance Software

Plans & Pricing