Heartbeat

Manage members, channels, threads, chat, events, groups, invitations, and courses in a Heartbeat community. Agents onboard members and keep community access aligned with billing and program status.

11 triggers 52 actions API key available

Heartbeat website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

A subscription payment fails in billing and the account enters dunning

Agent resolves the community member with Find User by Email and reads their role and group memberships

Agent looks at what the person is currently in the middle of: an active course, an upcoming event they are hosting, a paid cohort seat

Agent confirms the retry schedule has actually run out rather than still being in progress

Agent sends the member a direct message with the billing link before anything is touched

The community manager chooses removal, downgrade, or grace, and the agent applies the choice

What This Integration Enables

Heartbeat is a community platform, not a team chat tool, and the difference decides what these flows are for. A community has members with roles, groups that gate what those members can see, invitation links that carry a role and a group assignment, events with RSVPs and attendance, courses with modules and lessons, and a wiki. Membership is usually tied to money. So the work here is not "post a message to a room". It is access management with a social surface on top, and it runs continuously as people join, pay, lapse, finish a course, or quietly fail to complete a signup.

This connector covers that whole surface. FlowRunner agents create, update, delete, and reactivate members, and create pending users who are admitted the first time they log in. They build and tear down channel categories, posts channels, chat channels, and voice channels. They write threads and comments in Heartbeat rich text with mentions, and send chat messages and direct messages as a chosen admin. They run events and read attendance, manage groups and their memberships by email, and create invitation links that assign a role and groups on join. They also build lessons inside courses. Eleven real time triggers cover the events that matter, each registering a Heartbeat webhook while it is enabled and removing it when it is not.

One of those triggers deserves calling out because it is a revenue signal wearing a community event's clothes. On Abandoned Invitation fires when somebody enters their email on an invitation link and then does not complete payment or join. That is a person who wanted in and did not make it, surfaced automatically, and it is precisely the kind of automation exception that never reaches anyone in a manual process because nothing in the product asks you to look for it.

Without FlowRunner

Access follows billing by hand Someone reconciles the payment system against the member list when they get to it

Onboarding is manual New members are created, roled, and grouped one at a time after they pay

Signals get missed Mentions, direct messages, and abandoned signups are noticed only if a human is looking

With FlowRunner

Access follows billing on a signal A payment event starts the flow the moment it happens

Onboarding runs on arrival The member, their role, their groups, and their welcome message are ready when they first log in

Signals become work Mentions, RSVPs, course completions, and abandoned invitations each start their own flow

Use Case Scenarios

Paid signup to fully provisioned member

A subscription is paid in Stripe. The agent calls Create User with the role that tier buys, then adds them to the starter group and to the cohort group for their intake month with Add Users to Group. It sends a personal direct message from the community manager's account introducing the two channels worth reading first, and posts a short welcome in the introductions channel. If the person paid but has not logged in yet, Create Pending User does the same work in advance so their account is waiting rather than being built while they watch a spinner.

Abandoned invitations turned into follow up

On Abandoned Invitation fires when someone starts an invitation link and stops. The agent reads which invitation they came through, which tells it the role and groups they were being offered, and writes the lead into the CRM with that context attached. A follow up goes out by email with the same link. Nothing about this is aggressive, and it does not require the community manager to notice a gap between invitation views and joins, because there was never a report that showed them that gap.

Events and courses that update the systems outside the community

After a live session hosted in Zoom, the agent posts a recap thread in the announcements channel with the recording link and the questions that went unanswered, then reads Get Event Attendance and writes who actually showed up back to the CRM. Separately, On Course Completed fires as members finish, and the agent logs the completion to Google Sheets, adds the member to the alumni group, and hands the certificate step to the flow that sends it. Community activity stops being invisible to the rest of the business.

Human-in-Loop Highlight

Delete User removes a person from the community. They lose the groups holding their history, the courses they may have paid for, and the threads they wrote. The action that usually triggers it is a payment event, and payment events are noisy. A card expires and the retry succeeds two days later. An annual renewal sits pending while a finance team processes an invoice. A dunning webhook fires while the member is halfway through a cohort they already paid for. Reactivate User exists, and it does not undo the experience of being locked out of a community you thought you belonged to.

So the agent assembles the case and stops. "Dana Okoro's subscription failed dunning after four retries. She is in the March cohort, has completed six of nine lessons, and is listed as a host on an event nine days from now. I have sent her the billing link by direct message and had no reply in five days. Remove her, downgrade her to the free role and keep her groups, or hold until after the event she is hosting?" The community manager answers on the human-in-the-loop channel they already use, and the agent applies exactly that outcome, whether that is Delete User, an Update User role change, or nothing at all. The agent should absolutely be doing the reconciliation, the outreach, and the waiting. The eviction is somebody's judgment call.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

