Skip to main content
Where: workflow detail → Edit Workflow (or Actions → Edit Workflow in the list) Everything except the policy and the AI model can be changed. That covers the information section, the playbook actions, the step engines, the output schema, and the reference notes — and none of those edits regenerate the playbook.
Edit Workflow screen

The Edit Workflow screen — each section has its own Edit button.

​
What is on the screen

Lower part of the Edit Workflow screen

The lower part of the edit screen — AI Model, JSON Output Schema, and Reference Notes.

​
The policy and the AI model cannot be changed

There is no policy definition section on the edit screen. Changing the policy means rebuilding the playbook, the actions, and every engine assignment — which effectively makes it a different workflow. So the policy is fixed after creation, and only the execution plan beneath it is adjustable. The AI model is read-only for the same reason. You can read the original policy text in policyText from GET /workflows/:workflowId. When you do need to change the policy itself, create a new workflow. Copying the existing one first is faster, because you do not have to rewrite the output schema.
Check the reference notes before you rewrite the policy. A verdict that comes out wrong is usually not caused by the policy sentence itself but by that sentence being carried into the action’s reference notes incorrectly. Reference notes can be fixed right on this screen.

​
Editing the information section

Information section

Information — select Edit to change the name and description.

Only the name and description change; the playbook is untouched.

​
Editing playbook actions

This is the edit you will use most. Selecting Edit switches the section into edit mode in place, not in a separate window. Change the order, names, descriptions, and engines, then Save to apply everything at once.
Playbook action edit mode

Playbook action edit mode — drag handle, pencil next to the name, engine button on the right, delete, and Add Action at the bottom.

Save is disabled while nothing has changed. Cancel returns everything to how it was before the edit.
step is only the execution order, so reordering reassigns the numbers. When your integration code refers to a step, use workId — it stays fixed regardless of order.

​
Editing step engines

Selecting n engine(s) (or Select engines) on the right of an action row opens a window for choosing the engines assigned to that step.
Editing step engines

Editing step engines — pick from the full engine catalog with checkboxes.

  • The title is Edit Step n Engines.
  • There is a Select All checkbox and a count such as “2 of 7 selected”.
  • Each engine shows its name and description, so you can confirm what it does right here.
  • Apply puts the choice on that step; the final save happens with Save on the playbook actions section.
Engine capabilities, prices, and supported countries are in AI model and engines.

​
Editing the output schema

An Edit Output Schema window opens with the same two tabs used at creation, Field Builder and JSON Schema Input.
Edit Output Schema

Edit Output Schema — the existing schema is expanded in the Field Builder.

The constraints match creation — the root must be "type": "object", nesting is 2 levels at most, and names cannot repeat. The full rules are in output schema.
Changing the schema does not change the results of analyses that already finished. An analysis freezes and stores the schema as it was at run time. The new schema applies from the next analysis onward.

​
Editing reference notes

This is the first place to look when an action carried the policy’s intent across incorrectly. The Edit Reference Notes window lists the entries in a text area as lines beginning with - .
Edit Reference Notes

Edit Reference Notes — one line is one entry.

Saving replaces the whole list. Save is disabled while nothing has changed.

​
What saving does

playbookId stays the same for the life of the workflow; only playbookVersion goes up with each edit. Past analyses froze the playbook as it was at run time, so edits do not affect them — reading analysis results. With nothing to change, the screen tells you there are no changes to save.

​
Common errors