# Fivetran Connector Sync

## Overview

Paradime provides a convenient way to trigger and orchestrate Fivetran connector syncs, allowing you to keep your data warehouse up to date with the latest data from your sources.

By leveraging Paradime's Fivetran Integration to triggering syncs, you can orchestrate your data pipeline by running dbt™ transformations immediately after your Fivetran sync completes. You can configure this by adding dbt™ commands directly in the same Bolt schedule or by using the [on run completion trigger](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/trigger-types) in a separate dbt™ pipeline.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2FOvFalj6EAZ5gjatsdrfo%2Fimage.png?alt=media&#x26;token=b48aeffb-faea-4d66-b15f-831655c534f8" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}

#### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

#### 1. Generate API Credentials

You will need a Fivetran API key and secret to use these commands. You can create them in your Fivetran account settings: [API Keys](https://fivetran.com/docs/rest-api/getting-started#generateapikeyandapisecret).  See our docs [here](https://docs.paradime.io/app-help/documentation/integrations/etl/fivetran).

**🔧 Connector Configuration**

* Ensure connector setup is complete and not in a "broken" state.
* Ensure source system credentials are valid.
* Verify destination warehouse permissions are correct.
* Unpause any paused connectors you want to sync.

#### 2. Set Environment Variables

Use the generated credentials and set as [environment variables](https://docs.paradime.io/app-help/documentation/settings/environment-variables/bolt-schedule-env-variables) for Bolt Schedules

* `FIVETRAN_API_KEY`
* `FIVETRAN_API_SECRET`
  {% endhint %}

### How to Configure Fivetran Connector Syncs

When setting up Fivetran Connector Sync, you can provide one or more Fivetran Connectors ID when setting up the task. Providing multiple Connector IDs in the same taks will allow the syncs to be run in parallel and continue to the next task only when all syncs completed.

{% hint style="success" %}
We recommend you set the Fivetran connector sync schedule to **manual**. This ensures Fivetran runs when you expect, and syncs are orchestrated only via Paradime.

<details>

<summary>How to Set a Fivetran Sync to Manual</summary>

This cURL command updates a Fivetran connection to use manual scheduling instead of automatic syncs.&#x20;

**Request Body Fields**

* **`schedule_type: "manual"`** - Sets sync schedule to manual (no automatic syncs)
* **`run_setup_tests: false`** - Skips connection validation tests during update

**Prerequisites**

1. **API Key & Secret**: Generate from Fivetran account settings
2. **Connector ID**: Found in Fivetran dashboard URL for the connector or using the [#list-fivetran-connectors](#list-fivetran-connectors "mention") CLI command

```python
curl -X PATCH \
  https://api.fivetran.com/v1/connections/<CONNECTOR_ID> \
  -u "<FIVETRAN_API_KEY>:<FIVETRAN_API_SECRET>" \
  -H "Content-Type: application/json" \
  -d '{"schedule_type": "manual", "run_setup_tests": false}'
```

**Expected Response**

Success (200 OK)

```json
{
  "code": "Success",
  "data": {
    "id": "abc123",
    "schedule_type": "manual",
    "sync_frequency": 0,
    "paused": false,
    ...
  }
}
```

**Validate in the Fivetran Dashboard UI**\
After updating your connection to manual schedule, verify the changes in the Fivetran dashboard:

1. Navigate to your Connector Dashboard
2. Locate your connector in the list
3. Check the top right corner of the connector details page

You should see:

* "Enabled"
* "Sync Scheduleed manually"

This confirms your connection is active and set to manual scheduling mode.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2Fw9p2UftT4uL12xxEc6S0%2Fimage.png?alt=media&#x26;token=989c94a2-41d6-433f-a968-9dab126c740c" alt=""><figcaption></figcaption></figure>

</details>
{% endhint %}

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2FOhtaqdIAaCgVWe9QBQcm%2Fimage.png?alt=media&#x26;token=8b01a992-e24f-42dd-ad5c-0f6bd083af53" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
**Learn More**: For all supported commands and additional configuration flags, refer to the [Paradime Fivetran CLI documentation](https://docs.paradime.io/app-help/developers/paradime-cli/fivetran-cli).
{% endhint %}

***

Now, let's learn how to configure the [Trigger Types](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules/trigger-types) of a Bolt Schedule. &#x20;