52 actions

Members

Get User Retrieves a community member by user identifier. Used to load a member's current state before acting on them.
Find User by Email Looks up a community member by email address. Used to join a billing or CRM record to the right person in the community.
List Users Returns all users in the community with profile, role, admin flag, and group memberships. Used for reconciliation against a source of truth and for periodic access reviews.
Create User Creates a new user with a role, optional group memberships, and profile fields. Used to provision access the moment a signup or payment lands.
Update User Updates a user's profile information, addressed by email. Used to change a role on upgrade or downgrade, and to keep profile data in step with the CRM.
Delete User Removes a user from the community, addressed by email. Cuts off access to groups, courses, and history, so it belongs behind an approval rather than behind a billing event.
Reactivate User Reactivates a previously removed user, restoring their access. Used when a lapsed payment is recovered or a removal was made in error.
Create Pending User Creates a pending user who is added to the community the first time they log in. Used to provision ahead of arrival so the account is ready rather than being built on first visit.
Get Notification Count Returns the number of pending notifications a member has, addressed by email. Used in re engagement flows to tell a quiet member from an unreachable one.

Channel Categories

List Channel Categories Returns all channel categories in the community. Used to place a new channel in the right section rather than at the bottom of the list.
Create Channel Category Creates a channel category and returns its identifier and name. Used when a new program or cohort needs its own section.
Update Channel Category Renames an existing channel category. Used to keep the structure legible as programs change.
Delete Channel Category Deletes a channel category from the community. Used in cleanup at the end of a program.

Channels

List Channels Returns all channels with identifier, name, emoji, and type. Used to resolve a destination channel by name before posting.
Create Channel Creates a posts or chat channel under a category, with optional privacy, read only mode, and invited users or groups. Used to provision a cohort or project space with the right audience already set.
Update Channel Edits a channel's settings. Used to open a private channel to a wider group, or to switch it to read only when a program ends.
Delete Channel Deletes a channel from the community, along with what was posted in it. Used in cleanup, and worth confirming when the channel holds member history.
Create Voice Channel Creates a voice channel under a category, with optional privacy and invited users or groups. Used for cohort office hours and study rooms.
Update Voice Channel Edits a voice channel's settings. Used to change who can join as a program moves through its phases.

Threads and Comments

List Channel Threads Returns the most recent threads in a channel with content, files, author, URL, and comments. Used to summarize activity and to spot questions nobody answered.
Get Thread Retrieves a thread by identifier, including its content and its comments with replies. Used to pull the full context behind a mention or a report.
Create Thread Creates a thread in a channel using Heartbeat rich text, an HTML subset that supports paragraphs, links, emphasis, headings, lists, and mentions by user or group identifier. Used for announcements, recaps, and weekly program posts.
Create Comment Creates a comment on a thread using Heartbeat rich text. Used to answer in place rather than starting a new thread, and to log an outcome under the post that raised it.

Chat and Direct Messages

Send Chat Message Sends a rich text message to a chat channel, posted as a chosen admin user. Used for live announcements during events and for time sensitive community notices.
Get Chat Messages Retrieves messages from a chat channel with cursor based pagination. Used to catch up on a room before summarizing it or routing something out of it.
Create Direct Chat Creates a direct chat between two users and returns its identifier and URL. Used to open a private thread with a member before a personal message.
Send Direct Message Sends a rich text direct message to a user. Used for welcomes, billing nudges, and one to one follow up that should not happen in a public channel.
Get Direct Messages Retrieves the most recent messages from a direct message conversation. Reads only conversations that include at least one admin user. Used to check whether a member replied before escalating.

Events

List Events Returns all events in the community, optionally filtered to a group. Used to build calendars and reminders outside Heartbeat.
Get Event Retrieves an event with its schedule, recurrence flag, creator, and invited users and groups. Used to confirm details before announcing or syncing it.
Create Event Creates a new event in the community. Used to publish a session from a scheduling system or a program plan without anyone retyping it.
Get Event Instances Returns all instances of a recurring event with their start and end times. Used to reason about a series rather than a single date.
Get Event Attendance Returns attendance data for recent instances of an event. Used to write who actually attended back to the CRM, and to find members who registered and stopped showing up.

Groups

