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.

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.