glossary · The process

Workflow router

definition

A workflow router is a single entry workflow that every new piece of work starts on: the agent triages the work, a decision picks one exit, and the matching sub-workflow runs before the router completes.

in one line: One door for new work. A decision picks the exit.

in context

Where does a workflow router fit?

Every new task. One door. In ConvOps, the agent triages the work, picks one exit, and records why.

triagewhat is this?
routefour exits
sub-workflowruns, returns
capturewhat was learned
complete
two ways to say it

What is a workflow router, in plain words?

Same idea at two depths: the plain version, then what the engine actually does.

Choosing the right process becomes a step of its own, done with the work in front of the agent.

Each exit leads to a small workflow that only handles its own kind of work.

for engineers

Owners and admins mark one template is_router. It attaches on create for tasks, bugs, initiatives and plans.

An explicit workflow on create wins. Without a router, rules match by type, area, tags and project.

the longer answer

Why does a workflow router matter?

Without a router, choosing the right process is someone's job at creation time. A person picks a template, or a rule matches on fields like type or tags. That works until the categories blur: a "task" that is really a code change needing review, a "bug" that is actually infrastructure. A router turns that choice into a step of its own, done by the agent with the work in front of it, and recorded.

The pattern has three parts. A triage step confirms what kind of work this is. A decision step offers a small number of exits, each naming the sub-workflow it starts, such as feature delivery, a code change with review, a small known task, or an operations change. After the chosen sub-workflow finishes, control returns to the router, which can run closing steps that apply to all work, like capturing what was learned.

Routers keep each downstream workflow small and specific, because none of them has to handle every case. They also make the routing auditable: the decision records which exit was taken and why, so a reviewer can see that a change went through the review path and not the quick one.

in convops

How does a workflow router work in ConvOps?

In ConvOps, a workspace can mark one workflow as its router. Owners and admins set it. When a new task, bug, initiative or plan is created, the router attaches directly; phases, goals, ideas and scheduled work keep their own matching rules. Naming a workflow explicitly when the work is created skips the router. Without a router, rules match new work to a workflow by type, area, tags and project. A router exit can also match a task field automatically, for example sending every initiative to feature delivery, so the agent decides only the cases that need judgment.

questions

What do people ask about a workflow router?

What does a workflow router do?

A workflow router takes new work, decides which process fits, and starts that process as a sub-workflow. In ConvOps a workspace can mark one workflow as its router, and the decision is a step the agent makes with the work in front of it, recorded so the chosen path can be reviewed. When the sub-workflow finishes, the router can run closing steps that apply to all work.

When should I use a router instead of matching rules?

When categories blur: a task that is really a reviewed code change, or a bug that is really infrastructure. ConvOps rules match on fields such as type, area, tags and project, while a router lets the agent judge the work. A router exit can still match a field automatically for the clear cases, such as sending every initiative to feature delivery.

Who sets the router in ConvOps?

Owners and admins of a ConvOps workspace mark one workflow as its router. It then attaches to every new task, bug, initiative or plan, while phases, goals, ideas and scheduled work keep their own matching rules. Naming a workflow explicitly when the work is created skips the router.

Which workspaces benefit from a workflow router?

Workspaces that receive many kinds of work and want each item on the right process without someone sorting it first. A ConvOps router suits mixed teams, such as engineering plus operations, because the agent judges each new task, starts the matching sub-workflow and records the choice, while owners and admins decide which workflow acts as the router.

What happens after the sub-workflow finishes?

Control returns to the router. In ConvOps the chosen sub-workflow runs on the same task until it finishes, and then the router continues at its next step. That is where closing steps that apply to all work belong, such as capturing what was learned in the workspace memory. The router completes only after them, so every item ends the same way whichever path it took.

How many exits should a workflow router have?

A small number, each naming the sub-workflow it starts. A ConvOps router might offer, for example, a sales proposal with review, a support escalation, a small known task and an operations change. Few exits keep each downstream workflow small and specific, because none has to handle every case, and the decision records which exit was taken and why, so a reviewer can check the path.