Can Heartbeat and Gmail talk in both directions?

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

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

Heartbeat triggers: 5
Heartbeat actions: 45
Gmail triggers: 4
Gmail actions: 11

Automation ideas

What you can build with Heartbeat and Gmail

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

New Member Joined in Heartbeat creates Send Email in Gmail
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Email in Gmail creates Create User in Heartbeat
Triggers when a new email matching the filters arrives.
New Member Joined in Heartbeat creates Request Approval in Email in Gmail
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Email in Gmail creates List Members in Heartbeat
Triggers when a new email matching the filters arrives.
New Member Joined in Heartbeat creates Reply to Email in Gmail
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Email in Gmail creates Get Member in Heartbeat
Triggers when a new email matching the filters arrives.