VegaDūtaTutorial · Automation
How to create an automated workflow
This tutorial walks you through building an automated workflow in VegaDūta: a multi-step process that runs on its own, triggered by a webhook or an incoming message, with AI agent steps and human approvals where you want them. You can start from one of more than 240 ready-made recipes or from a blank canvas, test the draft with pinned data before any live trigger touches it, and pause a run for a person wherever you choose.
By the VegaDūta team · Last updated
Step by step
Start from a recipe or a blank canvas
Browse the recipe library at /help/workflow-recipes — more than 240 recipes organized into about 90 industries — and pick one close to your process, or open a blank canvas in the workflow builder. Recipes are editable, not fixed.
Choose a trigger
Decide what starts a run: a webhook call from another system, or an incoming message on any of 11 channels, including WhatsApp, Telegram, and email. One workflow, one trigger; you can build sibling workflows for other entry points.
Add the nodes
Drag in the steps: agent nodes that think and act, condition nodes that branch, knowledge nodes that retrieve from your documents, plus code, loop, parallel, and sub-flow nodes for more involved logic — 21 node types in all. Connect them in the order the work should flow.
Pass data between steps with expressions
Fields on a node accept expressions that read the trigger payload and earlier nodes' outputs. The field previews the result as you type, and the lint panel lists problems before you run. The full syntax is documented at /help/workflow-expressions.
Pin an output while you build
Test a step, then choose Pin output on it. Draft runs and step tests now use that saved output instead of running the node again, so you can build the steps after a slow or costly node without calling it each time. A pinned node shows a Pinned badge; Unpin removes it. Live runs never use pins.
Add an approval node where a human should sign off
Anywhere the workflow is about to do something consequential — send an external message, change a record — insert an approval node. The run pauses there until a person approves or rejects, then continues down the matching branch.
Run the draft and watch the execution
Run the draft and watch it execute step by step. If any nodes are pinned, the run is labelled as a draft run that used pinned data, so a green result is not mistaken for a real end-to-end run. A run that reaches an approval node is parked there and continues from that node once someone decides. When the draft behaves, promote the version to production; webhooks, schedules, and channel triggers run the production version.
Share it if you want to
A workflow can be shared with a one-tap public link, letting someone outside your console kick off a run. Keep approval nodes in place on shared workflows so public triggers still pass through your sign-off.
Troubleshooting
When a workflow does not behave, look at the run history before editing the graph.
- A run stuck 'waiting' is usually parked at an approval node — check the approvals queue.
- A trigger that never fires is usually a channel not yet connected, or a webhook URL not yet called by the other system.
- Test condition branches with runs that deliberately take each path; an untested branch is where surprises live.
Frequently asked questions
What can trigger a workflow in VegaDūta?
A webhook call from any external system, or an incoming message on any of 11 supported channels — including WhatsApp, Telegram, and email. That means a customer message can start a full multi-step process, not just a chat reply.
Can a human approve a step before the workflow continues?
Yes. Insert an approval node at any point and the run pauses there until a person approves or rejects it. The paused state is stored on the run record, and the run continues from that node once a decision arrives.
Can I test a workflow without calling every step for real?
Yes. Pin a node's output and draft runs use the saved data instead of running that node. The run summary states how many nodes were pinned. Live runs from webhooks, schedules, channels, and share links always run every node.
Do I have to build workflows from scratch?
No. There are more than 240 ready-made recipes, organized into about 90 industries, at /help/workflow-recipes. Pick the closest one, then edit its triggers and nodes to fit your process — a recipe is a starting point, not a locked template.
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.
