Create a Workflow
You describe the routine in plain English and the agent authors the Workflow. You review what it proposes before anything lands in the Project.
Audience: builders
Before you start
A Workflow runs inside a Project, so you need the Project first. It will also run better if the Project already has what the work depends on: the data sources it reads, the Instructions that set your team's norms, the Skills or verified logic it should call. See Project context.
You do not have to have all of it in place. It is often easier to describe the Workflow, see what the agent asks for, and add the missing pieces then.
Author it in chat
Open the Project in Build
Switch the header to Build. The Context tree appears in the sidebar.
Find Workflows under Automations
Automations is the first group in the tree and opens by default, because what a Project runs is usually what you came to check on.
Click Create a workflow in chat
The composer opens seeded with "Create a workflow for this project that ". Finish the sentence with the routine you want.
Be concrete about three things: what starts the work, what the agent should do with it, and what you want back.
Create a workflow for this project that takes an inbound vendor email asking about an invoice, looks the invoice up in the AP data collection, and drafts a reply with the payment status and expected date. Flag anything where the invoice is not found, or the amount does not match the PO, for a human to look at.
Review what the agent proposes
The agent writes the Workflow and comes back with the change. The review shows the steps, the contract, and the files it wants to add. Read it, ask for adjustments in the same conversation, and apply it when it is right.
Add a trigger
A new Workflow can be run by hand. To have work arrive on its own, open the Triggers tab and add one. See Triggers.
Iterate in the same conversation. The fastest way to tighten a Workflow is to run it, look at the Work item it produced, and tell the agent what was wrong. It has the Workflow and the run in front of it.
You can also add the file
Workflows are files under .blockparty/workflows/ in the Project. If you have one already, from another Project or from a colleague, adding the file makes it appear in the Context tree.
There is no separate publish step. A Workflow is live in its Project as soon as the change is applied. What controls whether work actually arrives is its triggers, so add those last, once the Workflow does what you want.