Zapier + SalesCrew
Outbound webhooks going out and the API coming in. That covers most of what people want a Zap for, with every write audited.
Want to see it first? Book a demo
- Webhooks out, API in
- Any Webhooks by Zapier step works
- Deliveries logged and retried
The short answer
- SalesCrew connects through outbound webhooks with deliveries and retries, plus its API and MCP server, rather than a directory app. Any Zap that uses Webhooks by Zapier works.
- Out of SalesCrew: register a webhook on the events you care about and Zapier catches it. Into SalesCrew: a Zap posts to the API or calls an MCP tool, and the write lands in the audit log with its actor.
- Webhooks carry the full event payload. A couple of minutes of setup gets you the same data a dropdown trigger would, for any event you register.
Mechanism
How data moves in each direction.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| SalesCrew to Zapier | Outbound webhook to a Zapier catch hook URL | Outbound | Any event you register | Available |
| Delivery reliability | Deliveries recorded, failures retried, signature secret rotatable | Outbound | Webhook deliveries | Available |
| Zapier to SalesCrew | Zapier posts to the SalesCrew API | Inbound | Contacts, companies, deals, tasks, notes, leads | Available |
| Zapier to SalesCrew over MCP | A custom action calling an MCP tool with a scoped token | Inbound | Anything with a tool, which is every UI action | Available |
Mechanisms read from the SalesCrew integration table, September 2026. Zapier's own pricing decides whether webhook steps cost you extra on your plan.
Setup
One Zap in each direction, and you have covered most cases.
- 1
Create the catch hook in Zapier
Start a Zap with Webhooks by Zapier as the trigger, choose Catch Hook, and copy the URL Zapier gives you.
- 2
Register the webhook in SalesCrew
webhook_create takes the URL and the events. webhook_test fires a sample so you can map fields before anything real happens.
- 3
Map the fields in Zapier
The payload is JSON. Map what you need into the destination app and ignore the rest.
- 4
For the other direction, issue a token
mcp_token_issue creates a token scoped by channel, profile and area. Give the Zap the narrowest scope that does the job.
- 5
Post from Zapier
A Webhooks by Zapier action posting to the SalesCrew API or an MCP tool. The write is audited with the token as the actor.
- 6
Watch the deliveries
webhook_deliveries shows what was sent and what failed, and webhook_retry replays one. Rotate the signing secret when someone leaves.
Every write is audited
Questions
- Is a webhook slower than a native trigger?
- No. A catch hook fires as soon as the event does.
- What events can I send?
- You register the webhook against the events you want. Because every action in the app is also an MCP tool, the surface of things that can happen is the same surface an agent can operate.
- Is this secure?
- Deliveries are signed with a secret you can rotate, and inbound writes use a scoped token that you can revoke. Every write is logged with the actor, whether that is a person, a token or an agent.
- Should I use Zapier, Make or n8n?
- Whichever you already run. All three connect the same way here, so the choice is about your own team rather than about SalesCrew.
Wire one webhook each way and see what it covers
Most teams find two Zaps replace the connector they were waiting for.
Want to see it first? Book a demo