Automate the checks. Keep the decision.
Prepare a change, wait for a human decision, and continue only after approval.
THE FLOW
From trigger to outcome.
A repeatable process with a visible human decision before the protected action.
- 01 →
Prepare
Collect the request, checks, and evidence the reviewer needs.
- 02 →
Wait
Pause at an approval step assigned to the responsible reviewer.
- 03 →
Continue
Run the approved next step and preserve the decision with the run.
BEFORE YOU BUILD
Bring these details.
- A clear definition of the action that needs approval.
- The reviewer and evidence required to make the decision.
- A defined rejection path, expiry policy, and safe next step.
BEFORE YOU ENABLE IT
Check the edges.
- Verify that no protected action runs before approval.
- Test approval, rejection, and an unanswered request.
- Check permissions and record the decision with the run.
USE THIS RECIPE
Start with a brief.
Review the workflow.
Copy this brief into your Adios AI workspace. Supply your project details, review the proposed steps, and test with sample data.
Prefer the visual builder? Open Workflows in the console and add the trigger and steps shown above.
Recipes are starting points, not preconfigured integrations. Opening the console does not create or enable a workflow. An account and the required service credentials are needed.
Help me design an approval workflow in Adios. Ask what action requires approval, who should review it, and what evidence they need. Prepare the evidence, then use the platform's approval/wait controls before the protected step. Define rejection and unanswered-request behavior explicitly. Keep the approved action tied to the reviewed inputs. Show me the workflow and tests first; do not approve, deploy, or enable any production action on my behalf.
KEEP CONNECTING