Tideflow Docs

Integration options

Tideflow exposes event data through outbound webhooks so you can integrate call handling with your own systems. There are three integration paths, ordered from simplest to most advanced.

1. Slack incoming webhooks

The lowest-effort option. Tideflow sends formatted Slack Block Kit messages to a channel of your choice whenever a call is handled, a lead is created, or a lead status changes.

No code required — just paste a Slack incoming webhook URL.
Best for team awareness and quick review.
See Slack for setup instructions.

2. Generic outbound webhooks

Tideflow sends structured JSON payloads to any HTTPS endpoint you control. Each delivery is signed with HMAC-SHA256 so you can verify authenticity. Built-in CRM templates can format payloads for HubSpot or Salesforce.

Moderate effort — you need a receiver endpoint that accepts POST requests.
Best for custom integrations, CRM syncing, and automation.
See Webhooks for general setup and webhook events for payload details.

3. Tideflow webhook receiver

An advanced option for teams that want a managed destination without building their own endpoint. Tideflow provides a Supabase Edge Function that receives deliveries and stores them in a queryable inbox table.

Higher effort — requires deploying a Supabase function and managing receiver tokens.
Best for technical teams that want full control over event processing without external infrastructure.
See webhook receiver for the setup guide.

Event types

All three paths share the same set of event types:

new_lead— A new caller/lead was created after a call.
call_completed— Call processing finished.
lead_status_changed— A lead's status was updated.

See webhook events for full payload documentation.

CRM payload templates

When creating a webhook endpoint, you can choose a payload template that reshapes the data for your CRM:

Template	Description
`raw`	Default JSON pass-through. Use this for custom integrations.
`hubspot_contact`	Maps lead data to HubSpot contact properties format.
`salesforce_lead`	Maps lead data to Salesforce lead format.

Plan requirements

Webhooks require an active plan that includes the webhooks feature. Slack notifications and webhook endpoints are configured from Settings → Integrations in your dashboard.

Next steps

Webhook events— Event types and payload schemas.
Webhook authentication and delivery — Signature verification and delivery semantics.
Webhook receiver— Managed receiver setup guide.