Set up a Fivetran connector

Capabilities
Gather Fivetran configuration information
Option 1: User API Key (simplest)
Option 2: System Key (granular scopes)
Configure the Fivetran connector

Capabilities

Resource	Sync	Provision
Account
Group
Role
Team

Additional functionality:

Account provisioning: Invite new users to your Fivetran account. A role can optionally be specified during provisioning.
Account deprovisioning: Delete users from your Fivetran account.

Gather Fivetran configuration information

Configuring the connector requires you to pass in information from Fivetran. Gather these configuration details before you move on. Here’s the information you’ll need:

API Key
API Secret

Fivetran supports two types of API keys. Either one works with this connector:

Option 1: User API Key (simplest)

A personal API key that inherits the permissions of the user who generates it.

Log in to the Fivetran Dashboard.
Click your user avatar in the bottom-left corner and select API Key.
Click Generate new API secret if you don’t have one yet.
Copy the API Key and API Secret.

The user generating the key must have the Account Administrator role for the connector to sync all resources and provision accounts.

Option 2: System Key (granular scopes)

A service-level key with configurable scopes per resource type. Use this for least-privilege access.

Log in to the Fivetran Dashboard.
Navigate to Account Settings > General > System Keys.
Click Add System Key and configure the required scopes.
Copy the generated Key and Secret.

Learn how to create a system key

Required system key scopes for sync only:

USER:READ
ACCOUNT:READ
TEAM:READ
ROLES:READ
DESTINATION:READ

Required system key scopes for sync with provisioning:

USER:MANAGE
ACCOUNT:READ
TEAM:READ
ROLES:READ
DESTINATION:READ

System key scopes only apply to System Keys. User API Keys inherit permissions from the user’s role and do not require scope configuration.

Configure the Fivetran connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Fivetran configuration information gathered by following the instructions above

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Integrations > Connectors and click Add connector.

Search for Fivetran and click Add.

Choose how to set up the new Fivetran connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

Click Next.

Find the Settings area of the page and click Edit.

Enter the configuration information from the previous section.

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Fivetran connector is now pulling access data into C1.

Follow these instructions to use the Fivetran connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.

Step 1: Set up a new Fivetran connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Fivetran connector:

Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

Click Next.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Fivetran connector deployment:

Secrets configuration

# baton-fivetran-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fivetran-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Fivetran config
  BATON_FIVETRAN_API_KEY: <API Key for Fivetran>
  BATON_FIVETRAN_API_SECRET: <API Key Secret for Fivetran>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-fivetran.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-fivetran
  labels:
    app: baton-fivetran
spec:
  selector:
    matchLabels:
      app: baton-fivetran
  template:
    metadata:
      labels:
        app: baton-fivetran
        baton: true
        baton-app: fivetran
    spec:
      containers:
      - name: baton-fivetran
        image: ghcr.io/conductorone/baton-fivetran:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-fivetran
        envFrom:
        - secretRef:
            name: baton-fivetran-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Fivetran connector to. Fivetran data should be found on the Entitlements and Accounts tabs.

That’s it! Your Fivetran connector is now pulling access data into C1.

Set up a Fastly connector

Set up a FleetDM connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Fivetran connector

Capabilities

Gather Fivetran configuration information

Option 1: User API Key (simplest)

Option 2: System Key (granular scopes)

Learn how to create a system key

Configure the Fivetran connector

Resources

Step 1: Set up a new Fivetran connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather Fivetran configuration information

​Option 1: User API Key (simplest)

​Option 2: System Key (granular scopes)

Learn how to create a system key

​Configure the Fivetran connector

​Resources

​Step 1: Set up a new Fivetran connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Fivetran configuration information

Option 1: User API Key (simplest)

Option 2: System Key (granular scopes)

Configure the Fivetran connector

Resources

Step 1: Set up a new Fivetran connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector