flowwork ships a web console built into the engine binary. When flowwork is running, open
it at:
http://localhost:9010(The REST API lives under /api; the console is served at the root.) It’s a read-and-operate UI
over the same engine flowctl talks to — handy for browsing what’s running, inspecting a run’s
history, and connecting accounts.
This page is a placeholder while we add annotated screenshots. The page list below is accurate; the walkthroughs will get richer once images land.
Pages
- Runs (home) — the landing page is a list of workflow runs (executions): status, workflow, and when they started. The starting point for “what’s happening right now.”
- Workflows — a listing of the registered workflow definitions in the workspace.
- Workflow view — opens a single workflow and shows both its JS source (script) and a rendered graph of its steps and transitions.
- Connections — the Composio connected accounts: connect a personal account (e.g. Gmail) via OAuth here, which also creates a ready-to-use connector instance. See Composio connector.
- Connectors — a listing of the registered connectors available to your workflows.
Run detail
Opening a run drills into its full history, organized into tabs — timeline, variables,
events, forms, signals, webhooks, queries, and connector jobs — plus the
workflow graph with the run’s current position highlighted. It’s the visual counterpart to
flowctl run narrative / run events / run vars.
Console vs flowctl
The console and flowctl are two front-ends over one engine: use the console to browse and
to run the OAuth connection flow (which is UI-driven), and flowctl to author, register, and
script runs. Anything you do in one is visible in the other.