Kapso
Kapso provides APIs for WhatsApp messaging, customer and contact management, broadcasts, workflows, and serverless functions.
Integration
- Vendor
- Kapso
- Category
- communication
- Auth
- API_KEY
- Tools
- 10
- Composio slug
kapso
Tools
- Get Function
Retrieve one Kapso serverless function's code, runtime configuration, deployment status, and computed URLs without invoking or changing it.
- Get Phone Number
Retrieve one Kapso WhatsApp phone-number configuration by its Meta phone number ID.
- Get Phone Number Health
Run Kapso's live checks for one WhatsApp phone-number configuration and return its body-level health status and individual check results.
- Get Workflow
Retrieve one workflow's metadata, full graph definition, or available variables without executing or changing it.
- List Conversations
List one page of WhatsApp conversations by recent activity, with filters for phone number, status, assignment, and activity time range.
- List Customers
List Kapso project customers and filter them by name, external customer ID, or creation time. Returns one page and a continuation cursor.
- List Functions
List serverless functions configured in the Kapso project, including runtime and deployment state, without returning function source code or invoking any function.
- List Messages
List one page of WhatsApp message history project-wide through Kapso Platform or for one phone number through the Meta-compatible proxy. This tool only reads history and never sends messages.
- List Phone Numbers
List WhatsApp phone-number configurations in the Kapso project, with filters for account, customer, messaging state, and display name.
- List Workflows
List project workflows and filter them by lifecycle status, name, or creation time. This read-only action does not execute a workflow.
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Kapso.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Kapso tools in chat.
What teammates see: by default, memories from Kapso are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.