2 ready-to-build workflows

AI agent workflows for Nonprofit & NGO

Thank donors, coordinate volunteers and answer beneficiaries — approval-gated on anything financial.

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 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

  1. Trigger

    Donation captured. A Webhook trigger receives the Razorpay UPI donation event the instant the money lands.

  2. Condition

    Verify amount & signature. A Condition node checks the amount and validates the payment signature before anything runs.

  3. Agent

    Draft receipt + thank-you. An Agent node generates a branded donation receipt and a warm thank-you in the donor's language.

  4. Approval

    Finance signs off the receipt. An Approval node holds the tax receipt for a human to confirm — anything financial is never issued automatically.

  5. 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.

  6. 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)
  • WhatsApp
  • Email
  • 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 agent1 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.

2. Volunteer sign-up and coordination

Volunteer interest arrives across forms, calls and messages, and a coordinator manually collects availability, confirms slots and reminds people — so shifts go unfilled and no-shows are common.

Trigger: Webhook (sign-up form) or WhatsApp

How the workflow runs

  1. Trigger

    Volunteer signs up. A Webhook (from your sign-up form) or a WhatsApp message starts the flow per volunteer.

  2. Agent

    Capture availability + skills. An Agent node collects when they're free and what they can help with, in their language, into a clean record.

  3. Condition

    Match to an open shift. A Condition node routes the volunteer to a suitable open slot, or holds them for the coordinator when nothing fits.

  4. Output

    Confirm + remind. An Output node confirms the assigned shift and sends day-before reminders on WhatsApp/SMS to cut no-shows.

  5. Tool (MCP)

    Log to the volunteer roster. A Tool (MCP) node records the assignment in your roster/CRM system.

Channels & connectors

  • Webhook
  • WhatsApp
  • SMS
  • Sarvam (multilingual)
  • Tool (MCP → volunteer roster)

Outcome

Volunteers are matched, confirmed and reminded automatically, so shifts fill and fewer people forget to turn up.

Why it helps

Replaces the manual back-and-forth of collecting availability and chasing confirmations with a self-serve flow the coordinator only supervises.

Build spec

1 agent1 agent captures availability and skills; the shift-matching Condition, the reminders and the roster write are workflow nodes.

System prompt (paste-ready)

You are a volunteer-coordination assistant for {{organization}}. In the volunteer's language, collect their availability and the skills/tasks they can help with into a clean record {name, availability, skills, location}. Match them only against the genuinely open shifts you are given — never invent a shift or over-promise a slot. If nothing suitable is open, tell them you'll hold their details for the coordinator rather than forcing a fit. Keep it friendly and brief.

MCP connectors

  • Volunteer roster / CRM — via a Tool (MCP) node (no first-party connector)
  • WhatsApp + SMS — receive + send channels
  • Sarvam — in-language conversation

Built-in tools

  • http_request (fetch the current open shifts)

Guardrails

  • Only assigns against genuinely open shifts — no double-booking a slot or inventing one
  • Unmatched volunteers are held for the coordinator, not force-fit into an unsuitable shift
  • Scope-locked to the volunteer's own record

Output & delivery

The agent captures availability + skills → the Condition node matches to an open shift or holds the volunteer for the coordinator → an Output node confirms the assigned shift and sends day-before reminders on WhatsApp/SMS → a Tool node records the assignment in the roster/CRM via MCP.

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.

See how VegaDūta compares to n8n, Dify and BotpressWhy VegaDūta's architectureEstimate your WhatsApp API costs