Airflow Connection

Description

An Airflow Connection holds the address of an Apache Airflow API server and how to sign in to it. The Trigger Airflow DAG run action uses it.

It works with Airflow 3 and its REST API v2. Airflow 2 is not supported.

Options

Option Description

Name

The name actions use to refer to this connection.

Description

What the connection is for.

URL

The address of the Airflow API server, for example http://localhost:8080. Leave out /api/v2.

Connect timeout (seconds)

How long to wait for a connection. Default: 10.

Request timeout (seconds)

How long to wait for the answer to one request. Default: 60.

Authentication

  • Username and password: Hop exchanges them for a token at /auth/token and gets a new token when the old one expires. This works with the simple auth manager and the FAB auth manager.

  • Token: Hop sends the token as a bearer token. Use this for a managed Airflow service that gives you an API token.

  • None: Hop sends no credentials, for example when a proxy in front of Airflow takes care of that.

Username, Password

The Airflow user, for Username and password.

Token

The token, for Token.

All options except Authentication accept variables, for example ${AIRFLOW_URL}.

Hop does not follow redirects. When the server redirects, for example from http:// to https://, the error names the new address: use that address as the URL.

Hop uses the certificates the Java runtime trusts. To connect to an Airflow server with a self-signed certificate, add that certificate to the Java truststore.

Test connection

Test connection signs in and reads the list of DAGs, so it checks the credentials as well as the URL. It shows the Airflow version.