Heartbeat

Heartbeat MCP integration

Answers questions about events, channels, members, and access groups from live community data, and restores a removed member by email.

7actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Retrieve user

    Lyro pulls a Heartbeat user's profile by ID during support interactions. Agents verify community member details without leaving the chat.

  • Reactivate user

    Lyro restores community access for a previously deleted member by email. Customers regain instant access without re-signup.

  • List groups

    Lyro shows all access groups in the Heartbeat community. Agents see available roles and groups for user management.

See all 7 actions

How businesses use Heartbeat + Lyro

Each card is one request a support team gets, and the Heartbeat actions Lyro runs to close it.

  • Tell members what is coming up in the community

    Lyro reads the community event list and answers a question about the next session with the details already on the calendar, instead of pointing someone at the events page.

    Get EventsList channelsList Users
  • Point someone at the right channel

    Channels can be listed by type and filtered on archived status, so a member asking where a topic belongs gets the active channel rather than one that was retired months ago.

    List channelsList GroupsGet Events
  • Check who a member is and what they can reach

    Lyro pulls a single member record or filters the roster by role, group membership, or join date, so an access question is answered against the community's own data.

    List UsersRetrieve UserList Groups
  • Restore access for a member who was removed

    A returning member is reactivated by email address, and Lyro can confirm the restored record and the group it sits in straight afterwards so nobody has to check twice.

    Reactivate UserRetrieve UserRetrieve Group

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Heartbeat actions it has and picks the ones a request needs.

  1. 01

    Connect Heartbeat

    Authorize the Heartbeat account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Heartbeat actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Heartbeat · Lyro

Everything else about Heartbeat

Setup, permissions, and the limits of what Lyro can do inside Heartbeat.

  • No. The toolkit is read access to events, channels, groups, and users, plus one write: Reactivate User. Posting, moderating, and deleting members stay with your admins in Heartbeat itself.

Every action available in Heartbeat

All 7 actions your agent can call on Heartbeat, straight from the live MCP connection.

  • Get events

    Retrieve event information from the community.

  • List channels

    Retrieve a paginated list of channels in the community.

  • List groups

    Retrieve a paginated list of access groups in the community.

  • List users

    Retrieve a paginated list of users in the Heartbeat community.

  • Reactivate user

    Reactivate a previously deleted user by email to allow them to access the community again.

  • Retrieve group

    Retrieve a single group by its ID.

  • Retrieve user

    Retrieve a single user by their ID.

Ready to connect Heartbeat?

Authorize the account and your agent has all 7 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot