Bracket lets you connect popular tools and backend databases for two-way or one-way syncs. In this guide, we’ll talk through how to get everything connected in a few quick steps.
1. Prepare your data sources for the sync
The prerequisites for a successful sync are:
- Both data sources exist (i.e., Bracket does not host on your behalf)
- Both data sources have a unique key
- The secondary data source is empty of data
2. Create an account on our web app
Bracket web appSet up your syncs here
3. Enter connection details for each data source
On the web app, you’ll need to enter certain connection details to get syncs running. See below for a summary of what information you’ll need.
|Data source||What you’ll need|
|Airtable||An existing Airtable base|
|Notion||An existing Notion database|
|Google Sheets||Share Sheet with Bracket service account and get the Sheet ID|
|Postgres||Connection string URI|
|MongoDB||Connection string URI with Bracket as added user and whitelisting IP address 0.0.0.0/0 or Bracket’s dedicated IP addresses|
|Snowflake||Login credentials and details about the warehouse / table to be synced|
|Salesforce||Valid Salesforce account|
4. Review the fields to be synced and choose sync direction
On this page, you can remove any fields that you do not want synced. While Bracket auto-maps fields based on field names, you can also adjust the mapping as needed.
5. Name your sync and choose sync frequency.
If you are using the legacy app, before initiating the sync, you should make sure the field names and intersection types are accurate:
- Verify that the field names for each data source have appropriate capitalization, spaces, etc. On the legacy app, field names are case-sensitive.
- Verify that
INTERSECTION TYPEis accurate. You can figure out the appropriate intersection type here
6. Test and initiate sync
To make sure the sync will work as expected, click “Test run,” then refresh the page to see te result of the test.
Then, click “Run once” or toggle the sync to
Active to begin the sync. Refresh the page to verify that a sync job has been planned.