Workflow orchestration documentation

How it works

Use Workflow Library to create, find, open, duplicate, archive, and publish reusable workflow drafts before you configure bot execution. Workflow Library is reachable from Automation through the Workflow Library tab, and new drafts can start from guided templates such as Start from blank, Call an API, Get data from a webpage, Download a file and send it to an API, Extract webpage data and call an API, or Run on a schedule. Workflow Builder opens from a selected workflow, shows the exact execution order as a linear sequence, lets you save and reopen the same real draft without a service identity, and uses + Add step to insert executable steps into the connected Start-to-End path for blank or templated drafts. Step editors keep required fields visible and place approved request, webpage, and download settings under More options. The Draft Summary shows Website domains and the Configured timeout/delay ceiling across enabled steps so limits remain visible while you configure the workflow. Drag a step onto another step to reorder with a pointer, or use the accessible Up and Down actions from the keyboard. Valid edits auto-save after a short pause; every edit is also protected in this browser so ordinary navigation, refresh, or a transient save failure can restore it. Undo, Redo, Restore saved draft, and manual Save Workflow Draft remain available. When mappings or a published version exist, read the Before changing the sequence warning before moving, deleting, or replacing steps; published Bot Runs pinned to an earlier version remain unchanged until a new version is published and their deployment is updated. The guided path does not expose a raw graph, arbitrary connection drawing, backward links, or unsupported forks. It also shows broken request or folder references before the workflow becomes a Bot Run deployment. Publish a version only after the saved draft has a validation receipt and a dry-run test receipt; the Bot Run deployment handoff appears after a published version is selected. G2P Bot Light supports small API, webpage, scraping, download/file, and data workflows. The supported launch boundary is 10 executable steps; Start and End do not count; warning at 8 should appear before users hit the limit. Only one optional simple If/Then/Else decision is in scope, and its Then and Else paths must either end separately or rejoin one shared downstream path. There are no nested forks, no parallel paths, no loops, no subflows, and no recursion; send nested conditions, parallel forks, long-running resumable processes, desktop/browser RPA, screen-coordinate mouse/keyboard work, computer-vision or OCR navigation, Citrix or remote desktop interaction, multi-app automation, worker queues or attended automation, out-of-domain/session/runtime requests, or complex branching to the B9 RPA handoff. The handoff submits a redacted inquiry package to the configured email provider for delivery to the monitored support mailbox; provider acceptance does not confirm mailbox receipt. No B9 automation is created automatically, and secrets, passwords, API keys, tokens, authorization headers, session cookies, private keys, sensitive payloads, and downloaded files must stay out of the package.

1. Open Workflow Library from Workspace or Automation and confirm the active workspace is the one that owns the workflow.
2. Create a workflow from the template selector or open an existing row, then use search and lifecycle filters when the library has multiple drafts or published versions.
3. Review the Exact execution order sequence; templates create the normal Start-to-End connections, + Add step inserts the next executable step, and a decision exposes guided Add step to Then and Add step to Else lane actions without exposing the raw graph or arbitrary connection editing.
4. Drag a step onto another step to reorder it, or use Up and Down for a keyboard-only reorder; the save-status announcement confirms the updated execution order.
5. Configure each step with its required fields first. Open More options for approved optional request, webpage, and download controls such as timeout, retry, failure handling, response mappings, authorization secret reference, output names, file type, and bounded download size.
6. Review Website domains and the Configured timeout/delay ceiling in Draft Summary; unresolved dynamic hosts stay explicit, request retries are included in the ceiling, and the Bot Run overall timeout remains separate.
7. Before moving, deleting, or replacing steps, read the Before changing the sequence warning. Revalidate mappings that depend on earlier outputs; Bot Runs pinned to a published version keep using it until you publish a new version and update their deployment.
8. For a simple Web Bot workflow, start from Extract webpage data and call an API, then configure Open Web Page to capture approved page HTML, Extract Page Data with a CSS selector, Download File for a bounded CSV/JSON/XML/text file, Parse File into a named output key, use the transform output picker for earlier step outputs, then send them through a saved API request.
9. Watch the visible save status: valid changes auto-save after a short pause, and Changes protected in this browser means a refresh, ordinary navigation, or transient failure can recover the latest draft. Use Undo, Redo, Restore saved draft, or manual Save Workflow Draft when needed.
10. Keep G2P Bot Light workflows inside small API, webpage, scraping, download/file, and data workflows, with 10 executable steps, Start and End do not count, warning at 8, and one optional simple If/Then/Else decision.
11. When you add that decision, configure its condition, choose the next step type and optional name, then use Add step to Then or Add step to Else. Each guided lane may run linear steps and ends separately without requiring connection drawing.
12. Do not model full RPA in Workflow Builder: no nested forks, no parallel paths, no loops, no subflows, no recursion, and use the B9 RPA handoff for desktop/browser RPA, multi-app automation, or complex branching.
13. Use Send to B9 RPA only when the redacted inquiry package accurately describes the workflow name, organization/workspace context, safe design metadata, expected outcome, unsupported requirement, and validation summary; No B9 automation is created automatically.
14. Validate the saved draft, run the dry-run test, confirm the Workflow Evidence panel shows both receipts, then publish and use the published-version Bot Run deployment handoff when a governed service identity is ready.