Select Run to run the workflow on this computer, or export it and run it with iab_workflow.py. Standard procedures (Send Email, HTTP Request, Create Ticket…) run in the runtime itself, with no browser and no model.

How they run

• Connections (SMTP, webhooks, databases, vaults, ServiceNow, Jira) come from a local iab_connections.json file, never from the workflow. There's a sample at examples/iab_connections.example.json.
• --dry-run writes emails, notifications, tickets and any writes to an outbox/ folder instead of sending them.
• Approvals are answered from a second terminal:

  python3 iab_workflow.py --answer <task_id> approve --by "Name"

• Secrets from Get Secret can feed later steps, but never show up in results, logs, approval files or console output.
• Workflows with only standard procedures no longer need Playwright; the browser starts only when a web procedure runs.

Auto heal

• Auto heal (next to Checks) fixes the problems that have a safe fix and lists every change. Undo puts it back.
• Heal from a run… loads a workflow_result.json. For web steps that couldn't find their field or button, it proposes new locators from the screen the run saved. Patched procedures need re-approval in Agent Workbench.

Run a workflow

Run (top right) asks for the Start arguments and runs the workflow through the AWB helper on this computer. Start the helper in Terminal, in your IAB repo folder: .venv/bin/python iab_local.py (or --install to start it at login, when the repo isn't in Desktop, Documents or Downloads). Secrets go in ~/.iab/secrets.env. From a terminal instead:

python3 iab_workflow.py my.workflow.json --params inputs.json --dry-run

Drop --dry-run to send for real. Secrets come from IAB_SECRET_<NAME> environment variables. See README.md and OOTB_PROCEDURES.md in the iab_workflow folder for more.