Can Heartbeat and Microsoft Teams talk in both directions?

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

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

Heartbeat triggers: 5
Heartbeat actions: 45
Microsoft Teams triggers: 4
Microsoft Teams actions: 16

Automation ideas

What you can build with Heartbeat and Microsoft Teams

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

New Member Joined in Heartbeat creates Create Channel in Microsoft Teams
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Channel Message in Microsoft Teams creates Create User in Heartbeat
Triggers when a new message is posted in a channel.
New Member Joined in Heartbeat creates Send Channel Message in Microsoft Teams
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Channel Message in Microsoft Teams creates List Members in Heartbeat
Triggers when a new message is posted in a channel.
New Member Joined in Heartbeat creates Send Chat Message in Microsoft Teams
Fires when a new member joins the community. Members added with Create User or Create Member do not fire it.
New Channel Message in Microsoft Teams creates Get Member in Heartbeat
Triggers when a new message is posted in a channel.