Integration Guide

Make Integration for Contractor Compliance Automation

Make contractor compliance automation lets TrackMyVendor send subcontractor COI expiration alerts, license monitoring events, and W-9 notifications to any tool your team uses — built visually, no developer needed. Make's drag-and-drop scenario builder is the fastest way to set up separate workflows for each event type. Setup takes about 10 minutes.

What you can automate

Post a Slack message when a sub's COI is about to expire
Get notified when a new subcontractor doesn't have a W-9 on file
Trigger a license renewal alert at 30 days before expiration
Update a Google Sheet row when a sub's compliance status changes
Route COI, license, and W-9 events to separate Slack channels
Create a Monday.com board item when a sub's license or COI is expiring
Add a HubSpot note or update a contact property when compliance status drops

Before you start

  • 1 A TrackMyVendor account with owner access
  • 2 A Make account (free tier supports webhook scenarios)
1

Create a new scenario with a Custom Webhook trigger

In Make, click Create a new scenario. When prompted to add a first module, search for Webhooks and select Custom webhook.

Make setup path:

+ Add module → Webhooks → Custom webhook → Add → Name it → Save

After you click Save, Make generates a unique webhook URL and shows it on the module. Copy it.

2

Add the endpoint in TrackMyVendor

In TrackMyVendor, go to Settings → Integrations → Webhook Endpoints and click Add Endpoint. This is the license monitoring webhook endpoint that will send contractor compliance events to Make.

URL Paste the Make webhook URL
Label Something like "Make — COI to Slack"
Events Select contractor compliance events to receive — COI expiration alerts, license monitoring, W-9 missing, etc.

Save the endpoint. TrackMyVendor shows the signing secret once — copy it if you want to verify signatures.

3

Let Make detect the data structure

Back in Make, click Determine data structure on the webhook module. Make waits to receive your first test event. Now trigger a real event from TrackMyVendor — the easiest way is to add a new contractor, which fires contractor.created immediately.

Make receives the payload and auto-maps every field. You'll see the JSON structure appear:

{
  "event": "contractor.created",
  "created_at": "2026-05-08T14:00:00Z",
  "data": {
    "vendor_id": 42,
    "vendor_name": "Apex Electrical LLC",
    "organization_id": 7
  }
}

Make maps data.vendor_name, data.days_left, etc. as drag-and-drop variables in your action modules.

4

Add action modules

Click the + after the webhook module to add an action. Popular choices for compliance workflows:

Slack

Send a message to #compliance with contractor name and days until expiry

Gmail

Email your team a summary when contractor.w9_missing fires

Google Sheets

Append a row to a compliance log sheet for every event

Monday.com

Create a board item with expiration date pre-filled when a COI or license alert fires

HubSpot

Add a note to the contractor's contact or update a custom compliance_status property

Tip: filter by event type

Add a Filter module between the webhook and your action. Set the condition to event = contractor.coi_expiring so each scenario only handles one event type. Run separate scenarios for different events.

5

Save and activate the scenario

Click Save, then toggle the scenario on using the switch in the bottom left. The scenario is now live — every qualifying event from TrackMyVendor will run it in real time.

Make's free tier includes 1,000 operations/month. Each webhook delivery counts as one operation. For high-volume teams, the Core plan ($10.59/month) provides 10,000 operations.

Event reference

Event When it fires Key payload fields
contractor.created A new contractor is added to your roster vendor_id, vendor_name
contractor.compliance_changed Overall compliance status changes (pass ↔ fail) vendor_name, from, to
contractor.license_expiring License expiration enters an alert window (90/60/30/7d) vendor_name, expiration_date, days_left, window
contractor.coi_expiring COI/insurance expiration enters an alert window vendor_name, expiration_date, days_left, window
contractor.w9_missing A contractor who had a W-9 on file no longer does vendor_id, vendor_name

Verifying the webhook signature (optional)

Every request includes an X-TMV-Signature header. In Make, add a Webhooks → Webhook response module or a Tools → Set variable module before your action, using the built-in HMAC functions:

Signature format:

X-TMV-Signature: t=<unix_timestamp>,sha256=<hmac_hex>

HMAC is computed as: HMAC-SHA256(signing_secret, "{timestamp}.{raw_body}")

Frequently asked questions

Does TrackMyVendor have a native Make app?
No — TrackMyVendor uses standard webhooks, which connect through Make's built-in Webhooks → Custom webhook module. Available on all plans including the free tier. No native app required.
What contractor compliance events can I send to Make?
Five event types: contractor.created, contractor.compliance_changed, contractor.license_expiring, contractor.coi_expiring, and contractor.w9_missing. Each endpoint can subscribe to any combination.
Do I need a paid Make plan?
No. Make's free plan includes 1,000 operations/month and fully supports webhook scenarios. Each incoming webhook from TrackMyVendor = one operation. For high-volume teams, the Core plan (~$10.59/mo) provides 10,000 operations.
Can I route different compliance events to different scenarios?
Yes — recommended approach. Create a separate scenario per event type and add a Filter module to match the event name. One scenario handles contractor.coi_expiring → Slack; another handles contractor.w9_missing → Gmail. Keeps each scenario simple and easy to debug.
Can Make trigger when a contractor license lapses or gets revoked?
Yes. Subscribe to contractor.license_expiring for advance warning at 90/60/30/7-day windows. Subscribe to contractor.compliance_changed for instant notification when TrackMyVendor's daily state database sync catches a mid-project license revocation.
What happens if a scenario fails — will I miss a compliance alert?
If a scenario fails, Make logs it in your history so you can replay it manually. Note that each replay counts as one operation against your monthly limit. On the TrackMyVendor side, the same event fires again at each threshold (90/60/30/7 days) — so a failure at 30 days will retry naturally at 7 days.

"We run three separate scenarios — COI alerts to #compliance, license warnings to #jobsite, W-9 gaps to the office manager. Make's visual builder made each one straightforward to set up."

Office Manager, Dallas TX general contracting firm — 28 subcontractors

Prefer Zapier?

Zapier's 6,000+ app library is the fastest way to connect compliance alerts to the tools you use.

Zapier guide →

Routing alerts to Slack?

See our guide for the specific Slack action setup and message templates.

Slack guide →

Using Microsoft Teams?

Post compliance alerts to Teams via Power Automate — no extra subscription needed.

Teams guide →

Don't have a TrackMyVendor account yet?

Track your first 25 subs free — no credit card required.

Start free →

Already have an account?

Add your Make webhook URL as an endpoint in Settings → Integrations.

Open Integrations Settings