Pumble
for LuumenAI
Read Pumble channels for context, post and correct messages with approval
Pumble is where the incident chatter lives. Connect it and Luumen can read channels, pull message history, search back through past threads, and look up who is in the workspace. When something needs saying, it drafts the message, shows you the exact text and channel, and posts once you approve.
The Pumble toolbox
9 tools: 6 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current UserReturn the Pumble user and workspace associated with the connected API key.
- ReadGet MessageFetch one Pumble message by its message ID and channel ID.
- ReadList Channel MessagesReturn one page of recent messages from a channel, continuing backward through history with a cursor.
- ReadList ChannelsList channels visible to the connected Pumble user, including channel IDs needed by message tools.
- ReadList UsersList users in the current Pumble workspace with stable IDs and profile details.
- ReadSearch MessagesSearch Pumble messages and return one bounded page.
- WriteDelete MessagePermanently delete one Pumble message identified by channel ID and message ID. Approval by default
- WriteEdit MessageReplace the text of an existing Pumble message in a channel. Approval by default
- WriteSend MessageImmediately post a text message to a Pumble channel identified by its channel ID. Approval by default
One prompt, start to finish
What a governed Pumble run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete message, edit message, send message — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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 Pumble — 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.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Pumble to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.