Automation & workflows
n8n voice agents,
wired by webhook.
Finn runs the call. n8n runs everything that happens next. There is no node to install — a Webhook node receives Finn's events, and an HTTP Request node starts calls from any workflow you already have.
30-minute free trial. No card. No procurement.
How it works
Webhook in.
API out.
Two nodes and a URL. Nothing to install on either side, and both halves are reversible — disconnect the webhook and calls carry on without it.
Add a Webhook node in n8n
Create a workflow whose trigger is a Webhook node. Copy the URL n8n gives you and paste it into Settings → Integrations → Webhooks in Finn.
Choose which events fire it
Subscribe the endpoint to the events you care about — call.analyzed carries the transcript, outcome and post-call analysis fields. Failed deliveries retry with backoff for 24 hours and are visible in the Delivery Log.
Latency
384ms
Status
200
Retries
0
Request
POST /api/inventory/check
{
"sku": "NAVY-HOODIE-M",
"region": "IN-MH"
}Response
{
"in_stock": true,
"count": 124,
"next_restock": "2026-06-04"
}Start calls from any workflow
Point an HTTP Request node at the Finn REST API to launch a call from n8n — a new row in a sheet, a form submission, a CRM stage change, a cron. Anything n8n can trigger on can now place a call.
Why webhooks rather than a connector
Nothing to wait for.
Nothing to outgrow.
No bolt-ons. No second platform. Every primitive ships with the editor.
Works on self-hosted n8n
No marketplace listing to depend on and no vendor node to keep current. If your n8n can reach the internet, or you can reach it, the integration works.
Every event, not a chosen subset
A connector exposes whatever its author wrapped. The webhook carries the full payload, so fields added later reach your workflow without an update.
Retries you can inspect
If your workflow is down or over its execution limit, Finn treats it as a failed delivery and retries with backoff for up to 24 hours. The Delivery Log shows the response Finn actually got.
Bidirectional from day one
Events out via webhook, calls in via the REST API. Most connectors do one direction well and the other badly.
Trust + ecosystem
Plugs in. Audits clean.
Wires into your existing stack via 100+ connectors. Compliant from day one across the workloads that demand it.
n8n
ZapierMakeWebhooksREST APIDon't see yours? Finn plugs into any system via REST + webhooks.
FAQ
Questions and answers.
Is there an official Finn node for n8n?+
No. There is no Finn node to install in n8n, and none in Zapier or Make either. The connection is a webhook: Finn sends the event, your Webhook node receives it, and the rest is ordinary n8n. For calls in the other direction, an HTTP Request node against the REST API does the job.
What does Finn send when a call ends?+
The call.analyzed event carries the transcript, the call outcome and the post-call analysis fields you configured — sentiment, extracted values, custom questions. See the webhook events reference in the developer docs for the full payload.
Can n8n start a call?+
Yes. Use an HTTP Request node against the Finn REST API. Anything that can trigger an n8n workflow — a new spreadsheet row, a form submission, a CRM stage change, a schedule — can place a call.
What happens if my n8n workflow is down?+
Finn treats a non-2xx response as a failed delivery and retries with backoff for up to 24 hours, then stops. Check Settings → Integrations → Webhooks → Delivery Log to see the exact response received.
Does this work with self-hosted n8n?+
Yes, provided Finn can reach your webhook URL. Self-hosted instances behind a private network need a tunnel or a publicly reachable endpoint, the same as any other webhook producer.
Should I use n8n or connect my CRM directly?+
If your CRM is HubSpot, Salesforce or Pipedrive, connect it directly — the native integration syncs contacts in and writes outcomes back without a hop. Use n8n when the work is not a CRM write, or when the system you want is not one Finn connects to natively.
Automation you already run
Finn handles the call.
n8n handles the rest.
Every call produces a transcript, an outcome and analysis fields. Send them to n8n and the downstream work — CRM writes, Slack posts, spreadsheets, follow-up emails — is workflow you already know how to build.