Webhooks & payment triggers

Wire Convo360 into the rest of your stack: push events out, pull events in to continue a conversation, and fire flows when a payment lands.

Outbound webhooks

Under Webhooks, subscribe a URL to events (new message, call ended, lead updated…). Convo360 POSTs a signed payload to your endpoint so your systems stay in sync. The delivery log shows every attempt, payload and response.

Inbound webhooks — run a flow

Create an Inbound Webhook to get a unique URL. When a third party (a payment page, a form, a shipping tool) POSTs to it, Convo360 matches the customer and runs a flow to them — mapping payload fields into flow variables.

Payment triggers (Razorpay)

With Payment Triggers you connect your own Razorpay: when you receive a payment, Convo360 automatically sends the payer a WhatsApp flow — a receipt, thank-you or upsell.

  1. Create a trigger and copy its webhook URL.
  2. In Razorpay → Settings → Webhooks, add the URL, subscribe to payment.captured, and set a signing secret.
  3. Paste that secret into the trigger, pick the flow, and save.
🔒 Every payment webhook is HMAC-verified with your own secret and de-duplicated, so a payer is never messaged twice for one payment. Payment details are available in the flow as {{payment_amount}}, {{payment_email}}, {{payment_contact}} and more.

The REST API

Everything you do in Convo360 can be done from your own software through the REST API: send WhatsApp templates, start and track broadcasts, place AI calls and fetch their transcripts and recordings, create and edit flows, read and reply in the inbox, and manage contacts, groups, leads and appointments.

  • Who has it. The API is included in the Business plan. It is not available during the free trial: subscribe first. On Starter or Pro, open API Keys and press Add API module: ₹999 a month plus GST, paid from your wallet. It renews each month from the wallet; you can stop renewal at any time and it keeps working until the paid month ends. If the wallet cannot cover a renewal you get an email three days before, and the API stops on the renewal day.
  • Keys. Under API Keys, create a key and choose what it may do (for example only "Send messages and WhatsApp templates"). The key is shown once. Send it as Authorization: Bearer ak_…. Each key allows 120 requests a minute.
  • Reference. Every endpoint, with its fields and the permission it needs, is in the API reference. Anyone can read it.
  • Trying it. Signed in, with the API active, press Test the API on the API Keys page: the same reference opens with Try it out, against your live workspace. Anything you send from there really happens.

Frequently asked questions

Can a payment trigger a WhatsApp message automatically?
Yes. Connect your Razorpay under Payment Triggers; when a payment is captured, Convo360 sends the payer a WhatsApp flow (receipt, thank-you or upsell). It's HMAC-verified and de-duplicated so the payer is never messaged twice.
What's the difference between inbound and outbound webhooks?
Outbound webhooks POST events from Convo360 to your systems. Inbound webhooks give you a unique URL that a third party POSTs to, which then runs a flow to the matched customer.
Which payment gateways are supported for triggers?
Razorpay today. Other gateways can be added on request; the same flow-trigger mechanism applies.