Approval workflow

Automation with judgment days: the flow does everything except the irreversible step, which waits for a person to approve or reject.

The pattern

(any preparation) → Human in the Loop ── approved → sensitive action (send / pay / publish)
                                     └── rejected → notify & archive

Step by step

1. Preparation branch — whatever produces the thing to approve: an LLM Agent drafting an email, a Transformer assembling a payment order, a PDF Generator building a contract.
2. Human in the Loop (Base) — configure:
   • Assignees: who can decide (one or several).
   • Context: pass the draft/order via variables so the approver sees exactly what they're approving.
   • Timeout: what happens if nobody answers (fail, or continue down a default branch).
3. Approved branch — the sensitive node: Email, HTTP Request to a payment API, WhatsApp Output.
4. Rejected branch — notify the requester and log the decision to a Database or Kanban.

Variations

• Two-level approval: chain two Human in the Loop nodes (manager → finance).
• Auto-approve small cases with a Conditional Flow before the gate (e.g. amounts under $100).
• Wrap the sensitive call with an Error Handler so failures notify instead of silently dying.

Genius prompt: "Create an approval flow: AI drafts the email, a human approves or rejects with a timeout, and only approved drafts get sent."