Platform · Automation
Workflow automation that survives failure
VegaDūta runs workflows on Temporal, the same durable-execution engine used for mission-critical automation at scale. A run survives restarts, retries failed steps, and can pause on a human-approval node until you say yes. You compose workflows from 13 node types — including agent, condition, loop, code, and parallel — and trigger them from 11 channels, from WhatsApp messages to plain webhooks.
If you would rather not start from a blank canvas, around 90 ready-made industry workflow recipes cover common jobs, and any workflow can be shared with a one-tap public link.
13 node types to compose from
A VegaDūta workflow is a graph of typed nodes, each doing one job. Agent nodes hand a step to an AI agent, condition nodes branch, loop and parallel nodes control flow, and code nodes run custom logic. Sub-workflow and supervisor nodes let larger automations delegate to smaller ones.
- Trigger, agent, knowledge, condition, approval, output
- Device control, tool, loop, code
- Sub-workflow, supervisor, parallel
Triggered from 11 channels
Workflows start from real-world events, not just cron. A customer message on WhatsApp, Telegram, SMS, Messenger, Instagram, Slack, Discord, or X can kick off a run, as can a phone call, an email, or an authenticated webhook from your own systems. The same workflow can serve every channel you connect.
Retries you configure, not a fixed policy
Every workflow carries its own execution limits rather than inheriting one platform-wide policy: how many retry attempts a failed step gets (anywhere from 0 to 5), the maximum number of steps a single run may take, and a per-step timeout. Both execution engines read the same per-workflow value, so the behaviour does not change depending on how a run happened to be dispatched.
- 0–5 retry attempts per workflow — set 0 for a step you never want repeated
- A step ceiling and a per-step timeout, also per workflow
- A quota rejection is never retried — it would fail identically and burn the attempt
Humans stay in the loop
Approval nodes pause a run — durably, for as long as it takes — until a person approves or rejects the step. Because Temporal persists workflow state, a run waiting on approval costs nothing and loses nothing, even across deploys and restarts. This is how VegaDūta keeps risky actions behind a human decision.
Recipes and sharing
Roughly 90 industry workflow recipes ship ready to adapt, organized by sector, so a clinic, kirana store, or agency starts from something that already works. Finished workflows get one-tap public share links. If you are comparing tools, we keep an honest comparison against n8n for India-focused teams.
Frequently asked questions
What workflow engine does VegaDūta use?
VegaDūta runs workflows on Temporal, a durable-execution engine. Runs survive process restarts, failed steps are retried automatically, and long waits — like a pending human approval — persist safely instead of timing out.
Can a workflow wait for human approval before acting?
Yes. An approval node pauses the run until someone approves or rejects it, and the paused state is durable — it survives restarts and can wait indefinitely. This is the recommended pattern for payments, deletions, and anything else you want a human to sign off on.
What can trigger a VegaDūta workflow?
Eleven channels: webhook, WhatsApp, Telegram, SMS, phone call, Facebook Messenger, Instagram, Slack, Discord, X, and email. A single workflow can be wired to several triggers at once, so the same automation answers customers wherever they message you.
Can I control how many times a failed workflow step is retried?
Yes — retries are configured per workflow, from 0 to 5 attempts, alongside a maximum step count and a per-step timeout. Both execution engines honour the same per-workflow setting. A quota-exceeded rejection is deliberately excluded from retry, since it would fail identically on the next attempt.
Do I have to build workflows from scratch?
No. Around 90 industry workflow recipes ship with the platform, covering common jobs by sector, and you adapt them rather than starting blank. You can also try the builder without signing up in the sandbox at /try.
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
