1. Sign in & look around
app.workflowhub.work — the Pull Queue is where work arrives; the Dashboard shows throughput and where work waits; every screen has a ? help icon and most have a guided tour.
Docs & support
How to run it, connect it, and get your data out.
The essentials live here; the full contextual help — a help icon on every screen, guided tours, and the knowledge base your own runs feed — is built into the product itself.
Getting started
First hour
For the complete reference — every routing rule, the security model, field types, agent setup — see the user manual. This page is the short version plus the integration contract.
2. Design a workflow
Workflows → visual canvas: queues, forms, routing, rules. Or open Connect Claude and let an AI assemble the workflow for you over MCP — it has an expert authoring guide built in.
3. Put an agent on it
Download the open-source edge agent, paste an API key from the API Keys page, and bind it to a queue. Your credentials stay on your machine; the platform sees work, never secrets.
Integration guide
Events out, actions in
The architecture in one sentence: WorkflowHub owns workflow state and emits events; your tools — n8n, scripts, BI — own scheduling and delivery. Authenticate everything with an API key in the X-Api-Key header; the machine-readable OpenAPI contract is served to key-holders.
Webhooks → your triggers
Subscribe (Integrations page or API) to WorkItemCreated, WorkItemRouted, WorkItemFinished, WorkItemFieldChanged, NoteAdded — fired from every real mutation path, including the rules engine's automatic routing (engine moves are marked routedBy: "workflow-rule").
- HMAC-signed (
X-WFH-Signature) — verify before trusting - Retried on failure, with a per-delivery inspection log
- SSRF-guarded: destinations must be public URLs
- Internal notes notify that, never what
REST + the idempotent intake door
Create and act on work over plain REST — and for machine-driven intake, POST /api/sources/ingest is idempotent: a dedupe ledger means redelivering the same source event never duplicates a work item. Retries are free by design.
- Route/finish honor the same human-approval gates as the UI
- Workflow variables: shared runtime state your apps and the rules engine both read
- Batch route / finish / note / field update
MCP for agent-shaped integrators
170+ tools over the Model Context Protocol, acting as the caller with per-request key attribution — work items, workflows, projects, knowledge, webhooks, reports. Point Claude (or any MCP client) at your workspace from the Connect Claude page.
Reports & data out
Reports you build in the product are server-executable: a stable URL returns the result as JSON or CSV. Paste the CSV URL into PowerBI or Excel as a Web source with your API key header — every refresh re-runs the report against live data. The same reports run over MCP (run_report, run_flow_report).
- Flow analytics built in: throughput, stage times, aging/stuck items, cost per item
- Row caps are always disclosed, never silent
Support
Early access means you talk to the people building it. In-product: the ? on any screen. Anything else: email and a human answers.