Kapso
for LuumenAI
Read WhatsApp numbers, conversations, workflows, and functions in Kapso
Connect Kapso with an API key and ask about your messaging stack in plain terms. List phone-number configurations and run KAPSO_GET_PHONE_NUMBER_HEALTH when delivery looks off. Page through conversations and messages, check workflow definitions, and review serverless function runtime and deployment state. Read-only, so nothing changes in Kapso.
The Kapso toolbox
10 tools, all read-only. They answer instantly, and every call is logged.
- ReadGet FunctionRetrieve one Kapso serverless function's code, runtime configuration, deployment status, and computed URLs without invoking or changing it.
- ReadGet Phone NumberRetrieve one Kapso WhatsApp phone-number configuration by its Meta phone number ID.
- ReadGet Phone Number HealthRun Kapso's live checks for one WhatsApp phone-number configuration and return its body-level health status and individual check results.
- ReadGet WorkflowRetrieve one workflow's metadata, full graph definition, or available variables without executing or changing it.
- ReadList ConversationsList one page of WhatsApp conversations by recent activity, with filters for phone number, status, assignment, and activity time range.
- ReadList CustomersList Kapso project customers and filter them by name, external customer ID, or creation time.
- ReadList FunctionsList serverless functions configured in the Kapso project, including runtime and deployment state, without returning function source code or invoking any function.
- ReadList MessagesList one page of WhatsApp message history project-wide through Kapso Platform or for one phone number through the Meta-compatible proxy.
- ReadList Phone NumbersList WhatsApp phone-number configurations in the Kapso project, with filters for account, customer, messaging state, and display name.
- ReadList WorkflowsList project workflows and filter them by lifecycle status, name, or creation time.
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.
No. Every one of the 10 tools LuumenAI has for Kapso is read-only, so it can answer questions from Kapso but cannot change anything in it. Reads are not gated — they answer immediately, and each one is recorded on the audit trail with the actor and the result.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Kapso 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 Kapso to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.