> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/sources/transformation-etl/fivetran/fivetran-integration-discovered-resources.md).

# Fivetran Integration Discovered Resources

The Euno-Fivetran integration discovers the following resources:

* Fivetran destination
* Fivetran connector
* Warehouse tables referenced by each connector's enabled destination schemas (non-authoritative stubs when the table is not already observed by a warehouse integration)

Supported destination services for connector-to-table lineage: **Snowflake** and **BigQuery**.

## Fivetran Destination

| Property            | Value                                                                    |
| ------------------- | ------------------------------------------------------------------------ |
| `type`              | `fivetran_destination`                                                   |
| `name`              | Destination name in Fivetran                                             |
| `created_at`        | Destination creation timestamp                                           |
| `native_id`         | Destination (group) ID in the Fivetran account                           |
| `is_active`         | `true` when destination `setup_status` is `connected`; otherwise `false` |
| `container_type`    | `pure_container`                                                         |
| `native_raw_object` | Combined Fivetran group and destination API payloads                     |

## Fivetran Connector

| Property            | Value                                                                                      |
| ------------------- | ------------------------------------------------------------------------------------------ |
| `type`              | `fivetran_connector`                                                                       |
| `name`              | Connector schema name in Fivetran                                                          |
| `created_at`        | Connector creation timestamp                                                               |
| `parent_container`  | URI of the Fivetran destination for this connector                                         |
| `native_id`         | Connector ID in the Fivetran account                                                       |
| `is_active`         | `true` when the connector is not paused and has succeeded at least once; otherwise `false` |
| `native_raw_object` | Full connector payload from the Fivetran API, including enabled destination schemas        |
| `defines`           | Warehouse table URIs the connector loads into its destination (see Relationships)          |

Connectors with no enabled tables in their Fivetran schema configuration may have an empty `defines` list (for example paused connectors or connectors with empty `schemas` in the API).

## Destination Tables (by reference)

For each enabled table in a connector's destination schema, the crawler may emit a non-authoritative `table` observation so Euno can resolve `defines` URIs before the warehouse integration observes the physical table. Lifecycle and rich table metadata remain owned by the warehouse source (for example Snowflake).

***

### Relationships

| Source type(s)         | Relationship | Target type(s)       | Notes                                                                                |
| ---------------------- | ------------ | -------------------- | ------------------------------------------------------------------------------------ |
| `fivetran_destination` | has child    | `fivetran_connector` | Connectors belong to their destination                                               |
| `fivetran_connector`   | defines      | `table`              | Destination tables the connector syncs into; set from enabled Fivetran schema tables |
| `table`                | has definer  | `fivetran_connector` | Inverse of **defines**                                                               |

{% hint style="info" %}
Connector-to-warehouse-table lineage uses the **defined-by** relationship (`defines` / `has defined`), not dependency lineage (`has downstream`).

**Example EQL:** find connectors that define tables:

`type = 'fivetran_connector' AND has defined(type = 'table')`

Find tables defined by Fivetran:

`type = 'table' AND has definer(type = 'fivetran_connector')`
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.euno.ai/sources/transformation-etl/fivetran/fivetran-integration-discovered-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.