​
What is a Source?

In V1 flows, Sources are third party integrations that can read data from you or your tenant’s authenticated accounts

For example, an e-commerce flow may include many different Sources, such as Shopify, Amazon Seller, and WooCommerce.

​
What is an available Source?

An available Source is a Source that you can add to your hotglue flows. You can find a complete list of the default available Sources here. You can also fork and create custom sources via the Hotglue CLI.

​
What is a supported Source?

A supported Source is a Source that you have configured to be available within a flow.

​
What is a linked Source?

A linked Source is a instance of Source that has been successfully connected to by a particular tenant.

​
Source Configuration

There are four main configuration options for Hotglue Sources:

  1. Credentials
  2. Field maps
  3. ETL scripts
  4. Triggers

​
Credentials

Sources generally use one of two types of authorization: APIs and OAuth. Before enabling an OAuth Source, you must obtain and set up OAuth credentials.

  1. Your Client ID and Client Secret will be found in your company or developer account for that Source.
  2. Scope is used for some OAuth applications to define the data you will be reading or writing. This will prompt tenants to confirm the data permissions you are requesting.

​
Field maps

Field maps allow you to choose what data hotglue will pull in a sync job.

The field map displays a list of tables that can be turned on or off. Within each table, the field editor displays a list of fields that can be pulled or ignored.

To modify a field map for a Source, navigate to your chosen flow, click the “Source” tab, then select a Source to configure it.

Under configuration, click “customize field map.” From here, you can toggle tables on or off by clicking them.

Click the “edit” pencil button on a given table to add or remove fields.

​
ETL script

ETL scripts (or transformation scripts) can be used to transform raw data from your Source into a digestible format for your backend or Targets.

​
Triggers

Triggers create webhooks on your behalf to automatically run jobs when something happens in a Source system.

For example, when a new contact is added in Salesforce, a trigger can automatically run a new sync job.