Make integration: send ZenMode events to Make
ZenMode POSTs six CRM events to a Make custom webhook URL you paste into settings — outbound only, and there is no ZenMode module in Make.
Verified against the product on September 3, 2026 · Updated · Set up in /dashboard/settings
What this integration is
There is no ZenMode app or module in Make's library — you will not find ZenMode by searching for it inside a scenario. The connection is a custom webhook URL, generated by Make's own webhook trigger module, that you paste into the "Webhooks (Zapier / Make)" card in ZenMode's settings. From then on ZenMode POSTs a JSON body to that URL whenever the event you picked happens, and your scenario runs on it.
So this is a webhook-mediated integration rather than a native one. The producer side is real and shipping; the Make side is a generic webhook trigger, and traffic only ever flows one way — ZenMode to Make.
What it triggers
Each saved webhook carries exactly one trigger, and you can save one per event you care about.
The body is always the same envelope — a JSON object with event, timestamp and data — with
the fields below inside data.
| Trigger | Fires when | Fields in data |
|---|---|---|
connection_sent | a connection request goes out to a prospect | contact_id, name, title, company, linkedin_url, campaign_id |
connection_accepted | the prospect accepts the request | contact_id, name, title, company, linkedin_url, campaign_id |
reply_received | the prospect replies | contact_id, name, title, company, linkedin_url, campaign_id |
new_contact | a CRM contact is created that did not already exist | contact_id, name, company, title, linkedin_url, source_campaign_id |
contact_status_changed | a contact's status moves | contact_id, name, old_status, new_status |
deal_stage_changed | a deal moves stage | deal_id, deal_name, contact_id, old_stage, new_stage, value |
What is absent is as important as what is there. reply_received tells you who replied and on
which campaign, not what the message said. new_contact only fires when the contact did not
already exist in the CRM. There are no open or click metrics in any payload, because ZenMode does
not collect them.
How to set it up
- In Make, start a scenario with the Custom webhook trigger module, add a webhook, and copy the URL Make generates for it.
- Open ZenMode's settings and scroll to the card titled "Webhooks (Zapier / Make)". The field's placeholder shows a Zapier-style URL, but any HTTPS endpoint is accepted — paste Make's.
- Choose one of the six triggers from the dropdown.
- Save the webhook.
- Put the Make scenario into "determine data structure" mode and press Test on the saved row in ZenMode. That sends a live delivery, which is how Make learns the payload shape.
- Repeat for every event you want. Each saved webhook has its own Test and Delete button.
When it runs
A webhook fires on the event as it happens. There is no polling interval and no batch window: ZenMode POSTs the JSON to your URL and allows a 10-second timeout for the response.
These CRM webhooks are unsigned — no X-ZenMode-Signature header, no shared secret. Anyone
holding the URL can post to your scenario, so treat it the way Make treats it: as a secret.
ZenMode's REST API is the surface that does sign its deliveries with an HMAC signature, and that
one is gated to paid plans other than Novice, which the plan comparison sets out.
What it's useful for
Make earns its place when the next step lives somewhere ZenMode has no native connector for.
A reply_received webhook into a router can notify the right rep by campaign. A
connection_accepted webhook can create a record in a database module and start a timer for a
manual touch. A deal_stage_changed webhook can keep a finance sheet or a reporting table in step
with the pipeline without anyone re-keying it.
Contacts and deals still live in ZenMode's built-in CRM; the scenario is for telling other systems that something moved, not for holding the data.
What it doesn't do (yet)
- No Make module. No ZenMode app in the library, no OAuth connection, no ready-made actions or searches. A custom webhook trigger is the whole integration.
- One direction only. Make cannot write contacts, notes or statuses back into ZenMode's CRM.
- No in-app delivery log. Deliveries are recorded internally, but the "Logs" button on a webhook has no working endpoint behind it, so you cannot review delivery history inside ZenMode. Make's own scenario history is where you check what arrived.
- Fixed payloads. You cannot add fields, pick a subset, or include reply text.
The card is shared with Zapier — same six triggers, same payloads — so the Zapier integration page describes the identical mechanism from the other side.
FAQ
Which plans include Make webhooks?
All plans. The CRM webhook card has no tier gate at all. The only integration surface at ZenMode that is plan-gated is the REST API and its signed webhooks, which require a paid plan other than Novice.
Does connecting Make need my LinkedIn password?
No. You paste an HTTPS URL into ZenMode and ZenMode posts CRM event data to it. No ZenMode integration asks for, stores or transmits LinkedIn credentials.
Is it two-way?
No. It is an outbound producer. ZenMode posts to your Make webhook when an event happens, and there is no supported route for a scenario to push data back into ZenMode's CRM.