Business Approval on Runtime Agent

Build the canonical business approval loop from template #237, export it to a runtime agent, and decide requests in the agent’s /approvals inbox.

What this template does

1. Request Approval — expense or generic sign-off to [email protected].
2. Wait for Decision — 5-minute delay (tune for your SLA).
3. Check Status — reads {{approvalId}} outcome.
4. Outcome Switch — approved vs rejected notifications.

Template description explicitly supports Studio Activity → Approvals or Runtime /approvals.

Step 1 — Load and customize

1. Studio → Templates → search Request Poll Branch.
2. Load template #237 — Request, Poll & Branch on Status.
3. Set approver email, title, and category in Request Approval.
4. Adjust Delay if managers need more than 5 minutes to decide.

Step 2 — Test in Studio (optional)

1. Manual trigger with {"amount": 450}.
2. Decide in Jobs → Approvals before delay ends.
3. Confirm approved/rejected notification branch.

Step 3 — Export to runtime agent

1. Validate and Activate the workflow.
2. Export Runtime → enable Operator approval support (auto-checked for approval nodes).
3. Install on the edge or factory PC — see Export Runtime to Edge.

Step 4 — Decide on the agent

1. Trigger the workflow (cron, webhook ingress, or manual API).
2. Open http://<agent>:9090/approvals.
3. Find the pending request. Enter approver email matching the node setting.
4. Approve or Reject.
5. After the delay + check nodes run, verify the outcome notification in agent run history.

Step 5 — Production notes

• Approvals created on the agent stay in the agent DB — not synced to Studio.
• Use {{$var.managerEmail}} for portable approver config across exports.
• Pair with Approval with Auto-Escalation (#77) if pending requests need escalation.

Related tutorials

• Approvals on Runtime Agent — full dashboard guide.
• Purchase Approval on Runtime Agent — form-based variant (#74).