Integrate.io Release Notes & Product Updates

July's release cycle extended destination coverage to the lakehouse and added a widely requested support-platform source. The rest of the cycle went into initial-sync reliability and giving teams a way to verify their alerting before they need it.

The Databricks Destination Lands Replicated Data in Delta Tables

Teams running on the lakehouse previously had to route CDC output through an intermediate warehouse before it reached Databricks. Pipelines can now replicate into Delta tables directly, with staging and load handled for you so resyncs, CDC updates, and scheduled runs behave the same way they do on every other warehouse destination. Type conversion is mapped across ten source types, including MySQL, Postgres, SQL Server, Oracle, DB2, Salesforce, BigQuery, and file storage, so high-precision decimals, Postgres complex types, SQL Server TIME, and JSON survive the load intact. Setup runs through a guided connection flow in the app, and AWS is supported today with Azure and GCP planned.

New Connectors

• Intercom Source: Intercom is now a supported source via OAuth with eleven streams covering contacts, companies, conversations, conversation parts, tickets, admins, teams, tags, segments, data attributes, and articles. Support and product teams can replicate their full Intercom history into the warehouse alongside the rest of their customer data.

New Features

• Slack Notification Hook: Pipeline run notifications can now go to Slack through a one-click OAuth connection in the Hooks UI. Teams get failure and completion alerts in the channel they already watch instead of only by email.
• Test Hook: A Test Hook action in the Hooks menu and in Settings sends a real ping to a configured Slack channel or email recipient list. Hook configuration can be verified at setup time rather than on the next failed run.
• Expanded Stripe Streams: Refunds, payment methods, and dispute balance transactions are now available as Stripe streams. Finance teams can reconcile chargebacks and refunds in the warehouse without maintaining a separate extract.
• Deleted Ad Records in Facebook Ads and TikTok Ads: Deleted ad rows are now included by default on supported streams, with a one-time historical backlog arriving on the first sync. Contact our team if you would rather exclude them.

Improvements

• Editing a hook preserves the fields you did not change, and an invalid configuration is rejected with a clear error instead of being saved.
• Databricks resyncs drop and recreate the destination table by default, with an opt-out for teams that manage table lifecycle themselves.
• The Intercom connector recovers on its own when a sync cannot resume from its last position, instead of stopping until someone intervenes.
• Intercom data attributes now use a composite primary key, so tables created before this change, including data_attributes and tickets, need a drop and resync.

Fixes

• Initial syncs no longer produce duplicate rows on affected pipelines, though a small number of tables that were mid-sync may need an explicit resync.
• DB2 to BigQuery initial syncs complete instead of hanging indefinitely.
• Pipelines that stop with an error fire the Pipeline Errored notification instead of Pipeline Stopped.
• The Bing Ads campaign stream includes the ad type that was previously missing.
• Intercom syncs complete for organizations with more than 10,000 records and recover from expired sessions.

Performance Enhancements

• Initial syncs to BigQuery run in parallel with safer retry handling, cutting the time it takes to load a large source.
• Out-of-memory failures during large initial syncs have been resolved, so a parallel sync finishes rather than ending partway through.

Let us know which sources you want us to cover next.