Read Revolt channels for context, then post updates as approved steps
Connect Revolt and Luumen can read the channels, users, and invites your team already uses to coordinate work. It answers questions about a channel or an account without you switching windows. When it needs to post an incident update, pin a runbook link, or clear a stale message, that change is previewed and, by default, waits for your approval. Authentication is by API key.
26 tools: 12 read, 14 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Revolt 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 acknowledge policy changes, add reaction to message, block user, create sync settings, and more. 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 Revolt — 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.