Skip to main content
Use Webhooks by Zapier for SendPilot events and REST actions. These are API-key integrations, not MCP OAuth connectors.

​
Receive an event

  1. Create a Zap with a Webhooks trigger and obtain its HTTPS destination.
  2. Register the destination in SendPilot → Integrations → Webhooks for the intended workspace.
  3. Select exact event types, such as reply.received or connection_request.accepted.
  4. Send a test event and map fields from the captured JSON body.
Verify the raw body and signature before trusting events. If the trigger cannot perform Svix verification, place a verifying receiver in front of the Zap and forward only verified events. Deduplicate by eventId.

​
Reply → notification or CRM task

Filter on eventType = reply.received. Use data.reply for message text and data.linkedinUrl for the profile. data.leadId and data.campaignId can be null for non-campaign conversations; only perform lead-ID actions when an ID is present. For connection notifications, filter on connection_request.accepted. For lead outcome changes, use lead.updated, whose data includes previousStatus and newStatus.

​
Form submission → campaign lead

Configure a Custom Request action:
Map your form fields into this body:
REST accepts flat custom fields and up to 1,000 leads per import. Check the import response for added, duplicate and invalid entries before marking the source record processed.

​
Update an outcome

Use PATCH /v1/leads/LEAD_ID/status, the same authentication/content headers and a stable idempotency key:
Do not set sequence-managed statuses such as REPLY_RECEIVED. See allowed lead outcomes.

​
Retries

Reuse the same Idempotency-Key and request on retries; do not generate a fresh random value for each attempt. Handle rate limits and uncertain outcomes using the REST retry guide. An accepted REST send executes directly, without MCP approval forms.