Every sync you set up with Bracket 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
- Submit a new connection or navigate to an existing connection
- 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.
- Verify that the
Intersection Typefor each field is accurate.
Intersection Typeis 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 Typevalues at the button below.
Bracket Intersection Type MappingSee all supported field types and Intersection Types here.
Intersection Typebased on the primary data source’s fields. Depending on your secondary source, you may need to adjust the
- 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 source||Fields generated when new connection submitted?||Fields generated when adding to existing sync?|
|Airtable||Yes, if you select “Create table for me” during setup||No, field must be added to data source separately|
|Notion||No, fields must already exist||No, field must be added to data source separately|
|Google Sheets||No, fields must already exist||No, field must be added to data source separately|
|Postgres||No, fields must already exist||No, field must be added to data source separately|
|Snowflake||No, fields must already exist||No, field must be added to data source separately|