​
Summary

Every sync you set up on the Bracket legacy app will have a field mapping between the data sources. It’s important to verify that the field mapping is accurate to make sure your sync works properly.

​
How to review the field mapping for a new sync

  1. Submit a new connection or navigate to an existing connection
  2. On the connection dashboard, scroll down to the “Fields” section. Verify that the field names for both your primary and secondary sources are accurate, and delete any fields that you do not want to sync.
By default, Bracket will list all fields from your primary data source for every new sync, and assume the secondary source field names are identical. If you have a different naming convention for your secondary source, you must update the field names in the mapping.
  1. Verify that the Intersection Type for each field is accurate. Intersection Type is Bracket’s bridge between field types from two different data sources. You can see a mapping of all supported field types and their respective Intersection Type values at the button below.

Bracket Intersection Type Mapping

See all supported field types and Intersection Types here.
Similar to field names, Bracket interpolates the Intersection Type based on the primary data source’s fields. Depending on your secondary source, you may need to adjust the Intersection Type.
  1. After any changes, click “Update mapping” to save your changes.

​
Do I need to create the fields in each data source beforehand?

In most cases, Bracket can only sync with existing fields, so you must create the fields you want to sync in both sources before syncing them. However, there are some exceptions. See below for a breakdown on when Bracket generates fields automatically.
Data sourceFields generated when new connection submitted?Fields generated when adding to existing sync?
AirtableYes, if you select “Create table for me” during setupNo, field must be added to data source separately
NotionNo, fields must already existNo, field must be added to data source separately
HubspotNo, fields must already existNo, field must be added to data source separately
Google SheetsNo, fields must already existNo, field must be added to data source separately
PostgresNo, fields must already existNo, field must be added to data source separately
MongoDBYesYes
SnowflakeNo, fields must already existNo, field must be added to data source separately
FirebaseYesYes