Workflows
Build multi-step automations on a canvas: triggers, AI steps, conditions, tools and approvals, tested in Development and deployed to Production.
A workflow connects steps on a canvas: a hot lead comes in → AI checks the company → if it's a fit, create a CRM deal and post to Slack → otherwise send a polite email. Workflows are for things chatbot automations are too simple for.
Start
Open Workflows → New workflow and start blank or from a template: Lead qualification, Customer follow-up or Support triage.
Triggers
| Trigger | Starts a run when |
|---|---|
| Manual | Someone clicks Run. |
| Webhook | Your system calls the workflow's address. |
| Form | Someone submits the workflow's hosted form. |
| Event | Something happens in ORYVOX, e.g. a hot lead. |
| Schedule | At set times, e.g. every Monday at 9:00. |
| API | Your code calls it and waits for the answer (up to 30 s) or not. |
Webhook and form addresses come with a token and secret, shown once and rotatable.
Steps
Add steps from the library (search with ⌘F, or drag them in): AI steps and agents, tools from your integrations, knowledge lookups, conditions and switches, AI decisions ("when should AI pick this branch?"), waits, approvals and outputs. Each step has an error port for what happens when it fails.
Insert data from earlier steps with the data picker, e.g. {{leo.lead_score}}. Steps that need a person show Approval required.
Test
| Mode | |
|---|---|
| Simulate | AI and reads run; actions that change data are only simulated. |
| Execute | Every step runs for real, in Development. |
Watch each step light up as it runs, then open the run log. Test step runs a single step.
Deploy
Publish a version, then Deploy to Production. Preflight checks run first: warnings let you continue, blockers don't. Say what changed; it's kept in the version history. Switch over immediately, or gradually with a share of runs. Changes apply to new runs only.
Versions shows every published version with a diff of what changed, and lets you roll back.
Runs and budget
Runs lists every run with a step-by-step waterfall of what happened and what it cost.
The budget guard shows what one run costs, the monthly forecast and the cost by step. Set a monthly limit and a per-run limit, each as a hard stop or a warning; changes apply from the next run.
Settings
General, execution, errors and retries, data retention, notifications and access. Deleting a workflow first lists what depends on it; run history is kept for its retention period.