Workflows
A workflow runs a set of steps whenever something happens: “when a new lead is created, wait two days, then send a follow-up.” Steps can call an agent, send an email, change CRM data, branch on a rule, wait, ask for approval, or call another service. Agents are optional.

Workflows (https://10ex.ai/workflows ) lists every workflow in tabs: Active, Drafts, Paused and All. Each row shows the name and version, who owns it, its trigger, how many steps it has, and how many times it ran in the last 7 days. The top of the page shows how many workflows are active, runs in 7 days, drafts and the average number of steps.
Two switches and buttons on a row are worth knowing:
- Run (play button): run the workflow by hand.
- Email me when a run fails: a switch per workflow. It controls only failed-run alerts.
Start from a template
Click Templates on the Workflows page for ready-made workflows grouped by category. Open one to see its steps, then install it. The install gives you your own copy to edit. Examples:
| Template | What it does |
|---|---|
| Welcome new leads | When a lead is created, send a welcome email. |
| Two-step lead nurture | Send an intro, wait two days, send a follow-up. |
| Prospect, verify, enrich | Prospector finds leads, Lead Verifier checks each one, Lead Research enriches the verified ones. |

Templates that use an agent pick your workspace’s own copy of that agent.
Can’t find what you need? Click Request custom on the templates page. Describe the workflow and the 10ex team builds it. The request also appears in Settings → Support.
Build a workflow
Click New workflow on the Workflows page, or open an existing one. The editor is a canvas where steps are cards connected top to bottom.

- Add a trigger. Every workflow needs one.
- Add steps from the library on the side. Search by name, or browse by group.
- Connect each step to the next by dragging between handles.
- Configure a step by opening it. Fill in its Parameters; the Settings tab holds the step’s name, what to do On error (stop, or continue to the next step), retries, a timeout and each-item mode; the Data tab shows what the step received and, after a test, what it returned.
- Test a step with the test button on its card, or Run the whole workflow.
- Save, then switch the workflow to Live.
A warning triangle on a card means a required field is empty or the app it uses isn’t connected. Connect it in place from the step, or in Settings → Integrations (see Integrations). You can configure a step first and connect before going live.
Hover a card for quick actions: run once, configure, test step, duplicate, delete. The wand button in the canvas controls tidies the layout.
A workflow can have up to 100 steps, and must have at least one trigger.
Triggers
| Trigger | Starts the workflow when |
|---|---|
| Manual | Someone clicks Run. |
| Schedule | A time you set, with presets or a cron expression. |
| Webhook | Another system sends a POST to the workflow’s webhook URL. See Trigger a workflow from a webhook. |
| Form submitted | A web form or an ad lead form is submitted. Narrow it to specific forms in the Triggers panel. |
| In-app events | Something happens in your CRM: New lead created, Lead status changed, Lead added to segment. Filters let you narrow by source, status or segment. |
Manage a workflow’s triggers from Triggers in the editor header: turn each on or off, copy the webhook URL, or rotate its token.
Steps
| Group | Steps |
|---|---|
| Agents | Agent runs an agent from your library. Pick one and its inputs appear as a form, with what it returns shown below. LLM generates or transforms text with AI. |
| Actions | Action sends, launches or publishes through a connected app: send an email, launch an ad, publish a post. For Send email you choose which connected inbox sends it, and see a live preview of the email. |
| Data | CRM / Knowledge reads or writes CRM and knowledge data. Tool runs one tool, such as an enrichment or a search. Set Fields, Limit, Remove Duplicates, Split Out, Sort, Aggregate reshape the items passing through. |
| Logic | If and Switch branch on rules (the outputs are labeled true/false or by case). Filter keeps matching items. Merge joins branches, by appending or by combining like a join. Wait pauses for a set time. Approval pauses for a human decision. |
| HTTP | HTTP Request calls any outside API. |
| Code | Code runs sandboxed JavaScript. |
To use data from an earlier step, reference it in a field. A step only sees data from steps connected before it, and an unconnected step says “No input connected.”
To hold a step until someone approves, see Approval steps.
Publish and go live
Use the Live / Draft switch in the editor header. Going live saves a version and arms the triggers. Switching back to draft pauses the triggers so nothing fires.
Versions lists the saved versions. Restore replaces your current draft with an older version, so unsaved edits are lost. It asks you to confirm first.
Watch a run
Open Runs in the editor to see past runs, filter by status (Needs approval, Waiting, Running, Failed, Done, Cancelled) and act on them without opening each one:
- Approve or Reject a run that is waiting for a decision.
- Resume now on a run that is waiting on a Wait step.
- Retry a failed run.
Click a run to replay it on the canvas. Steps show their status as they go, and the lines between them show how many items passed.
Every run emails the company owner when it starts and again when it ends, in the same thread.
Make an agent run recurring
When an agent finishes work in the CMO chat, its result card has a Make this recurring action. It drafts a workflow from that run and opens the editor. The draft stays inactive until you switch it to Live, so nothing fires by surprise. For schedules on a single agent, you can also use the agent’s own schedule. See Agents.
Limits worth knowing
- The webhook URL and the approval page are public links protected by a token, and they are rate limited.
- A step that sends, launches or publishes follows your approval rules. The Skip approval for this step option on an Action step can only be changed by an owner or admin. See Guardrails.
- Creating and editing workflows needs a role that can write workflows. Viewers can look but not change anything. See Roles and permissions.