Templates
Start from the automations you answer for most
Each template will ship with its workflow, its guardrails as a policy, and the tests that prove the policy does what it says. You change the limits and the approvers; the shape stays sound.
Every template on this page Planned
Refunds, payouts and deploys
- Planned
Refunds
Refund customers quickly without letting a large or unusual refund through unseen.
- Trigger
- A refund is requested in your store or help desk.
- Guardrails · refunds.v3
- Refunds over your limit wait for a Finance lead.
- Refunds to a card added in the last 24 hours are blocked.
- Approver
- Finance lead
- Step that acts
- Refund in Stripe, once.
- Planned
Payouts
Pay suppliers and partners on time, and never to a bank account that changed this morning.
- Trigger
- A payout is approved in your finance system.
- Guardrails · payouts.v7
- Payouts to a bank account changed in the last 48 hours are blocked.
- Payouts over your limit need a second person.
- Approver
- Treasury
- Step that acts
- Send the payout through your payment provider.
- Planned
Deploys
Ship to production on schedule, inside the change window, with the right sign-off.
- Trigger
- A release is tagged in GitHub.
- Guardrails · deploys.v2
- Deploys outside the change window wait until it opens.
- Deploys during a change freeze need the on-call lead.
- Approver
- On-call lead
- Step that acts
- Start the production deploy.
Every template starts in shadow, so you see what it would have done before it does anything. Limits and approvers above are examples; you set your own.
Automations you can answer for.
Tell us which automation you have to answer for. In the private beta you route its steps through your own gateway from the tool you use today, and move to Decionis Auto when it opens.
Join the private beta
Decionis Auto PlannedYour existing tool Private beta