Three Cashfree triggers start a run the moment Cashfree reports an event:

Trigger What it says Cashfree event
Payment success When a customer's payment succeeds PAYMENT_SUCCESS_WEBHOOK
Payment failed When a customer's payment fails PAYMENT_FAILED_WEBHOOK
Refund status When a refund succeeds, fails or is cancelled REFUND_STATUS_WEBHOOK

They are instant triggers — see How instant triggers work. Cashfree only sends events to an address set in its own dashboard, so you paste Bizomate's address there once.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

On Cashfree's side, someone who can manage webhooks in the Merchant Dashboard.

Before you start

A Cashfree connection — see Connect Cashfree. Bizomate checks every event with its Secret key.

Steps

In Bizomate:

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under Cashfree, select the trigger — for example Payment success. It reads Cashfree · instant.
  3. In Connection, choose your Cashfree connection.
  4. Below, One step in Cashfree says Cashfree sends events only to an address set in its dashboard. Copy this into Cashfree › Developers › Webhooks, choose the payment and refund events, and save. Bizomate checks each event with the connection's secret key.
  5. Beside Webhook address, select Copy.

In Cashfree:

  1. Sign in to the Merchant Dashboard, in the same environment as the connection — sandbox for a Sandbox (test) connection.
  2. Go to Developers, then Webhooks, and add a webhook endpoint.
  3. Paste the address.
  4. Choose the events — payment success, payment failed and refund — and save.

Back in Bizomate:

  1. Add the steps, then Publish. You can paste the address before publishing — it is made the first time an Admin or Editor opens the trigger.
  2. Make a test payment. The panel reads Waiting for the first event — Make a payment through Cashfree — in its sandbox, if the connection is Sandbox; it appears here within seconds. — then Listening — instant — Last event 10:45 · Payment success · ₹ 1,499.00.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

Payment success and Payment failed — each payment is one item:

Field What it is
orderId The order paid. Use it in Refund an order or Get an order.
paymentId Cashfree's id for the payment.
status SUCCESS, FAILED …
amount, amountText 1499, ₹ 1,499.00.
currency INR.
method How it was paid — upi, card, net_banking …
message Cashfree's message about the payment — why it failed, for a failure.
customerPhone, customerEmail The customer's phone and email.
event The Cashfree event.

Refund status — each refund is one item: refundId, orderId, status (SUCCESS, FAILED, CANCELLED), note, amount, amountText and event. The run is named Refund success · ₹ 500.00.

What happens next

  • Each event starts one run of the live version, in Production, named after it — Payment success · ₹ 1,499.00.
  • Every event is checked. Cashfree signs each one with your Secret key; one whose signature does not match is answered 401 and starts nothing.
  • Other events are ignored. The webhook in Cashfree can send every event; each trigger starts runs only for its own.

Good to know

  • One workflow, one address. Each workflow has its own address; add an endpoint in Cashfree for each.
  • A new Secret key in Cashfree makes every event fail the check until you reconnect the connection with it.
  • Switched off, events still arrive and show as the last event, but start no runs.
  • Deleting the workflow does not remove the endpoint from Cashfree. Its address then answers No workflow listens here.; remove it in Cashfree too.

If something goes wrong

What you see Why What to do
Waiting for the first event stays after a payment The endpoint is in the other environment, the event is not chosen, or the address was pasted wrongly. Check the endpoint in Cashfree against the address on the panel.
Cashfree shows deliveries failing with 401 The connection's Secret key is not the account's current one. Reconnect with the current Secret key.
Nothing has arrived yet — make one happen in Cashfree, then try again. on Output No event has arrived. Make a test payment, wait for Listening — instant, then Use the last event.