Build a dynamic workflow

To build a dynamic workflow, open the Workflows page, go to Dynamic, add a workflow to the list, and write your instruction in the editor beside it. Your changes save on their own as you work.

The two columns

The view is laid out in two columns.

Left — the list of workflows. My workflows holds your own. A "show team workflows" toggle adds a Team workflows section, holding everyone else's.
Right — the editor for whichever workflow is selected.

Select a workflow in the list to open it in the editor.

On a small screen the two columns do not sit side by side. A switcher above them moves between Workflows and Editor, one at a time; opening a workflow takes you to the editor, and closing it brings you back to the list.

Add a workflow

Select + beside the Workflows heading. A menu offers three ways to start:

Blank workflow — "Start from scratch." A new workflow appears in the list, selected, with the cursor in its title ready for you to name it.
From template… — "Pick a default to start from." Choose a starter template and the new workflow arrives with that template's content already in it, selected and ready to edit.
Create with AI — "Describe the job and the agent drafts the workflows." See Create workflows with the agent below.

Create workflows with the agent

Create with AI opens Quick Chat over the list, in a new discussion started for the purpose. Describe the job in your own words: what comes in, what you need to find out or produce, and what happens with the result. The agent sorts the job into the parts that belong elsewhere in Tiro Pro, such as uploading documents or filing them into a matter, and the parts a dynamic workflow should do; decides whether that is one workflow or several, and if several, what passes from one to the next; settles what each workflow needs to be told when it is run; and drafts each one.

Each draft appears under Drafts at the top of the list as the agent writes it. Open a draft to read and edit it, then Accept it to make it one of your workflows or Discard it. Where a job is several workflows, you run them yourself in the order the agent gives, taking one workflow's output from Activity to the next with Save to documents; nothing runs one workflow on another's result by itself. The discussion is an ordinary discussion in every other way and stays in Discussions for you to return to.

You can also ask the agent in Discussions to create an ordinary dynamic workflow for you or update one you own. A workflow the agent writes arrives as a draft, under Drafts at the top of the list, and only you can see it there. Open it to read and edit it as you would any workflow, then select Accept to make it one of your workflows, visible to the team and ready to run, or Discard to throw it away. A draft cannot be run until it is accepted.

Write the workflow

The editor holds three things to fill in: the workflow's title, its description, and the instruction itself. Write the instruction in plain English — what you want the agent to do with the documents you give it.

Inputs

Some workflows need to be told something on each run: a client's name, a date, a choice between options, or a particular document. Declare these under Inputs, between the description and the instruction, and refer to each one in the instruction by its name in double braces, such as {{client_name}}. Whoever runs the workflow is asked for every input before the run starts.

Each input has a name, a label, and a kind: short text, longer text, one of a list, several of a list, a document, or several documents. Tick Required for anything a run cannot do without; give an input a default where the team usually wants the same value, and the runner can still change it. If you type a new {{name}} into the instruction, the input appears in the panel on its own. The agent, when it drafts a workflow for you, declares the inputs it decides the workflow needs.

Format the instruction

A formatting toolbar sits with the content, offering bold, italic, headings, quote, and link.

Select the text you want to change, then select the action. Bold works as a switch: select it once to make the selection bold, and again to take the bold off. The link action puts a link around the text you selected, for you to fill in the address.

Saving

Your edits save on their own, shortly after you stop typing. An indicator reports where things stand:

Unsaved changes — you have made a change that has not been written yet.
Saving… — it is being written now.
Saved — everything is written.

There is no save button. If you select another workflow, or leave the page, before a save has happened, your changes are saved first and then the page moves on.

Run a workflow

Select the workflow, then select Run workflow on its row. The same control opens the Run workflow window.
Choose the source documents.
Fill in the workflow's Inputs, if it has any: the things it needs to be told for this run, such as a client's name or a choice between options. A required input is marked with an asterisk, and Run stays unavailable until every one has a value; an input with a stored default is filled in already.
With two or more documents selected, choose a Dispatch mode: "Send all documents to the same agent", which is the default, or "Send each document to a separate agent".
Select Run.

With a separate run per document and more than ten documents selected, you are asked to confirm before the runs go out.

The runs appear in Activity when they are ready — the dispatch message's View link takes you straight there. There is no list of runs on this page; see Track agent runs.

Give a workflow its own tab

A workflow your team runs often can have a tab of its own on the Workflows page. On the workflow's row, select Give it a tab. A new sub-tab appears beside the others, named after the workflow, with a form made from its inputs: a field for each one, a document picker for an input that takes documents, and a Run button that stays unavailable until every required input has a value. Running from the tab starts the workflow exactly as Run workflow does, and the result arrives in Activity.

The form follows the workflow: change its inputs and the tab shows the change on your next visit. A workflow that already has a tab shows Open its tab on its row instead. Delete the tab from the tab itself; deleting the workflow removes the tab with it.

A colleague's workflow is read-only

Select a workflow owned by someone else and the editor opens it for reading. Its fields are disabled, a Read-only indicator appears, and Clone to my workflows takes the place of the edit and delete actions. Select it to take your own copy, which you can then edit like any other.

If the owner edits the workflow while you have it open, what you are reading updates on its own.

Delete a workflow

Select Delete on a workflow you own and confirm in the window that opens. The workflow goes from the list, and the editor clears. A colleague's workflow has no delete action for you.

Where a workflow gets used

A workflow is not only run from here. Three other places put it to work:

the documents table, where you select documents and send them to a workflow — see Work with the documents table;
Discussions, where you can ask the agent to find a saved workflow and run it against attached subjects, a subset, or other team documents. The run continues in the background and the agent links you to Activity; and
a policy, which runs the workflow whenever a document matches the rule — see Create and manage policies.