Official Meta Business Partner

Use your data
in every chat

Look 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.

How it works

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.

Your systems
Shopify, Stripe, your CRM
env.DB · project database
env.API_KEY · secrets

One function,
four places to use it

Write it once and use it wherever a conversation needs it.

  • Workflow step

    Run it in a workflow and use what it returns in the next message.

  • Branching

    Let it decide which path the conversation takes next.

  • AI agent tool

    Give your agent a tool it can call when it needs your data.

  • HTTP endpoint

    Call it from anywhere with a URL, private or public.

Storage and secrets,
already wired up

Every project gets a key-value store and a SQL database bound to its functions. Secrets are encrypted and never shown again.

env.KV
Persistent key-value storage with TTLs
env.DB
Your project database, bound as Cloudflare D1
env.API_KEY
Encrypted secrets you set on the function page
fetch()
Call any API, with standard Web APIs

Every invocation, recorded

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 →

Frequently asked
questions

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.

Ship your logic
next to your messages

Write a handler, deploy it, and attach it to a workflow in minutes.