Does SalesCrew work with Zapier, Make and n8n?

Yes. Outbound webhooks push CRM events to your flows, and the API and 140+ MCP tools take data back in.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/deals
Pipeline with weighted forecast and stage breakdown

The short answer

  • SalesCrew works with Zapier, Make and n8n via outbound webhooks, the SalesCrew API and its MCP server.
  • SalesCrew outbound webhooks send CRM events to a Zap, a Make scenario or an n8n workflow, with a delivery log and automatic retries.
  • Zapier, Make and n8n write back into SalesCrew through the API, and web forms can post leads to the SalesCrew inbound webhook.
  • SalesCrew's 140+ MCP tools let AI clients and custom agents work the CRM directly, with no middle layer.

Two directions, two mechanisms

Out of SalesCrew, you use webhooks. You add the Zap, scenario or workflow URL as an outbound webhook and choose the events. When one fires, SalesCrew posts it, logs the delivery and retries if the receiver doesn't answer. Your flow then does the rest: a Slack message, a row in a sheet, a task in your project tool.

Into SalesCrew, you use the API. Zapier, Make and n8n all have an HTTP step that can create or update a contact, company or deal. For web forms, there's a simpler route: post the form to your instance's inbound webhook, and SalesCrew records the lead with its source.

How SalesCrew connects to each automation tool

ToolOut of SalesCrewInto SalesCrew
ZapierOutbound webhook to a webhook triggerAPI call from a webhook action
MakeOutbound webhook to a custom webhook moduleAPI call from an HTTP module
n8nOutbound webhook to a Webhook nodeAPI call from an HTTP Request node
Web formsNot neededPost to the inbound webhook
AI clients and agentsMCP read toolsMCP write tools, with approval for external sends

SalesCrew integration mechanisms, September 2026.

Where MCP replaces the middle layer

Some automation is only glue for AI: fetch a record, send it to a model, write the answer back. With SalesCrew, you can skip that step. Claude, ChatGPT, Cursor or your own agent calls the MCP tools directly, under a token scoped to what that person can see.

Keep Zapier, Make or n8n for fixed flows between SalesCrew and tools without an MCP client. You'll find step-by-step setup for each on the Zapier, Make and n8n pages.

Test the webhook before you build the flow

Send a test event from SalesCrew first, so your Zap or scenario sees a real payload. Mapping fields against a real sample saves you from a flow that breaks on the first live event.

Questions

How do I send SalesCrew events to Zapier?
Create a Zap that starts with a webhook trigger and copy its URL. In SalesCrew, add an outbound webhook with that URL and pick the events you want. Send a test, and the Zap sees a sample payload to map. Each delivery is logged, and failed ones retry.
Can Make or n8n create records in SalesCrew?
Yes. A Make scenario or an n8n workflow calls the SalesCrew API to create or update contacts, companies and deals. A lead from a form can also post straight to your instance's inbound webhook, which records it with its attribution.
Do I need Zapier to connect SalesCrew to other tools?
Often you don't. SalesCrew has 140+ MCP tools, so an AI client or your own agent can read and write the CRM directly. Zapier, Make and n8n earn their place when you want a fixed, no-code flow between SalesCrew and a tool that has no MCP client.
What happens if a SalesCrew webhook delivery fails?
SalesCrew logs every delivery with its status and retries the ones that fail. You can open the delivery log to see what was sent and when, and send a test event at any time to check the receiving flow.