Flows
A flow is a recipe you build once and run whenever you need it: take this data, ask an agent to write something, then save the result or send it by email. Instead of repeating the same request every week, you draw the steps once.
In the app, flows appear as Automations. This documentation calls them flows.
What a flow is made of
Section titled “What a flow is made of”A flow is a diagram of nodes joined by arrows. Data goes from one node to the next. There are five kinds of node:
| Kind | What it does | Examples |
|---|---|---|
| Input | Asks for the data the flow needs when it runs. | Text, number, choice, structured data, file, image, video. |
| Data | Prepares or reshapes data. | Reuse a fixed text (a catalog, a style guide), extract one field from the data. |
| AI | Calls an AI model or one of your agents. | Build a prompt, write a text, classify a message, return structured data, ask a departmental agent. |
| Logic | Controls the path. | A condition (do one branch or the other), a wait of up to 25 seconds. |
| Output | Delivers the result. | Save a file (Markdown, text, JSON, CSV or HTML), send an email. |
Two examples:
- Weekly KPI report: an input node takes the week’s numbers, an AI node writes the executive summary, and an output node sends it by email.
- Reply to a review: an input node takes the review, an AI node drafts the answer in your tone, and an output node saves it as a file for you to check.
You can also start from one of the 11 ready-made templates (commercial proposal, service contract, meeting summary, follow-up email, job offer, KPI report, message classifier, review reply, social post and more). Templates are read-only: press Use template to get your own copy and change it.
Running a flow
Section titled “Running a flow”A flow starts in four ways:
- By hand, with the Run button in the flow screen, or by asking Amadeus to run it in the chat.
- On a schedule: at the time or frequency you choose.
- By webhook: when another tool calls the flow’s address.
- By a Shara event: when a contact is created in the CRM, a task is completed, an approval is decided or a WhatsApp message arrives.
If the flow has inputs, the app asks you for the values first. If a required value is missing, nothing runs and nothing is spent.
A run is synchronous: it has a limit of 30 seconds in total. The result appears in the run results panel, node by node: how many nodes went well, failed or were skipped. When a condition sends the flow down another branch, the nodes that were not used are shown as skipped and are not charged.
Triggers
Section titled “Triggers”A flow can start by itself: on a schedule, when a webhook arrives or when one of the Shara events listed above happens. It runs just as it does by hand, with the same time limit and the same quota checks.
What a flow costs
Section titled “What a flow costs”AI nodes spend STU like any other agent work. A flow goes through the same checks as the chat before it spends anything: an active subscription, your quota limit and the spending caps.
Each AI node asks for a model alias (Prelude, Sonata, Symphony or Concerto). If your plan does not include that alias, the flow does not fail: it uses the closest lower one. For example, a node set to Symphony on the Pro plan runs with Sonata, and on First, which only includes Prelude, every node runs with Prelude. Outside your business hours, the cloud plans also switch to saving mode, as in the chat. The reason is written in the node log.
Who can do what
Section titled “Who can do what”| Action | Who |
|---|---|
| See flows shared with them, and the templates | Everyone. |
| Create, edit, run and share a flow | Every role except Viewer. |
| Delete a flow, or change who it is shared with | The person who created it, and owners and administrators. |
Viewers can look at flows but not change or run them. The full list of roles is in Roles and permissions.
A flow is private to its creator until they share it. They can share it with the whole company, or with specific people, roles or departments.
Limits and good practice
Section titled “Limits and good practice”- Keep each flow short and focused. A run that exceeds 30 seconds is stopped.
- Put the wait node only where you need it: it counts toward the 30 seconds.
- The email node sends the message when the flow reaches it, so test it with your own address first.
- Review the run results after the first runs. They show what each node received and produced.
Related: Agents, Connectors and Approvals and audit.