List Groups Returns all groups in the community with members, color, parent group, and archived flag. Used for reconciliation and for working out what a member can currently see.
Get Group Retrieves a group by identifier with its members and settings. Used to check membership before adding or removing anyone.
Create Group Creates a group with optional initial members by email, a parent group, and isolation and joinable settings. Used to stand up a cohort, a tier, or a program audience.
Update Group Edits a group's settings. Used to open a cohort to self joining, or to close it once intake ends.
Delete Group Deletes a group from the community. Removes the access it granted, so it belongs in a reviewed cleanup rather than a rule.
Add Users to Group Adds users to a group by email address. This grants what the group gates, so it is an access change rather than a tagging operation.
Remove Users from Group Removes users from a group by email address. Used on downgrade and at the end of a cohort, and worth confirming when the group holds paid content.

Invitations and Roles

List Invitations Returns all invitations in the community with their code, role, and groups. Used to audit which join paths are open and what they grant.
Create Invitation Creates an invitation link that assigns joiners a role and adds them to given groups. Used to give a partner, a cohort, or a campaign its own join path with the right access baked in.
Add Users to Invitation Adds users to an existing invitation by email, optionally sending them an invitation email. Used to enroll a known list against a join path that already carries the right role.
List Roles Returns all roles in the community with their identifier and name. Used to resolve the right role before creating or updating a member.

Courses and Content

List Courses Returns all courses with their category and full cohort, module, and lesson structure. Used to map a member's entitlement to actual content.
Get Lesson Retrieves a lesson by identifier, including its content and community embed cards. Used to check what a lesson contains before editing or linking to it.
Create Lesson Creates a lesson in a course module with a hero video, a publish status, and optional community embed cards. Requires either a Heartbeat native video or an external embed URL, so the video step comes first.
Update Lesson Updates a lesson's content or publish status. Used to release drip content on schedule and to correct published material.
List Videos Returns all Heartbeat native videos with name, aspect ratio, duration, and view count. Used to resolve the hero video a new lesson needs.

Documents and Webhooks

List Documents Returns wiki posts in the community with cursor based pagination. Used to inventory the knowledge base and find stale material.
Get Document Retrieves a wiki post by identifier, including its content. Used to mirror community documentation into another system.
List Webhooks Returns all webhooks registered for the community with their identifier, URL, and trigger action. Used to audit what is currently listening to the community.

Triggers

11 triggers

Event Triggers

On User Joined Fires whenever a new user joins the community. Used to start welcome, group assignment, and CRM sync flows at the moment of arrival.
On User Updated Fires whenever a user updates their profile or their group memberships change. Used to keep an external record in step and to notice an access change nobody logged.
On New Thread Fires whenever a new thread is created in the selected channel. Used to route questions to the person who can answer them and to mirror announcements outward.
On Mention Fires whenever the selected user or group is mentioned in a thread or comment, optionally limited to one channel. Used to make sure a support or moderator group never misses a call for help in a busy community.
On Direct Message Fires whenever the selected admin user receives a direct message. Supports admin users as the watched recipient. Used to triage inbound member questions without a person watching an inbox.
On Event Created Fires whenever a new event is created in the community. Used to publish the event outward to a calendar, a newsletter, or a CRM campaign.
On Event RSVP Fires whenever someone RSVPs to an event, optionally limited to one event and to members or external guests. Used to send confirmations, add people to a reminder sequence, and forecast attendance.
On Group Joined Fires whenever a user joins the selected group, including the first time they join the community. Used to deliver the onboarding that belongs to a specific tier or cohort rather than a generic welcome.
On Course Completed Fires whenever a user completes the selected course. Used to issue certificates, move members into an alumni group, and trigger the next offer.
On Document Created Fires whenever a wiki post is created in the community. Used to review new documentation and to mirror it into an external knowledge base.
On Abandoned Invitation Fires when someone enters their email on an invitation link but does not complete payment or join. Used to follow up on a person who wanted in and did not make it, which is the one community signal that no report will show you.

Frequently Asked Questions

What can FlowRunner do with Heartbeat?

FlowRunner agents can run Get User, Find User by Email, and List Users in Heartbeat, plus 49 more actions.

Does connecting Heartbeat to FlowRunner require OAuth?

No. Heartbeat connects to FlowRunner with an API key, no OAuth flow required.

Can Heartbeat trigger a FlowRunner workflow automatically?

Yes. Heartbeat supports 11 triggers that can start a FlowRunner workflow automatically.

Start building with Heartbeat

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us