Feed Pipedrive deals from your SalesCrew outbound
SalesCrew reaches Pipedrive via webhooks. A Zapier, Make or n8n flow turns each booked meeting into a person and a deal.
- Via webhooks
- Match on email
- Your own database per client
The short answer
- SalesCrew connects to Pipedrive via webhooks, with Zapier, Make or n8n in the middle. You choose the SalesCrew events, and the flow creates or updates Pipedrive persons, organizations and deals through Pipedrive's API.
- Pipedrive stays the client's closing pipeline. The prospecting, the sequences, the sender pool and the suppression list stay in SalesCrew, in a database that belongs to that client alone.
- Deliveries carry an HMAC SHA-256 signature, land in a delivery log, and retry with backoff. After 20 straight failures the webhook pauses until you fix the receiver and click Retry.
Mechanism
Which event triggers what, and where it lands in Pipedrive.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Booked meeting | meeting.booked webhook, then a flow that creates a Pipedrive person and deal | Outbound | Persons, deals | Available |
| New qualified lead | lead.created webhook, filtered in the flow before it reaches Pipedrive | Outbound | Persons, organizations | Available |
| Stage mirror | deal.stage_changed webhook for deals that start in SalesCrew | Outbound | Deals | Available |
| Pipedrive back to SalesCrew | Pipedrive webhook, then a post to a SalesCrew inbound webhook | Inbound | Leads | Available |
| Agent-driven updates | MCP tools such as deal_update_stage and note_add | Inbound | Deals, notes | Available |
| Failure handling | Delivery log, backoff retries, replay with webhook_retry | Outbound | Deliveries | Available |
SalesCrew mechanisms read from the SalesCrew integration table, September 2026. Pipedrive's REST API and Webhooks endpoint checked on developers.pipedrive.com, September 2026.
Setup
One flow per client pipeline, built in your automation tool.
- 1
Start the flow with a webhook trigger
Create it in Zapier, Make or n8n and copy the URL it gives you.
- 2
Add the webhook in SalesCrew
Settings → Webhooks → Add. Paste the URL and pick meeting.booked, plus any other event the client wants to see.
- 3
Map to Pipedrive
Send a test ping, then map event and data fields to a Pipedrive person, organization and deal. Look up the person by email first.
- 4
Pick the pipeline and stage
Decide where a booked meeting lands in the client's Pipedrive pipeline, so their sales team sees it on the right column.
- 5
Add the return path if you need it
Subscribe to a Pipedrive webhook for deal changes and post it to a SalesCrew inbound webhook with a default owner set.
Agree who owns each field
Questions
- How do SalesCrew leads get into Pipedrive?
- Through an automation tool. SalesCrew posts a signed webhook on events such as meeting.booked, and a Zapier, Make or n8n flow turns it into a Pipedrive person and deal through Pipedrive's API.
- Can Pipedrive send changes back?
- Yes. Pipedrive documents a REST API with a Webhooks endpoint on developers.pipedrive.com. Subscribe to the change you care about, send it to your automation tool, and post it to a SalesCrew inbound webhook.
- Why keep outbound out of the client's Pipedrive?
- Volume and hygiene. Cold lists, bounces and opt-outs belong in the system that sends, where suppression is checked when the audience freezes and again at send time. Pipedrive then receives only people who replied or booked.
- What does it cost to run this for several clients?
- Each client gets their own SalesCrew instance on any tier: $299, $699 or $1,200 a month, with unlimited seats. The automation tool is billed by its own vendor.
Send Pipedrive only the leads that booked
Outbound and suppression in SalesCrew, closing in Pipedrive, one signed webhook between them.