Route an expense for approval

Check the request before it reaches a manager. Complete requests move to a decision; incomplete ones produce a clear list of what the employee still needs to provide.

Ask in your own words

Build an “Expense approval” workflow for acme/operations. A teammate will paste an expense request. Check for the amount, date, business purpose, and receipt. If anything is missing, write a short list for Finance and stop. If the request is complete, ask the employee's manager to approve or reject it, then email the request and decision to finance@example.com. Show me the proposed workflow before saving it.

Proposed graph

Expense request
      ↓
Are all required details present?
   ├── No → List missing details → Notify Finance
   └── Yes
          ↓
      Manager decision
       ├── Approve ─┐
       └── Reject ──┴→ Notify Finance

The completeness check should answer one yes-or-no question. Both manager outcomes preserve the original request and the recorded decision in the run history.

Change it later

Add Finance approval after the manager for requests above $1,000. Keep the required fields, missing-details route, manager decision, and notification address. Show me the change before saving it.

Test it

Omit the receipt and confirm the workflow stops before manager approval.
Use a complete request and confirm the manager sees the original details.
Test both approval outcomes and confirm Finance receives the decision.