Home/Platform/Workflow setup & simulation
Workflow setup

Turn messy recurring work into
a safe first simulation.

Workflow setup is a shared place to start, continue, interrupt, review, and complete AI-assisted work. Guided setup turns messy recurring work into a reviewable workflow — then you prove it on sample data before connecting a single live app or system.

hubson · Control Hub
Acme was double-charged on order #C-22841 — issue the $2,840 refund.
hubson · refund-approval
Double-charge confirmed. $2,840 is above the $2,000 threshold in finance.refunds.v3 — pausing for approval.
Paused at step 4/6 · Awaiting approval
Hubson Work PlannerThinking through the next step
Read ticket & confirm double-chargeZendesk #C-22841 · ops.read
Verify charge in Stripematch found · $2,840 · ops.read
Issue refund of $2,840above $2,000 threshold · awaiting approvalPAUSED
5Notify customer via email
6Write Action ReceiptRun · R-1284
Guided setup

You don't have to become an AI engineer

Describe the recurring job in plain English. Hubson drafts it and walks you through the parts that make it safe to run — no blank agent canvas.

OWNER & TRIGGER

Who and when

Define who owns the workflow and what kicks it off — a request, a schedule, or a handoff.

SOP

The SOP to follow

Attach an existing SOP, checklist, or policy — or have Hubson draft a starter SOP from how the work happens today.

APPS / ACTIONS

What it can touch

Review exactly what Hubson can read, draft, update, or ask to do — before anything is connected.

RISK CONTROLS

Where it pauses

Mark customer-facing, financial, or destructive actions as approval-required.

APPROVAL POINTS

Who decides

Route the risky step to the right person, with a clear, specific approval card.

SUCCESS MEASURE

What "done" means

Define the outcome that counts, so repeat runs and ROI reporting have a target.

Guided, not blank

Setup is a short conversation

Hubson asks a handful of plain questions and drafts the workflow from your answers — no agent canvas to figure out.

  1. What workflow do you want to improve?
  2. What starts it?
  3. Which SOP should guide it?
  4. Which apps does it touch?
  5. Which action should require approval?
  6. Who owns the result?
  7. What does success look like?

Not sure it should be a saved workflow yet?

Use Work Planner for one-off work. If the same pattern repeats, Hubson can suggest saving it as a workflow. Work Planner should be a bridge to saved workflows, not a replacement for them.

Trust before you connect anything

Run it as a simulation first

Map, draft, and simulate every workflow for free. Hubson runs the whole thing on sample data and mock app responses, pauses for approval where it should, and produces a real Action Receipt — without touching a single live app or system.

Simulation

  • Sample data
  • Mock app responses
  • Real approval card
  • Real Action Receipt
  • No live systems touched

Live run

  • Only the required apps connected
  • Same SOP and risk controls
  • Approval before any risky action
  • Activity and receipt generated
hubson · Control Hub · simulation
Simulationworkflow · refund-approval
Read ticket & confirm double-chargesample data · mock Zendesk response
Verify charge in Stripematch found · $2,840 · mock response
Issue refund of $2,840above $2,000 threshold · real approval cardPAUSED
5Notify customer via email
6Write Action ReceiptRun · R-1284
Simulation · no live actions

Map & simulate free → connect live only when it's trusted

Nothing at risk

Prove the workflow before you connect a live app

Draft it, scope it, and run a simulation in minutes. Connect live access only when the receipt earns your trust.