The info in this doc only applies to the following integrations:
Have a suggestion? Reach out to us.
For some of our SaaS integrations, you can choose which tables should be synced to your data warehouse after a successful connection is established.
The majority of SaaS integrations, however, will have all available data synced to your data warehouse. For detailed info on what data you can expect to see for each integration, refer to the Expected SaaS Data section.
In this article, we'll cover:
Before we dive in, there are a few things you should keep in mind about how Stitch handles SaaS integrations:
Syncing Salesforce Columns
If you want to sync individual columns from Salesforce, click into the table you want to sync. Then you can select the columns you want.
Note that column-level syncing only applies to Salesforce at this time.
For SaaS integrations that support table selection, you can unsync tables individually or en masse with just a few clicks.
Unsyncing individual tables is done exactly the opposite of syncing.
You can unsync all tables by clicking the grey icon above the Syncing Icon column and selecting Stop Syncing All:
A few factors can play into how quickly you'll see the new data or changes take effect in your data warehouse:
All of the above can impact how long replication can take.
If your data hasn't shown up after a reasonable amount of time, reach out to our support team. We'll help you get to the bottom of it.
If you haven't already, the next step is to set the Replication Frequency for your integration.
We recommend you also check out the articles linked below in the Related section. These resources will help you understand how your data will appear in your data warehouse, how Redshift handles schema changes, why some tables/columns have hashed names, and more.