Your calling assistant has finished a useful conversation. Now your team needs a callback task, an internal update or a record of the outcome. The HeyRik n8n Cloud integration sends saved call outcomes to a workflow you build, so you can connect that follow-up to the tools your team already uses.
For example, an Indian admissions team could route a callback request into its counselling tracker. A sales team could review summaries in an internal workflow before deciding its next action. These are workflows you configure, not actions installed automatically. This release adds optional post-call delivery for each assistant, alongside the existing HubSpot and automation connections. It does not alter the live conversation or add an n8n lookup tool.
What reaches your workflow
- A structured event with an ID, call and assistant IDs, status, direction, duration, outcome, summary and timestamps.
- Only new calls after post-call delivery is enabled for that assistant; no historical backfill.
- No recording files, recording links or full transcripts. Summaries can still contain caller information, so review your destination and permissions.
Connect n8n Cloud
- 1Create a Webhook node with POST, Authentication None and Respond Immediately. Retain its randomly generated UUID-v4 path and publish the workflow.
- 2Choose your assistant in HeyRik Connected apps and attach n8n Cloud. Paste its production URL: https://<instance>.app.n8n.cloud/webhook/<UUID>. Keep this URL private.
- 3Send a HeyRik test event and inspect the workflow's Executions. This uses the production URL; temporary webhook-test URLs are not supported.
- 4In your workflow, filter body.event = call.completed and deduplicate using body.id before any downstream action. A test event uses connection.test.
- 5Enable After a call ends, make a test call and verify both HeyRik delivery history and the destination result.
Understand the boundaries
This version supports n8n Cloud production endpoints with UUID-v4 paths and secret-URL access only. Self-hosted instances, custom paths and additional authentication headers are not supported. Anyone who obtains the URL can trigger the workflow. Do not use an unvalidated webhook alone to authorize payments or other high-risk actions.
HeyRik queues delivery outside the call and retries temporary failures. A delivered status confirms webhook acceptance, not that a downstream action succeeded. Network retries can produce duplicates, so check your deduplication step. Disabling delivery cancels queued post-call work; a request already in flight may still arrive.
Start with an internal follow-up
Begin with a test assistant and a low-risk internal destination. Check which fields arrive, make sure connection tests cannot trigger business actions, and verify that receiving the same event twice does not create duplicate work. Then enable the assistants that need the workflow. n8n and connected services may require their own plans and permissions. This connector makes no India data-residency guarantee. Open Connected apps to set up your workflow, and check its execution history before relying on it for your team's follow-ups.
A little more before you begin.
Does this support self-hosted n8n?
No. This release accepts only supported n8n Cloud production webhook URLs.
Can n8n return information to my agent during a call?
Not through this connector. It sends events after calls and does not create live-call tools.
Does this automatically update a CRM or send messages?
No. You must separately configure and authorize those steps in your n8n workflow.
Start here
Connect your post-call workflow
Build a voice agent, upload your list or connect your leads, and run your first campaign on HeyRik — free to start, no credit card required.