> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-pipeline-tools/airflow/metadata-extracted.md).

# Airflow Metadata Extracted

List of all the metadata that Secoda pulls from Airflow

### What does Secoda extract from Airflow?

Whether you are using the Airflow APIs or the Secoda Plug in, the following information is extracted from Airflow.

* DAGs
  * Name
  * Description
  * Owners
  * URL
  * Runs
    * Name (ID of the Run)
    * Status
    * Created At (Timestamp)
    * Ended At (Timestamp)
* Tasks
  * Name
  * Description
  * Started At (Timestamp)
  * Ended At (Timestamp)

If you're using the Secoda Plugin for Airflow, Secoda will also extract:

* Queries
* Lineage
  * Secoda will parse the SQL query in each DAG to determine the source and target resources and build lineage

{% hint style="info" %}
Lineage and Queries will only work if the Operators used in the DAGS expose SQL queries. It will work best with Snowflake and BigQuery Operators.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/integrations/data-pipeline-tools/airflow/metadata-extracted.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.