dheerajturaga opened a new pull request, #1689: URL: https://github.com/apache/airflow-site/pull/1689
**What**: Adds the [Airflow Inbound Webhooks Provider](https://github.com/dheerajturaga/airflow-provider-inbound-webhooks) to *Third Party Airflow Plugins and Providers*. One entry, placed after the last provider entry. **What it is**: a third-party provider and plugin (`airflow-provider-inbound-webhooks` on [PyPI](https://pypi.org/project/airflow-provider-inbound-webhooks/), Apache-2.0, registered through the `apache_airflow_provider` and `airflow.plugins` entry points) for Airflow 3.1.1+. It adds a `/webhooks/<name>` endpoint to the API server that verifies each delivery's signature or secret header against an `inbound_webhook` connection and records it as an asset event, so a Dag triggers by scheduling on an asset named after the event, e.g. `github/<org>/<repo>/pull_request/labeled/deploy-preview`. GitHub, GitLab and Jira are built in; any other service that signs with HMAC-SHA256 or sends a secret header is described in its connection. **Why it is useful**: webhook senders can't obtain an Airflow API token, so today they need a relay service in front of Airflow or sensors that poll the other service. **Testing**: CI runs the unit tests and a test that starts the real `airflow api-server` with the installed wheel and sends it signed deliveries, across Airflow 3.1.1 to latest, Python 3.10 to 3.14, and SQLite, PostgreSQL and MySQL. A working end-to-end example is in [inbound-webhooks-demo](https://github.com/dheerajturaga/inbound-webhooks-demo). **Why this page**: `providers/ACCEPTING_PROVIDERS.rst` points third-party providers to this ecosystem page. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
