Answers questions about events, channels, members, and access groups from live community data, and restores a removed member by email.
7actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro pulls a Heartbeat user's profile by ID during support interactions. Agents verify community member details without leaving the chat.
Ayro restores community access for a previously deleted member by email. Customers regain instant access without re-signup.
Ayro shows all access groups in the Heartbeat community. Agents see available roles and groups for user management.
Each card is one request a support team gets, and the Heartbeat actions Ayro runs to close it.
Ayro 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.
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.
Ayro 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.
A returning member is reactivated by email address, and Ayro can confirm the restored record and the group it sits in straight afterwards so nobody has to check twice.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Heartbeat actions it has and picks the ones a request needs.
Authorize the Heartbeat account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Heartbeat actions that close it and chains as many as the request needs.
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 freeHeartbeat · Ayro
What can you do in Heartbeat without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 7 actions your agent can call on Heartbeat, straight from the live MCP connection.
Retrieve event information from the community.
Retrieve a paginated list of channels in the community.
Retrieve a paginated list of access groups in the community.
Retrieve a paginated list of users in the Heartbeat community.
Reactivate a previously deleted user by email to allow them to access the community again.
Retrieve a single group by its ID.
Retrieve a single user by their ID.
Same connection, same setup. Pick the next one your team already uses.
Creates and lists 2Chat contacts, audits the webhook subscriptions behind WhatsApp and call events, and checks remaining API quota before a run.
Confirms who a member is and which guilds they belong to, checks premium entitlements, consumes purchases, and audits slash command permissions.
Reads the message log behind a delivery question, checks domain verification and API quota, and provisions SMTP users, tokens, and event webhooks.
Reads back what happened on a call, places outbound callbacks, keeps voice agent knowledge bases current, and batch tests an agent before it ships.
Creates and updates contact records, finds the thread a customer means with its channel and status, and keeps inboxes, labels, and webhooks accurate.
Receives real-time WhatsApp message events and processes the deliver and read acknowledgments that follow, validating the webhook token on each payload.

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