Read Botpress workspaces, bots, and usage, then make changes as approved steps
Connect Botpress and your agent can answer questions about workspaces, bots, and the integrations and plugins they depend on. It reads account details, quota completion, and per-bot usage on request. Changes — creating a bot, adding an integration, sending a message into a conversation — are previewed and held for approval by default. Authentication is by API key.
53 tools: 36 read, 17 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Botpress 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 botpress_charge_workspace_unpaid_invoices, botpress_create_admin_integration, botpress_create_admin_workspace, botpress_create_bot, 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 Botpress — 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.