Can Heartbeat and Resend talk in both directions?

Yes. Build one flow that starts in Heartbeat and acts in Resend, 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.

Connect Heartbeat to Resend

Move data between Heartbeat and Resend 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.

Start building Explore Heartbeat Explore Resend

Heartbeat triggers: 5
Heartbeat actions: 45
Resend triggers: 1
Resend actions: 22

Automation ideas

What you can build with Heartbeat and Resend

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

New Member Joined in Heartbeat creates Send Email in Resend
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Event in Resend creates Create User in Heartbeat
Triggers when a selected email, domain or contact event happens.
New Member Joined in Heartbeat creates Send Batch Emails in Resend
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Event in Resend creates List Members in Heartbeat
Triggers when a selected email, domain or contact event happens.
New Member Joined in Heartbeat creates Get Email Status in Resend
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Event in Resend creates Get Member in Heartbeat
Triggers when a selected email, domain or contact event happens.