Before you start
- You have an agent in your workspace. See Create an agent.
- For the CLI tab, you have signed in with
pinework login.
Start a workflow and watch its steps
1
Pick a workflow
- Dashboard
- CLI
Open Automations in the sidebar. The Workflows section lists each workflow with its description and its last run. Click a name to read its program under Code.
2
Start it
This example starts Single agent step. It runs one agent on one prompt.When it works, the dashboard shows a toast that the workflow started. The CLI prints the workflow run as JSON. Its
- Dashboard
- CLI
- In the Workflows section, click Start next to the workflow.
- Set Access. Check first asks you before any action without a rule runs. Full access runs it, and your ask and deny rules still apply.
- Fill in the inputs. For Single agent step, pick the Agent and write the Prompt.
- Click the start button. It reads
Startplus the workflow’s title.
id starts with flr_ and its status is running.Some workflows, such as Build a slice, run only with full access. Their Access field is fixed. A CLI start with --mode ask still prints a run. That run then fails at once. Its summary says the engine refused the start.3
Watch each step
- Dashboard
- CLI
Open Automations, click the Runs tab, and click the workflow run.The Steps table has one row per step. It shows the step’s number, its kind (Agent or Gate), its state, the run it dispatched and the agent. A gate row also shows the command and its exit code. The page refreshes every 15 seconds while the workflow runs.
Click a step’s run to read its run trace. When the workflow ends, its status reads Ran or Failed.
4
Answer when a step needs you
A workflow can stop and wait for you in two ways.
- An approval. With Check first, an action without a rule waits for your approval. The step’s state reads Waiting on you and links to the approval. See Answer approvals.
- A question. Some workflows ask you what to do next, such as after a failed gate. A card marked Needs you shows the question and its answers. It appears on the workflow run’s page and at the top of the Runs tab.
Start a workflow an agent wrote
An agent writes a workflow as a JavaScript program. It declares ameta object, then calls agent steps through pw. A short one looks like this:
pinework workflow create --file <program.js>. Start it from the CLI by its meta.name:
Fix a workflow that does not start or move
The CLI says required inputs are missing
The CLI says required inputs are missing
Every required input needs a value. Run
pinework workflow catalog or pinework workflow get <name> to see each input’s key. Then pass it as --input key=value.A workflow you created yourself fails at once
A workflow you created yourself fails at once
A workflow you wrote needs an agent for its steps to run as. A workflow created from your own login has no author agent. Started by you, it fails with a message that nobody can run it. Ask an agent to write and save the workflow instead.
The start is refused because the workflow was retired
The start is refused because the workflow was retired
pinework workflow delete <name> retires a workflow. A retired workflow cannot start. Its past runs still show, and runs already going still finish.Answer approvals
Approve or deny what a workflow step waits on.
Runs
Read the run each step dispatched.
Schedule a routine
Give one agent a prompt on a schedule.
Approvals and questions
How Pinework pauses work for your answer.