> 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/fivetran-integration.md).

# Fivetran

{% content-ref url="/pages/93VexPZblHdYUCkxCSNH" %}
[Fivetran Metadata Extracted](/integrations/data-pipeline-tools/fivetran-integration/metadata-extracted.md)
{% endcontent-ref %}

## Getting Started with Fivetran <a href="#h_21e27f5a15" id="h_21e27f5a15"></a>

There are two steps to get started using Fivetran with Secoda:

1. Generate an API Key and an API Secret on Fivetran
2. Connect Fivetran to Secoda with your API Key and API Secret

{% hint style="info" %}
Secoda pulls the following metadata from the Fivetran API: jobs, run times, owners, destinations, and other general metadata around jobs.
{% endhint %}

### Generate an API Key

1. Login to Fivetran and head to the Settings/API Config section.
2. Generate an API Key and API Secret (make sure to copy the key and secret).

> Note: If you already have an API key and secret issued generating a new key will disable and replace the existing key.

### Fivetran API Key Permissions

When generating an API Key in Fivetran, Secoda will need **view** access on:

* Destinations
* Transformations in Destinations
* Connectors
* Users

### Connect to Fivetran

1. In Secoda, head to the **Integrations** page and click **New Integration**
2. Select **Fivetran**
3. Paste the API Key
4. Head to the **Sync History** tab on the side bar and click **Run sync**


---

# 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.secoda.co/integrations/data-pipeline-tools/fivetran-integration.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.