Landbot
for LuumenAI
Read your Landbot agents, bots, and conversations, then act with approval.
Connect Landbot and your team can ask about bots, channels, agents, and the customers who have talked to them, without opening the builder. Luumen reads that context on request and answers right away. Changes — updating an agent, setting a status, sending a message to a customer — are previewed first and go out after you approve them.
The Landbot toolbox
13 tools: 6 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet BrandRetrieve your brand data including contact information and settings.
- ReadList AgentsRetrieve a list of agents in your Landbot account.
- ReadList BotsList all bots in your Landbot account.
- ReadList ChannelsList all channels integrated with your account.
- ReadList CustomersList customers who have interacted with your bot.
- ReadList WhatsApp TemplatesList all WhatsApp message templates available for the account.
- WriteDelete BotDelete a specific bot from your account. Approval by default
- WriteReplace AgentReplace all data for a specific agent (full update). Approval by default
- WriteReplace BrandReplace or update brand data with a full update (PUT operation). Approval by default
- WriteSend MessageSend a plain text outbound message to a Landbot customer. Approval by default
- WriteSet Agent StatusChange your agent status to online, offline, or busy. Approval by default
- WriteUpdate AgentUpdate an agent's information in your Landbot account. Approval by default
- WriteUpdate BrandPartially update your brand data in Landbot. Approval by default
One prompt, start to finish
What a governed Landbot 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.
This connection exposes write actions such as delete bot, replace agent, replace brand, send message, 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 Landbot — 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
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Landbot to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.