1. UPI donation → instant thank-you and receipt
A supporter donates over UPI, and today a staffer eventually notices it on the dashboard, drafts a receipt, and sends a thank-you by hand — slowly, and receipts get missed at campaign volume.
Trigger: Webhook (Razorpay UPI donation.captured)
How the workflow runs
- Trigger
Donation captured. A Webhook trigger receives the Razorpay UPI donation event the instant the money lands.
- Condition
Verify amount & signature. A Condition node checks the amount and validates the payment signature before anything runs.
- Agent
Draft receipt + thank-you. An Agent node generates a branded donation receipt and a warm thank-you in the donor's language.
- Approval
Finance signs off the receipt. An Approval node holds the tax receipt for a human to confirm — anything financial is never issued automatically.
- Output
Thank the donor on WhatsApp. On approval, an Output node sends the receipt and thank-you on WhatsApp (or Email) within moments of the gift.
- Tool (MCP)
Log to the donor CRM. A Tool (MCP) node records the donation against the donor's record. There's no first-party CRM connector — it's written via MCP.
Channels & connectors
- Webhook (Razorpay UPI)
- Approval / HITL
- Tool (MCP → donor CRM)
Outcome
Every donor is thanked and receipted promptly and the gift is logged automatically — with a human confirming the financial document.
Why it helps
Removes the manual 'did a donation come in?' check and the receipts that slip at volume, while the money/receipt step stays approval-gated.
Build spec
1 agent — 1 agent drafts the receipt + thank-you; verification, the finance Approval and the CRM write are workflow nodes.
System prompt (paste-ready)
You are a donations assistant for {{organization}}. Given a verified UPI donation {amount, donor_name, language}, write a warm thank-you in the donor's language and a clean donation receipt (receipt no., amount, date, and 80G/tax details only if present in the record). Never state a donation was successful unless the input is marked verified=true. Do not invent tax-exemption details or amounts — use only the fields provided. Prepare the receipt for finance; do not present it as issued until it is approved.MCP connectors
- Razorpay UPI — inbound via Webhook trigger
- Donor CRM — via a Tool (MCP) node (no first-party connector)
- WhatsApp + Email — send channels
Built-in tools
- http_request (fetch the donor record for the receipt)
Guardrails
- Signature + amount verification at the Condition node before anything runs — stops spoofed donation webhooks
- Idempotent on the Razorpay payment_id — a retried webhook never double-receipts or double-thanks
- The tax receipt is never issued without the finance Approval node
Output & delivery
On verify, the agent drafts the receipt + thank-you → finance confirms the tax receipt at the Approval node → an Output node sends it on WhatsApp/Email → a Tool node logs the donation against the donor's record in the CRM via MCP, keyed idempotently on the payment id.