Industry workflow recipes
Real, buildable automations for every industry — each one maps 1:1 to VegaDūta's workflow nodes, channels and connectors, with the guardrails, budgets and human approvals that make them safe to run in production.
How to read a recipe
Every recipe is one workflow: a Trigger starts it, a chain of nodes does the work, and an Output delivers the result on a real channel. Hover any block below to see what it does — each one is a node you can drop into the Workflow designer:
Design principles
Every recipe below holds to the same tenets — the ones a reviewer would hold any production agentic workflow to. They are what make these safe to run and cheap to scale, not just clever demos.
Ground, don't guess
Answers come from the Knowledge base with citations. Low confidence escalates or defers to a human — a confident wrong answer is the failure mode to design out.
Humans own consequential calls
Money, safety, legal, clinical, credit and data-changing actions pass an Approval node. Agents propose and prepare; a person decides.
Tier your models
Cheap/fast models by default, premium only on demand. The agent that runs most often must be the cheapest — that single choice dominates cost at scale (cost routing).
Budget every agent
Per-agent tool-call and token caps, plus bounded loops, make cost predictable and stop a runaway before it starts.
Least privilege & separation of duties
Each agent is scoped to its own tools and Knowledge. Routers route, specialists act, critics critique — no agent holds more power than its job needs.
Idempotent & safe to retry
Keyed by a stable id (payment, order, item) so a re-run or a duplicate webhook never double-charges, double-sends or double-counts.
Observable & audited
Every routing decision, approval, model tier and tool call is logged — so you can prove what happened and tune cost against real data.
Compose, don't copy
Shared logic (KYC, PII redaction, payment verification) lives in one versioned sub-workflow every workflow reuses — fix it once, everywhere inherits it.
Fail gracefully
Fallback provider/model on an outage; degrade to a human, never to a wrong answer. Resilience is a design choice, not an afterthought.
Meet users where they are
WhatsApp/voice/email on the channel they already use, in their own language (Sarvam covers 22+; ElevenLabs speaks back) — reach beats a portal nobody opens.
Which pattern should I use?
Match the situation to the orchestration pattern — and don't over-build. One good agent beats five mediocre ones; reach for routing, parallelism or reflection only when the job actually needs it. The featured Advanced multi-agent patterns section builds each of these out in full.
| If you're… | Use this pattern |
|---|---|
| One clear task, one domain | Single agent — Trigger → Agent → Output |
| Many domains; each message belongs to one | Supervisor → specialists (route-to-one) |
| Gather from many sources, then decide | Parallel fan-out → aggregator (+ guardrail agent) |
| Output must clear a quality / accuracy bar | Generator ↔ critic (reflection, round-capped) |
| Thousands of items — too big for one context | Map-reduce — Loop/Parallel (map) → reduce |
| The same step is reused across workflows | Sub-workflow library (build once, govern centrally) |
| Mixed difficulty and cost-sensitive | Cost-tiered escalation — cheap → premium on demand |
| Any money / legal / clinical / data-changing action | Add an Approval node — always, regardless of pattern |
Accounting & CA / CPA firms
2 recipesChase filing documents at every deadline and onboard clients with clean KYC — while a qualified accountant stays the one who reviews and files.
Open the dedicated pageSolar & renewable-energy installers
2 recipesQualify enquiries, book site surveys and catch underperforming inverters — with a human on every quote and every chargeable visit.
Open the dedicated pageAutomotive & dealerships
2 recipesBook test drives, chase service due dates and answer parts enquiries — before a rival dealer calls back.
Open the dedicated pageTelecom
2 recipesPlan changes, complaint resolution, KYC collection and outage notices — multilingual, with billing decisions gated.
Open the dedicated pageAviation & airlines
2 recipesRebook disrupted passengers, log baggage claims and answer check-in questions — in the passenger's own language, before the queue forms.
Open the dedicated pageMedia, entertainment & OTT
2 recipesHandle subscriber support, moderate what viewers upload and win back cancellations — at streaming scale, with humans on the calls that bind.
Open the dedicated pageJob seekers & career growth
4 recipesScreen postings against your real must-haves, tailor only where it's worth it, keep the tracker honest and practise out loud — without a single invented line on your CV.
Open the dedicated pagePersonal finance & document admin
4 recipesGet renewals, warranties, tax papers and forgotten subscriptions out of the Downloads folder and onto a dated timeline — organised and reminded, never advised, and never paid without your click.
Open the dedicated pageSupervisor routing, parallel research and cost-tiered escalation — with the budgets and guardrails that keep genuinely multi-agent flows safe AND cheap.
Open the dedicated pageAutomate ad-spend decisions, lead follow-up and reporting across Google/Meta Ads.
Open the dedicated pageAnswer, understand and speak back on live calls — in the caller's own language.
Open the dedicated pageTurn a UPI payment event into instant confirmation, fulfilment and reconciliation.
Open the dedicated pageReady to build one?
Every recipe above drops straight into the visual Workflow designer — start from a Trigger and wire up the nodes.
