Trusted by 50,000+ developers worldwideLook up an order, book a slot, or update your CRM in the middle of a WhatsApp conversation. Write the logic in JavaScript, and Kapso runs it for you.
A function sits between the conversation and your systems. The workflow calls it, it calls your API, and the answer goes back to the customer.
Write it once and use it wherever a conversation needs it.
Run it in a workflow and use what it returns in the next message.
Let it decide which path the conversation takes next.
Give your agent a tool it can call when it needs your data.
Call it from anywhere with a URL, private or public.
Every project gets a key-value store and a SQL database bound to its functions. Secrets are encrypted and never shown again.
See what called each function, what it got, what it returned, and how long it took. It's all in Kapso Logs too.
Search them in Logs →On Cloudflare Workers. Kapso wraps your code, calls handler(request, env), and gives each project its own KV namespace and D1 database.
Add them as secrets on the function page after you deploy it. Secrets are encrypted, never shown again after you save them, and your code reads them as env.NAME.
Yes. A deployed function has an invoke URL, https://api.kapso.ai/platform/v1/functions/{function_id}/invoke. It is private by default and needs your X-API-Key header. Make the endpoint public to call it without a key.
Yes. Add it as a function tool on an agent. The agent decides when to call it, and your handler reads the arguments it chose from body.input.
Write a handler, deploy it, and attach it to a workflow in minutes.