Add human approval to Airflow with AI
Pause a pipeline for a reviewer, collect a choice or form response and decide explicitly what happens if the response deadline passes.
To add human approval to Airflow with AI, name the decision that must happen between two tasks. A monthly close might need a reviewer to confirm a total before an export goes further. The airflow-hitl skill helps match that requirement to an operator supplied by the installed standard provider.
A yes-or-no gate, a choice of downstream paths and a form that collects extra values serve different purposes. The timeout also deserves a deliberate choice. Setting an approval as the default allows a silent timeout to count as approval, which may be inappropriate for an explicit sign-off.
What it does
- Add a review step between preparation and release of a report.
- Present a choice that determines which downstream task will run.
- Collect comments or other form inputs during a DAG run.
- Discover the supported parameters for the installed provider version.
- Design the timeout behaviour and review the result in the Airflow UI.
Install and use
- Install the skill and use Airflow 3.1 or later with its compatible standard provider, the af CLI and jq. Reviewers need an authorised account. An external responder also needs appropriate API access.
- Ask, “Require an explicit approval before our export. Show how to handle a rejection and how to fail if the deadline expires.”
- Test each response and the timeout path in a suitable instance before scheduling the workflow.
FAQ
Source
Made by Astronomer. Original skill: airflow-hitl, published on GitHub under the Apache-2.0 licence.
View on GitHub