Skip to content
Twilio logoHeartbeat logo

Connect Twilio to Heartbeat

Move data between Twilio 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.

Twilio triggers
5
Twilio actions
6
Heartbeat triggers
5
Heartbeat actions
45

Automation ideas

What you can build with Twilio and Heartbeat

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

  • New Incoming SMS in Twilio creates Create User in Heartbeat

    Triggers when the selected Twilio number receives an SMS.

  • New Member Joined in Heartbeat creates Send SMS in Twilio

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

  • New Incoming SMS in Twilio creates List Members in Heartbeat

    Triggers when the selected Twilio number receives an SMS.

  • New Member Joined in Heartbeat creates Phone Number Lookup in Twilio

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

  • New Incoming SMS in Twilio creates Get Member in Heartbeat

    Triggers when the selected Twilio number receives an SMS.

  • New Member Joined in Heartbeat creates Call Phone in Twilio

    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 Twilio 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.