Connecting your CRM
Spelo doesn’t ship native Salesforce/HubSpot/Pipedrive/Google Calendar integrations. Instead, the platform exposes a public REST API and outbound webhooks — the right shape for letting customers wire their own automations.
This page is the recipe book for connecting Spelo to anything.
The two delivery models
- Push (webhooks) — Spelo POSTs to your URL the moment something happens. Use this for low-latency CRM creation, Slack alerts, calendar invites.
- Pull (REST API) — your tool calls Spelo on a schedule. Use this for batch sync, reporting, or systems that don’t accept webhooks.
Most customers use BOTH: push for new-lead alerts, pull for nightly reconciliation.
Push events
| Event | When |
|---|---|
conversation.ended | a voice call finished |
conversation.recording_ready | the audio file is uploaded (separate from ended because upload is async) |
lead.captured | the agent called submit_lead |
lead.updated | a PATCH /v1/public/leads/:id happened (echoes status/notes changes back to your other tools) |
See Webhooks for payload shapes and HMAC signature verification.
Pull endpoints
The standard integration shape
Spelo ──webhook──▶ Zapier / Make / n8n ──▶ Your CRM / Calendar / Slack ──▶ (optional fallback) DB / S3The middle layer (Zapier, Make, n8n) does three things:
- Verify the HMAC signature so a bad actor can’t forge events
- Transform Spelo’s payload into the CRM’s API shape
- Route failures to a fallback (a Slack channel, an inbox, a dead-letter queue)