Skip to content
  • There are no suggestions because the search field is empty.

Setting up and managing Data Connectors


A Data Connector links Trak to an outside data source so you can import records automatically instead of uploading files by hand — and, for a couple of connectors, export records back out. You manage them from Data → Connectors.

Only Site Admins can see and manage connectors. If Connectors does not appear under Data in the left navigation, your role does not have access — ask a Site Admin.

Which connectors are available

Connector Connects to Available for
AWS S3 CSV files in an Amazon S3 bucket Imports and exports
Microsoft Azure CSV files in Azure Blob Storage Imports
Database Query An external MySQL or SQL Server database Imports
Google Drive CSV files or Google Sheets spreadsheets Imports
Microsoft Dynamics Dynamics 365 records, queried through the API Imports
Salesforce Salesforce records, queried through the API Imports and exports
Zapier Thousands of other apps, through Zapier Triggering Zaps — see below

Connectors work in one of two ways:

  • File connectors read a spreadsheet or CSV file from a location you point them at: AWS S3, Microsoft Azure, and Google Drive.
  • Query connectors ask the source directly for records: Database Query (using an SQL query), Microsoft Dynamics, and Salesforce (each using an entity plus a query you build when you set up the import).

Zapier is different from the rest — it does not import or export data. It lets Zapier watch your saved views and trigger Zaps in other apps. Setting it up and using it is covered in its own article: Connecting Trak to Zapier.

Each connector's card carries a plan badge:

  • Salesforce and Microsoft Dynamics show a Professional badge — they are available on the Professional plan and above.
  • AWS S3, Microsoft Azure, Database Query, Google Drive, and Zapier show an Enterprise badge — they are available on the Enterprise plan.

To add a connector your plan does not include, or if you are unsure which plan you are on, contact your CSM.

Before you start

  • You need the Site Admin role. Enabling, changing, or disabling a connector also requires the Editor role — a Site Admin with the Viewer or Contributor role can view the page but not make changes.
  • Have the connector's credentials ready. Most connectors need details from the provider — an access key, a consumer key, a client ID and secret, or database login details. Each provider issues these differently.
  • Trak has a setup guide for each provider. Contact your CSM or Onboarding Specialist to be walked through obtaining the credentials for the connector you want.

How to enable a connector

  1. Go to Data → Connectors.
  2. Find the connector's card and choose Enable.
  3. If the connector needs credentials, a form opens. Enter the values from the provider and choose Save.
  4. The card now shows the connector as enabled, with a menu (⋯) of further actions.

Some connectors, once enabled, need a second step to authorize access to the source — see the next section.

How to authorize Salesforce, Microsoft Dynamics, or Google Drive

These three connectors sign in to the provider on your behalf and hold a token for it. After you enable and save the connector, authorize it from the connector's card:

  • Salesforce — choose Generate Token. Trak requests the token straight away and confirms with "Token has been generated."
  • Microsoft Dynamics and Google Drive — choose Authenticate. A provider sign-in window opens; sign in and approve access, and you are returned to Trak with the connection made.

An OAuth connector (Dynamics or Google Drive) also has a Refresh action in its menu, which renews the connection without signing in again.

The other connectors — AWS S3, Microsoft Azure, and Database Query — authenticate with the credentials you entered when enabling them, so they have no separate token step.

How to test a connector

  1. On the connector's card, open the actions menu (⋯).
  2. Choose Test.
  3. Trak checks the connection and shows the result — for example, "Salesforce connection successful." A failure reads "…connection failed."; recheck the credentials, and for Salesforce, Dynamics, or Google Drive, re-authorize the connector.

Testing does not import or change any data. It confirms Trak can reach the source with the details you provided.

How to disable a connector

  1. On the connector's card, open the actions menu (⋯).
  2. Choose Disable and confirm.

Disabling clears the connector's saved credentials and revokes any token it held. Imports or exports set up to use it stop working until you enable and authorize it again. To pause access without removing the credentials on an OAuth connector, use Revoke in the actions menu instead — it drops the token but leaves the connector enabled.

What to do if a token has expired

Salesforce, Microsoft Dynamics, and Google Drive tokens do not last forever. When a token expires, Trak notices the next time a scheduled import tries to use it:

  • The import stops and its detail page shows a banner: "This import is not working. The Token that is utilized on this import needs to be refreshed," with a Fix it here link.
  • Trak also emails the workspace's Site Admins so the expiry does not go unnoticed.

To fix it, a Site Admin re-authorizes the connector:

  1. Go to Data → Connectors.
  2. On the affected connector's card, choose Generate Token (Salesforce) or Authenticate (Microsoft Dynamics or Google Drive). For an OAuth connector you can try Refresh first.
  3. Choose Test to confirm the connection is working again.
  4. Re-run the import, or wait for its next scheduled run.

Related

  • Connecting Trak to Zapier