Skip to main content

​
Overview

The Auto Sync New Columns feature detects columns added at the source between pipeline runs and adds them to the destination table on the next sync. Enable it to keep destination schemas in step with source schemas without editing the pipeline each time a new field appears. The feature applies to Singer-based connectors, including HubSpot standard and custom objects, Google Sheets, Facebook Ads, Google Ads, Google Analytics, LinkedIn Ads, Bing Ads, Klaviyo, Stripe, Shopify, eBay, Braintree, Zendesk Support, SurveyMonkey, Square, ReCharge, Shippo, Onfleet, Yotpo, GitHub, and GitLab.

​
Key features

  • Automatic detection: At the start of each sync, the connector discovers the source schema and compares it against a per-table baseline of previously seen columns.
  • Destination updates: New columns are added to the destination table before the sync writes the next batch of records.
  • First-sync seeding: The first sync after enabling the toggle seeds the baseline silently. No notification is sent for columns that already existed.
  • Notifications: When new columns are detected on a later run, a Hook notification lists the affected table and columns.
  • No history backfill: Historical values for new columns are not populated. Rows synced before the column appeared remain NULL for that column. Contact Support to resync a table if you need history.

​
How it works

1

Discovery at sync start

The connector queries the source and lists the columns available on each selected stream or table.
2

Diff against baseline

The discovered columns are compared to the baseline stored in pipeline state. Any column not in the baseline is treated as new.
3

Destination ALTER

For each new column, the pipeline adds the column to the destination table using the discovered data type.
4

Baseline update

The baseline is updated so the same column is not reported again on future runs.
5

Notification

A Hook email lists the new columns and reminds you that history is not backfilled.

​
Configuration

The toggle is available on the Sync Settings step during pipeline creation, and on the Settings tab of an existing pipeline. It is off by default. The toggle appears only when all of the following are true:
  • The source is a Singer-based connector.
  • The feature is enabled for your account. Contact Support if you do not see the toggle on a supported source.
  • The pipeline runs a version that supports new-column detection. Older pipelines may need an upgrade. Contact Support to upgrade an existing pipeline.

​
Considerations

  • Pipeline-level feature: Enable the toggle on each pipeline where you want new-column detection. Two pipelines that share the same source are configured independently.
  • No backfill: Only rows synced after the column is detected have values in the new column. Resync the table to populate history.
  • Column removal: Removing a column at the source does not remove it from the destination. See How Integrate.io ELT & CDC Handles Schema Changes for details on other schema changes.
  • Non-Singer sources: Database sources such as MySQL, PostgreSQL, and SQL Server use their own column-addition behavior. See How Integrate.io ELT & CDC Handles Schema Changes for details.
Last modified on October 27, 2026