Skip to content
Supero
Platform · Workflows

Business workflows that run the same way every time

Define a multi-step process once. Supero runs each step, retries or stops it on the limits you set, records every run, and undoes the completed steps if a later one fails.

Refused state changesAutomatic rollbackApprovalsRun history
Workflow run · job_settlement · FieldOpsSAMPLE
  1. capturestripe_checkout · payment captureddone
  2. invoicequickbooks · invoice createddone
  3. notifyemail · customer emaileddone
  4. finalizeupdate appointment · failedfailed
Rolling back, newest first
notifyskipped: a notification
invoiceskipped: accounting sync is best-effort
capturerefund_payment · payment refunded
Run status: compensatedEvery step written to the run log
How it works

From definition to a recorded run

Your app decides when a workflow starts. Supero runs each step, keeps the run record and undoes completed steps when one fails.

01 · Define

Describe the process

The steps, what each one calls and how to undo it. Your AI writes the definition into your app's setup.py when it builds over MCP, and you can edit workflows in the console.

02 · Call

Your app starts a run

Your app's code starts a run through the REST API or the SDK, or binds a workflow to an event, such as a new order being created.

03 · Run and record

Supero runs each step

It runs the steps in order, retries or times them out as defined, records each step's result and rolls back completed steps if one fails.

Example

A job settlement, step by step

When a FieldOps technician finishes a job, one workflow captures the payment, creates the invoice, emails the customer and closes the job.

A state change that isn't allowed

Built-in services such as bookings allow only the state changes they define. Completing a cancelled booking is refused.

POST complete · booking in state 'cancelled'
409 INVALID_STATE_TRANSITION
"Cannot complete from state 'cancelled'."
record unchanged

The wrong person decides an approval

An approval goes to named approvers in order. Someone who isn't the assigned approver for the current step can't approve or reject it.

approve · step 2 · caller is not its approver
403 NOT_YOUR_STEP
approval unchanged

A later step fails

Closing the job fails after the payment was captured. The completed steps are undone, newest first, and the payment is refunded.

finalize failed
– notify   skipped
– invoice  skipped
↺ capture  refund_payment
status: compensated
Capabilities

What workflows include

Refused state changes

Live

Built-in services such as bookings, approvals, carts and payments allow only the state changes they define. Anything else returns 409 and the record is left as it was.

Automatic rollback

Live

If a step fails, the steps that completed are undone, newest first. Steps such as notifications can be marked to skip the undo.

Approvals by the assigned approver

Live

Approvals move through named approvers in order. Only the approver assigned to a step can approve or reject it.

Calls to other systems

Live

A step can call any integration, such as Stripe, QuickBooks, Slack, email or SMS, reserve stock, or create and update records in your app.

Conditions, loops and parallel steps

Live

Branch on a value, repeat a step over a list, run steps side by side, or reshape data between steps.

Retries and time limits

Live

A step can retry a set number of times. Each step and each run has a time limit, so a stuck call doesn't hold the run.

Run history

Live

Every run is recorded with its status, each step's result, errors and timings, and the order in which steps were undone. The console lists recent runs.

Event triggers

Live

Bind a workflow to an event, such as a record being created, so it starts without extra code in your app.

For engineers

What a workflow looks like

The definition from the FieldOps reference app, the call your app makes and the run record Supero keeps.

Source: fieldops/setup.py

# fieldops/setup.py
WORKFLOW_DEFINITIONS = [{
  "workflow_id": "job_settlement",
  "on_error": "compensate",
  "steps": [
    {"id": "capture", "type": "service_call",
     "service": "stripe_checkout", "operation": "create_checkout_session",
     "compensate": {"kind": "automatic", "service": "stripe_checkout",
                    "operation": "refund_payment"}},
    {"id": "invoice", "type": "service_call",
     "service": "quickbooks", "operation": "create_invoice",
     "on_error": "continue",
     "compensate": {"kind": "skip_acknowledged",
                    "reason": "accounting sync best-effort"}},
    {"id": "notify", "type": "service_call",
     "service": "email", "operation": "send_email", ...},
    {"id": "finalize", "type": "crud_operation",
     "operation": "update", "object_type": "fieldops:appointment", ...},
  ],
}]
Where teams use it

Common workflows on Supero

Payments and settlement

Capture a payment, create the invoice and close the job, with a refund if a later step fails.

See it in FieldOps →

Approvals

Expenses, purchase requests and quotes signed off by the right approver, then paid or fulfilled.

See it in Ledgerline →

Orders and bookings

Reserve stock or a slot, confirm, fulfil and capture, with the reservation released if a step fails.

Notifications and follow-ups

Message a Slack channel and text the assigned technician when a job is dispatched, or remind a customer before an appointment.

FAQ

Workflow questions

Who writes the workflow definition?

Your AI writes it when it builds the app over MCP. It lives in your app's setup.py as WORKFLOW_DEFINITIONS, next to your data models, and you can also edit workflows in the console.

What happens if an undo step itself fails?

The rollback stops there and the run is marked compensation_failed, with the error for each step that couldn't be undone. The console's run list shows the run and the records that are still active, so you can clean them up.

Can a step call external systems?

Yes. A step can call any integration your project has set up, such as Stripe, QuickBooks, Slack, email or SMS, and can create or update records in your app.

How do I see what happened in a run?

Each run has a record with its status, each step's result and error, timings and the order in which steps were undone. Read it through the API, or open the workflow's runs in the console.

Can a workflow start on its own when data changes?

Yes. Bind a workflow to an event, such as a record being created, and it runs when the event happens.

Is a language model involved in running a workflow?

No. The Supero runtime runs each step from the definition. A model is called only if you add a step that calls one.

Build, deploy and scale with Supero.

Bring a PRD and your AI. Free plan with 3 projects and preview deploys, no credit card required.