Your admissions, sales or support team finishes a call. Who creates the callback task or updates the operations tracker? The Pabbly Connect integration lets HeyRik send a structured call outcome to a workflow you control, so the next step does not depend on copying a summary by hand.
This addition is designed for teams, including Indian businesses, that already use Pabbly Connect for their day-to-day workflows. Choose an assistant, save your workflow's webhook URL and explicitly enable post-call delivery. It does not change how your agent speaks or add a delay inside a live conversation. Here is how to connect it safely and check that your follow-up actually happened.
A useful next step after the call
For example, an education counselling team could route a callback outcome to its follow-up tracker, while a support team could send a summary to an internal notification workflow. You build and authorize these downstream steps in Pabbly; HeyRik does not install them automatically.
- Events include call and assistant IDs, status, direction, duration, outcome, summary and timestamps.
- Only new calls for the selected assistant are included after opt-in; previous calls are not backfilled.
- No recordings, recording links, full transcripts or hidden metadata are sent. Summaries can still contain caller information.
Set up the Pabbly Connect integration
- 1Create a Pabbly Connect workflow with Webhook by Pabbly as its trigger and copy its connect.pabbly.com/workflow/sendwebhookdata/ URL.
- 2In HeyRik Connected apps, choose your assistant, attach Pabbly Connect and save the URL. Treat it like a password.
- 3Capture the webhook response in Pabbly, then send a test event from HeyRik. Check the received fields before mapping them.
- 4Filter event = call.completed before customer-facing actions. Connection tests use a different event. Deduplicate by the top-level event ID.
- 5Enable After a call ends and activate your tested Pabbly workflow. Make a test call, then check HeyRik delivery history and the actual destination result.
Accepted is not the same as completed
HeyRik uses a background queue and retries temporary failures up to five attempts. Post-call delivery waits for saved call data to settle. A delivered status means Pabbly accepted the webhook, not that a CRM task or notification completed.
Timeouts can produce duplicate delivery. Your workflow must deduplicate using event ID before taking an action. Disabling delivery cancels queued post-call work; disconnecting removes the connection. A request already in flight may still arrive.
Start with an internal workflow
Try an internal tracker before connecting customer-facing messages. Check the event filter, duplicate handling and exactly what the summary shares. Pabbly and downstream services may have their own permissions and charges. This release supports secret-URL webhook authentication, not extra authentication headers, live lookups or agent action tools. It makes no promise about where Pabbly stores data. Once your test result is correct, enable the connection only for the assistants that need it.
A little more before you begin.
Does this replace HubSpot or Make?
No. It is another optional workflow destination. Existing connections remain unchanged.
Can the agent wait for a Pabbly result during a call?
No. This release sends events after calls and does not add live-call tools.
Are WhatsApp messages sent automatically?
No. Any messaging step must be separately configured and authorized in your workflow, including the destination provider's requirements.
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.