Refund automation
Policy-aware refunds with human approval gates and authenticated refund tools.
Architecture
Intent/flow → lookup order → condition policy → approval → refund tool (challenge) → complete
Prerequisites
- Refund tool with auth required
- Owner/Admin approvers
- Policy knowledge in workspace
Installation
- Complete User getting started for the Support (or commerce) workspace.
- Connect channels required by this solution.
- Register tools / connectors (see links below).
- Declare and enable flows; Accept versions after sync.
- Run a dry-end-to-end test in a non-production workspace when possible.
Flows
See order-approval style flows with approval + auth:required tool
Deployment
- Production checklist: Production deployment
- Observe Flow Runs and
/api/v1/org/eventsfor event-driven paths
Troubleshooting
- No answer / weak citations → knowledge coverage (Knowledge Base)
- Tool failures → tool logs + SDK webhook health
- Event flow never starts → namespaced name, Enabled+Valid+Accepted,
whenpredicate (Events) - Approval stuck → Owner/Admin role (Approvals)