What Is A Workflow?
Workflows are reusable automation templates that define:- What tasks to perform
- How data flows between tasks (edges)
- When each task runs (based on dependencies)
Tasks
Individual steps like AI processing, human reviews, data imports, and custom code.
Edges
Connections that define how data moves between tasks and the order they run.
Variables
Named inputs and outputs that carry data through the workflow.
Workflow Lifecycle
Every workflow goes through two states:| State | What it means | Can run jobs? | Can edit? |
|---|---|---|---|
| Draft | You’re still building and testing | No | Yes |
| Active | Ready for production use | Yes | No |
Jobs can only run on active workflows. If you use sub-workflows, they must also be active and in the same workspace.
Activating A Workflow
Click Activate in the Builder after testing in preview mode. The workflow is now locked and ready to run jobs.Workflow Structure
Data moves through your workflow via connections between tasks:- Connect outputs to inputs: Link what one task produces to what the next task needs
- Automatic ordering: Tasks wait for their inputs before running
- Required inputs: A task won’t start until all its required inputs are ready
Running Workflows
Two Ways To Run
| Method | Where | When to use |
|---|---|---|
| Preview | In the Builder | Testing before you activate |
| Job | Jobs page or API | Production runs with full tracking |
Sub-Workflows
The Execute Workflow task lets you run another workflow inside yours:- The sub-workflow’s inputs and outputs connect to your main workflow
- Both workflows must be active and in the same workspace
Example Workflows
Opus includes a templates library with over 30,000 ready-to-use workflows. Click Templates in the left navbar to browse the collection. You can filter by industry to find workflows built for your specific use cases—a great way to learn how others structure quality workflows and get a head start on your own.Best Practices
Validate inputs early
Add a check at the start to catch bad data before it causes problems downstream.
One action per task
Each task should do one thing well. Combining actions makes workflows harder to debug.
Keep tasks independent
Minimize dependencies so you can update tasks without breaking others.
Separate review from action
Don’t combine review and action in one task. Keeping them separate aids debugging.
Output only what matters
Only emit data you need for monitoring. Too much output hides what’s important.
Limit parallel tasks
Run no more than 3 heavy tasks at once. Mix parallel and sequential steps.
Break up long operations
Use sub-workflows to split complex operations into smaller, reusable pieces.
Test integrations in preview
Validate credentials during Builder preview—don’t wait until production.
Add human review where needed
When accuracy matters, include Human Review tasks for accountability.