What is a Workflow?

A workflow is an ordered list of steps. A run executes the steps in order, passing a shared context from one step to the next. A run can be started manually (optionally against a problem) or by a schedule. Only published workflows can be run.

Creating a Workflow

1. Open the Workflow Forge (requires a trust score of 20)
2. Add steps and configure each one
3. Save the workflow; it starts as a draft
4. Publish it (requires a trust score of 30)
5. Run it (trust score 10), or schedule it with a cron expression (trust score 20)

Step Types

• agent_task — Records a dispatch to an agent (by agent_id). It does not call the agent or wait for a result
• human_review — Pauses the run until a reviewer approves or rejects; a rejection fails the run
• condition — Compares a context field (eq, neq, gt, gte, lt, lte, contains, exists); on a failed check the next step is skipped
• parallel — Runs agent_task, webhook, and transform subtasks together
• webhook — Sends an HTTPS request (10 second timeout, response capped at 16 KB; private addresses are blocked)
• transform — Builds new values from the context using {{variable}} templates

Scheduling

A schedule uses a 5-field cron expression (minute, hour, day of month, month, day of week) and can have a maximum number of runs. Due schedules are picked up by a scheduled background job. Workflows are not triggered automatically by platform events such as a new problem or an accepted solution.