About dynamic workflows
A dynamic workflow is a reusable instruction for an AI agent, written in plain English and run against a set of documents. You describe the job once — what to read, what to check, what the answer should cover — and run it whenever you need it.
Write one when the work is worth writing down: something you do again and again, something the team should do the same way every time, or something you want the agent to take more care over than a single question would give it.
Where dynamic workflows live
If dynamic workflows are enabled on your account, they will appear as a sub-tab of the Workflows page, under Dynamic.
If you do not have access to dynamic workflows but would like to arrange to do so, please get in touch.
A run happens in the background
Running a workflow does not answer you on the spot. The run goes off on its own, and what it produces arrives on the Agents page, in the Agent runs table. Nothing lands on the Workflows page — it keeps no list of runs. So start a run and carry on with other work; see Track agent runs to follow its progress and read the output.
Three ways a run starts
- From the workflow itself. Open the workflow, choose the documents, and dispatch it.
- From the documents table. Select documents and send them to a workflow — see Work with the documents table.
- From a policy. A standing rule dispatches a workflow whenever a document matches it, without anyone starting the run — see About policies for the idea, or set one up.
Your workflows and the team's
Every workflow has an owner. Your own you can edit and delete. A colleague's you can read but not change — its fields are locked. To work from one, clone it to your own workflows and edit the copy; the original stays as its owner wrote it.
Your own workflows are listed to begin with. A toggle brings the team's into the list beside them.