Skip to content
KrispCall logoHeartbeat logo

Connect KrispCall to Heartbeat

Move data between KrispCall and Heartbeat the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

KrispCall triggers
5
KrispCall actions
4
Heartbeat triggers
5
Heartbeat actions
45

Automation ideas

What you can build with KrispCall and Heartbeat

A few flows teams run between KrispCall and Heartbeat. Use one as a starting point, or build your own from scratch.

  • New Voicemail in KrispCall creates Create User in Heartbeat

    Trigger when a new voicemail is received.

  • New Member Joined in Heartbeat creates Add Contact in KrispCall

    Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.

  • New Voicemail in KrispCall creates List Members in Heartbeat

    Trigger when a new voicemail is received.

  • New Member Joined in Heartbeat creates Delete Contacts in KrispCall

    Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.

  • New Voicemail in KrispCall creates Get Member in Heartbeat

    Trigger when a new voicemail is received.

  • New Member Joined in Heartbeat creates Send SMS in KrispCall

    Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in KrispCall and acts in Heartbeat, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.