Read your Heartbeat community roster, and restore removed members on approval.
Connect Heartbeat and Luumen can answer questions about your community without you opening the admin panel: who the members are, which channels exist, what access groups they belong to, and what events are on the calendar. When someone who was removed needs back in, the agent looks up the account first, shows you what it plans to do, and reactivates it once you approve. Authentication is by API key.
7 tools: 6 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Heartbeat run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as reactivate user. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Heartbeat — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.