Integrate.io Release Notes & Product Updates

June's release cycle focused on expanding destination coverage with three new connectors and opening up programmatic pipeline management through a public API. Alongside that, sync reliability and security posture were hardened across MySQL, PostgreSQL, and Snowflake.

The Public API and YAML Import/Export Enable Programmatic Pipeline Management
Pipelines can now be managed programmatically through a new public API, with support for exporting and importing pipeline definitions as YAML. Teams can version pipeline configurations alongside application code, replicate pipelines across environments, and manage pipelines from their own tooling instead of relying solely on the dashboard. See the documentation for endpoint reference and authentication setup.

PostgreSQL, MySQL, and SQL Server Destinations Round Out Database Coverage
These Databases are now available as destinations, rounding out the platform's database destination coverage alongside existing targets. Teams running on these databases can land CDC data directly into them without staging through an intermediate warehouse first.

New Features

• Google Ads Expanded Performance Report Fields: CAMPAIGN, AD, ADGROUP, BUDGET, and KEYWORDS performance reports now expose significantly more fields per stream, aligning their schemas with the equivalent entity-stream reports and giving analysts access to metrics that previously required a separate report.
• MySQL and BigQuery Schema Change Hooks: MySQL and BigQuery sources now emit NEW_COLUMN and NEW_TABLE hook events, letting teams trigger downstream automation when source schemas change instead of polling for new fields or tables.
• Hubspot Custom Object Support: Hubspot sources can now sync custom objects in addition to standard objects, giving teams with custom Hubspot schemas full pipeline coverage instead of being limited to default object types.

Improvements

• PostgreSQL destination's graceful termination handling has been improved, and credential inputs are now available directly in the UI setup instead of requiring manual configuration.
• Snowflake destination role requirements have been hardened to least privilege, dropping the OWNERSHIP and schema MODIFY privileges that were previously required to sync data.
• MySQL source now supports per-table error isolation, so an issue with one table no longer halts replication for the rest of the source, and an optional GTID rewind override is available when replication state is ahead of the source.
• PostgreSQL destination now supports an override to make the heartbeat table optional, accommodating deployments that restrict heartbeat table creation.
• Parallel chunk workers on sources writing to BigQuery destinations have been disabled by default to avoid tripping BigQuery rate limits during sync.
• Hubspot connector now automatically syncs new columns added to custom objects, extending the custom object support shipped earlier this cycle.

Fixes

• PostgreSQL destination no longer produces ghost rows during a full resync, and no longer requires table ownership or CREATE privileges to sync.
• Non-PostgreSQL destinations no longer fail from a regression tied to a null file compression configuration value.
• Snowflake connector's test connection setup query helper no longer returns undefined values.
• MySQL connector no longer mismaps uint columns, JSON columns during parallel sync, or datetime values nested inside JSON during parallel sync.

We'd love to hear how these updates land in your day-to-day syncs, so don't hesitate to reach out with feedback.