It plugs into what you already run
A conversation platform that cannot tell anything else what happened is a silo with good manners. This is the wiring: a deal created, an order paid, a booking rescheduled — delivered to your endpoint, signed, and retried until you take it.
- Webhooks on real events
- A REST API
- You choose what fires
Your other systems, told what happened
- Sends forty events to endpoints you choose — deals, quotes, orders, bookings, calls, campaigns, opt-outs, invoices and more.
- Signs every delivery and gives it an idempotency key that is stable across retries, so you have a ready-made dedup key.
- Retries eight times over roughly ten hours, then parks the delivery where you can see it and replay it yourself.
- Mints API keys with a fixed scope, shown once, revocable, and never widened in place.
- Accepts inbound calls from your systems, so a booking your back office confirmed comes back and updates the record.
- Lets you define an action your assistant can take mid-conversation — it collects the fields, the platform validates them, and your endpoint is called.
- Keeps every connector’s credential encrypted and rotatable in one place, with a dry-run test and a delivery log.
Set up once, then it runs
- Save your endpoint as a named connector under Integrations, with its credential alongside it.
- Route the events you want to that connector. Subscribing is point-and-click.
- Verify the signature on your side, answer 2xx within ten seconds, and process afterwards.
- Order by the event’s own timestamp and dedupe by its id — delivery is at-least-once and ordering is not guaranteed.
- For the other direction, create a hook and have your system sign its call the same way.
Want to see this doing your job, with your prices?
Ask on WhatsAppThe things this does not do
Every product page in this market lists capabilities. This is the other half. If one of these is a dealbreaker, we would much rather you found out on this page than in month two.
- This is not a general read-write API for your account. The key scopes are a closed set — trigger a call, notify, read events, administer hooks — and there is no CRUD API over contacts, deals or conversations.
- A key’s scopes are fixed when it is minted. Widening a live credential in place is how scope creep happens invisibly, so you mint a new key instead.
- Delivery is at-least-once with no ordering guarantee. If your handler is not idempotent, you will double-process something eventually.
- Your endpoint has ten seconds. Redirects are not followed, and a slow handler becomes a retry rather than a longer wait.
- Inbound and outbound sign differently today. Outbound signs the body; inbound signs the timestamp with the body. An integrator writing the receiving side implements what the contract specifies, and the contract says so explicitly.
- There is no live lookup into your systems to decide who a caller is. Contacts sync ahead of time; a mid-conversation call to your endpoint is a deliberate action you configured, not something the identity layer does.
- Generic REST connectors, actions, hooks and API keys are one product. They arrive together on your plan or not at all.
What people ask us
Can I pull my data out through the API?
Not through this. The scopes cover triggering calls, notifications, reading events and administering hooks — there is no general read API over your contacts or conversations. What you can do is receive every event as it happens and keep your own copy, which for most integrations is the better shape anyway. For a one-off extract, reports export a full filtered CSV.
What happens if my endpoint is down?
We retry eight times over about ten hours, backing off as we go. After that the delivery is parked as failed and sits on the Integrations screen until you replay it. Nothing is silently dropped, and an accepted event survives a restart on our side.
Does this work with n8n, Make or Zapier?
Yes — they are ordinary HTTPS endpoints as far as we are concerned, and they are the shortest path if you would rather not write a receiver. Point a connector at the webhook URL they give you and route your events to it.
Can my assistant call my system during a conversation?
Yes, as a defined action. You declare the fields it needs; the model collects them naturally, the platform re-validates them server-side, and your endpoint is called with the customer’s explicit confirmation on record. The model never gets to supply the address or skip the validation.
What it works alongside
- Contact sync Kooday pulls contacts from your own REST endpoint on a schedule, tags what the sync owns, and deactivates what you deleted upstream — so your lists are live rather than a stale export.
- Catalogue & orders Enter what you sell as structured entries and the assistant looks the price up as the customer asks — shows it as a card on WhatsApp and web chat, builds a quote, and takes the order.
- Sales pipeline Enquiries become deals on a board automatically, the assistant advances them on evidence and writes down why, and only a person ever closes one.
Would this work for your business?
Message us and say what your week actually looks like. You will be talking to our own assistant — the thing this page describes, doing the job on our side of the conversation.
Plans from ₹99/month.