A call ends, but the work often continues: someone needs a follow-up task, a CRM update or a team notification. HeyRik's new Make integration sends a structured event after a call so you can build that next step in your own Make scenario.
Following our HubSpot integration, this addition gives teams another way to connect calls with the tools they already use. HubSpot handles contact lookup and confirmed lead creation during calls; Make focuses on workflows after calls. You choose the assistant and destination, and switch delivery on explicitly. It does not run inside the live conversation or enable any workflow automatically.
Turn a call outcome into a next step
For example, route a saved callback outcome into a task for your sales team, or collect call summaries in an operations tracker. These are scenarios you configure in Make, not actions HeyRik installs automatically. Filter by the event type and outcome before running downstream steps.
- Receives call and assistant IDs, status, direction, duration, outcome, summary and timestamps.
- Works with new web and phone calls for the assistant you select.
- Does not send recordings, recording links, full transcripts or hidden metadata. Summaries can still contain personal information.
Set up the Make integration
- 1Create a Make scenario beginning with Webhooks → Custom webhook. This release supports the eu1, eu2, us1 and us2 Make webhook hosts and secret-URL authentication only, not additional API-key headers.
- 2In HeyRik Connected apps, select your assistant and attach Make. Paste the webhook URL and save it; keep it private like a password.
- 3Choose Run once in Make, then send a test event from HeyRik. Inspect the received fields before mapping them.
- 4Filter event = call.completed so connection tests cannot trigger customer-facing actions. Deduplicate using the top-level event ID before creating tasks or sending messages.
- 5Enable After a call ends in HeyRik and activate your tested Make scenario. Make a test call and verify both delivery history and the downstream result.
Delivery is not the same as completion
HeyRik queues post-call events and retries temporary failures up to five attempts. Delivery waits for saved call data to settle; it is not immediate. A delivered status means the webhook accepted the request, not that every action in your Make scenario succeeded.
A network timeout may occur after Make accepted an event, so retries can produce duplicates. Your scenario should deduplicate by event ID. Disabling post-call delivery cancels queued post-call work; disconnecting removes the connection. A request already in flight may still arrive.
Start with a low-risk workflow
Begin with a test assistant and a destination used only by your team. Check that the event filter excludes connection tests, the summary contains only information you intend to share, and duplicate events do not create duplicate tasks. Then enable the workflow for the assistant that needs it. This release is post-call-only: it does not add live-call tools, retrieve results from Make or replace your existing CRM connection. Open Connected apps to set up your first workflow.
A little more before you begin.
Does Make receive my previous calls?
No historical backfill is enabled. Post-call delivery applies to new calls created after opt-in for that assistant.
Does a delivered event mean my task was created?
No. Check your Make scenario run and destination to confirm downstream actions completed.
Can my agent wait for a Make result during a call?
Not in this release. Make is a post-call webhook integration, not a live lookup or action tool.
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.