Identify the exact approved version
Record the content and version under review, including amount, target and relevant files. If the requester can change it afterward, define when another decision is required. An abbreviated notification is not necessarily the approved object; let the reviewer inspect the authoritative content and changes.
Separate review from execution authority
Distinguish reviewer, return-to-requester authority and the actor permitted to mutate a register or external service. Decide whether approval authorizes automatic execution or a separate operator. Match platform capabilities to the actual policy rather than obscuring responsibility with one shared login.
Treat approval links according to their authority
Windmill documents approval through secret resume URLs. Where possessing a URL grants action authority, do not treat it like a public document link. Verify forwarding, expiry, identity and cancellation conditions and avoid careless replication into broad chat channels or logs.
Handle absence, rejection and timeout
Represent reviewer absence, expiry, returned work and withdrawn requests distinctly. Define escalation without silently turning missing approval into permission. Operators also need a way to find stalled work, not only alerts for decisions that already happened.
A hypothetical equipment request
Use a hypothetical equipment request with item, reason and amount, followed by review and a register entry. Test a changed amount, another reviewer, repeated clicks and expiry. Use this example to check authorization and record design before extending the process to payment execution under the organization’s purchasing rules.
Evaluate the complete evidence trail
Whether combining an execution platform, app handoffs or a working register, inspect each component’s role. Acceptance should show that the authorized version matches the executed version and remains explainable afterward. Include paid controls or evidence requirements rather than pricing an unusable minimum setup.
Invalidate an approval after a material change
Change the amount on a fictional request after approval and verify that the old authorization cannot silently drive the changed action. The acceptance condition is matching approved and executed versions, not only sending an alert. Define re-review or authorized cancellation according to the organization’s actual rules, and test that repeated use of a decision link does not execute the same external effect twice.
Estimate costs for your workload
Enter monthly jobs, billable steps and retries to see how different billing units affect your estimate.
Open cost calculatorOfficial sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Windmill suspend and approval stepsInformation checked: 2026-10-28
- Windmill plans and upgrade scopeInformation checked: 2026-10-28
- Activepieces pricingInformation checked: 2026-10-27
- Airtable plans overviewInformation checked: 2026-10-28
- Windmill pricing and computeInformation checked: 2026-10-28
- Windmill jobs and cancellationInformation checked: 2026-10-28
- Activepieces installation optionsInformation checked: 2026-10-27
- Activepieces Community and Enterprise editionsInformation checked: 2026-10-27
- Airtable pricingInformation checked: 2026-10-28
- Airtable billable collaboratorsInformation checked: 2026-10-28