After you connect an integration and Stitch performs a structure sync, the next thing you’ll do is select tables and columns to replicate. In this guide, we’ll cover:

Table and column selection support

Below is the level of support each integration has for table and column selection:

  • indicates that table/column selection is supported for the integration. Note: Only the data you select will be replicated. If nothing is selected, the integration will have a status of Not Configured.

  • indicates that table and/or column selection isn’t supported for the integration:

    • For table selection, all available tables and columns will be automatically set to replicate. For detailed info on the data Stitch replicates from SaaS integrations, check out the Schema section of any integration’s guide.
    • For column selection, all available columns in the tables you select will be automatically set to replicate.
Table and column selection is not available for Stitch's webhook integrations. By default, all data sent to Stitch in a webhook message will be loaded to your destination. Refer to the webhook provider's documentation for info about possible attributes.
Table selection Column selection

Set data to replicate

To set data to replicate, click into the integration from the Stitch Dashboard page and find the table or column you want to replicate. Then, click the checkbox next to the object’s name. A green checkmark means the object is set to replicate. Keep in mind that:

  • For database integration tables, all columns will be set to replicate automatically.

    Additionally, you’ll be prompted to select a Replication Method for tables that you set to replicate.

  • For SaaS integration tables that support column selection, you can select columns by clicking on the table name and then tracking columns to replicate.

Note: Parent objects - or objects that contain other objects - must be set to replicate for the objects they contain to replicate. For example: For a column to replicate, the table that contains it must also be selected. If applicable, so must the schema containing the table, and the database containing the schema.

Select new and additional columns in already-selected tables

What happens when you’ve added a brand-new column in the data source or you want to replicate additional columns on an already-replicating table?

For more info check out the Syncing New and Additional Columns guide.

Select database views

While the steps for replicating a database view are almost the same as those for replicating a table, there are some slight differences.

For more info check out the Replicating Database Views guide.

Troubleshooting common issues

In this section:

Missing objects

Stitch cannot detect any objects (databases, tables, etc.) at or below this level.

If you receive this message or you can’t find an object (database, table, column, etc.), it’s typically a permissions issue.

Not supported table/column messages

If you see a status of Not Supported for a table or column in a database integration, there a few potential root causes:

  • Insufficient permissions. Verify that the Stitch user has all the required permissions as outlined in the Setup instructions for the database. Refer to the documentation for your database for more info.

    After you grant the required permissions and a full replication cycle has completed, the table’s Sync Status should change to Supported and be available for syncing.

  • Unsupported column. If a column is displayed as Not Supported, it may be that the column contains an unsupported data type.

Parent object not set to replicate

The table containing these columns is not set to sync. Please sync the parent table to ensure replication of columns selected on this screen.

If you receive this message, it means that the object above it isn’t set to replicate. For example: The table that contains a selected column isn’t set to replicate. Parent objects must be selected for the objects they contain to also replicate.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.