2 ready-to-build workflows

AI agent workflows for Payments & fintech (UPI)

Turn a UPI payment event into instant confirmation, fulfilment and reconciliation.

Each recipe below is expressed only in VegaDūta's real workflow building blocks — Trigger, Agent, Knowledge, Condition, Approval, Output, Tool (MCP), Voice, Device, Loop, Code and Parallel — so it maps 1:1 to something you can assemble in the Workflow designer. Consequential actions always pass a human Approval step.

1. UPI payment → instant receipt, confirmation and fulfilment

A customer pays you over UPI. Today someone manually checks the bank/Razorpay dashboard, then confirms the order and sends a receipt — slowly, and only in business hours.

Trigger: Webhook (Razorpay payment.captured)

How the workflow runs

  1. Trigger

    Payment captured. A Webhook trigger receives the Razorpay UPI 'payment.captured' event the instant money lands.

  2. Condition

    Verify amount & status. A Condition node checks the amount matches the order and the signature is valid before anything runs.

  3. Agent

    Draft the receipt & message. An Agent node generates a branded receipt and a thank-you in the customer's language.

  4. Output

    Confirm on WhatsApp. An Output node sends the receipt + order confirmation on WhatsApp within seconds of payment.

  5. Tool (MCP)

    Update order / inventory. A Tool (MCP) node marks the order paid and decrements stock in your system.

Channels & connectors

  • Webhook (Razorpay UPI)
  • WhatsApp
  • Tool (MCP → orders/inventory)

Outcome

The customer gets an instant, professional confirmation and the order moves to fulfilment automatically — day or night.

Why it helps

Removes the manual 'did the payment come in?' check and the delay before fulfilment; reconciliation happens as the money arrives.

Build spec

1 agent — 1 agent writes the receipt/message; verification and the order update are workflow nodes.

System prompt (paste-ready)

You are a payments assistant. Given a verified payment {amount, order_id, customer_name, language}, write a short, warm confirmation in the customer's language and a clean receipt (order id, amount, date, GST if present). Never state a payment is successful unless the input is marked verified=true. Do not invent order contents — use only the fields provided.

MCP connectors

  • Razorpay UPI — inbound via Webhook trigger
  • Orders/inventory — via a Tool (MCP) node
  • WhatsApp — send channel

Built-in tools

  • http_request (fetch order line items)

Guardrails

  • Signature + amount verification at the Condition node before ANY message or fulfilment (stops spoofed webhooks)
  • Idempotency on payment_id — a retried webhook never double-fulfils or double-messages
  • Agent may only confirm when verified=true; refunds are a separate approval-gated flow

Output & delivery

On verify, the agent's receipt text is sent via the WhatsApp channel within seconds, and a Tool node marks the order paid + decrements stock in the OMS via MCP — the whole thing keyed idempotently on the Razorpay payment id.

2. Refund request with mandatory human approval

Refunds are high-stakes and fraud-prone. You want them fast, but never automatic.

Trigger: WhatsApp (customer refund request) or Webhook

How the workflow runs

  1. Trigger

    Refund requested. A WhatsApp trigger (or Webhook from your support tool) starts the flow.

  2. Agent

    Assemble the case. An Agent node pulls the order, payment and reason into a one-screen summary.

  3. Approval

    Finance approves. An Approval node holds the refund until a human explicitly approves — the non-negotiable control.

  4. Tool (MCP)

    Issue the refund. On approval, a Tool (MCP) node calls the Razorpay refund API.

  5. Output

    Tell the customer. An Output node confirms the refund and timeline on WhatsApp.

Channels & connectors

  • WhatsApp
  • Approval / HITL
  • Tool (MCP → Razorpay)
  • Webhook

Outcome

Refunds are decided in minutes with a clear approver and a full trail — never issued without a human.

Why it helps

Combines speed with control: the mechanical work is instant, the money decision stays with a person.

Build spec

1 agent — 1 case-assembler agent; the finance approval and the refund call are workflow nodes.

System prompt (paste-ready)

You are a refunds case assembler. Given a refund request {order_id, customer, reason, channel}, pull the order and original payment and produce a one-screen summary {order_id, paid_amount, payment_date, refundable_amount, reason, prior_refunds, risk_flags[]}. Never state or imply the refund is approved — you only assemble the case for a human approver. Flag anything unusual (partial use, repeat refunder, amount mismatch) in risk_flags. Do not initiate the refund yourself.

MCP connectors

  • Razorpay refund — via a Tool (MCP) node, only after approval
  • Orders/payments lookup — via a Tool (MCP) node
  • WhatsApp — request + confirmation channel

Built-in tools

  • http_request (order + payment history)

Guardrails

  • No refund is ever issued without the finance Approval node — the agent only assembles, a human decides
  • The agent may not initiate the Razorpay refund; the Tool node fires only on explicit approval
  • Duplicate-request check on order_id so the same refund can't be approved twice

Output & delivery

The agent's case summary goes to the finance Approval node; on approval a Tool node calls the Razorpay refund API, and an Output node confirms the refund + timeline to the customer on WhatsApp.

Related industries

Build one of these in minutes

The sandbox gives you a live agent workspace — no account, no card. Or head back to the full catalogue and compare patterns across every industry.

Try this in the sandbox — no signupBrowse all industries
See how VegaDūta compares to n8n, Dify and BotpressWhy VegaDūta's architectureEstimate your WhatsApp API costs