Integrate.io Release Notes & Product Updates

September's release cycle put more of the platform's output where teams already work, from partner-ready files and spreadsheets to the observability tools they run. Easier downstream edits in the package designer and deeper marketing and CRM connectors filled out the month.

Downstream Field Propagation Keeps Every Component in Step

Renaming a field early in a package used to mean opening every component after it to find what broke, often after a job had already failed. Downstream Field Propagation tells you which components a field change leaves out of step and brings the compatible ones back in line in one click. Changes that alter meaning, such as a sort key or a join field, come to you for review instead of being rewritten silently. A refactor that used to cost an afternoon of clicking becomes a review of a short list.

Log Drains Stream Job Logs Into the Observability Stack You Already Run

Job logs have lived inside the platform, so lining up a failed pipeline with the rest of your systems meant copying errors out of the dashboard by hand or retrieving them through an API endpoint. Log Drains send job success and failure logs to any OpenTelemetry-compatible service (e.g. New Relic, Datadog, Grafana, etc), for selected packages, whole workspaces, or the entire account. Pipeline failures then alert, correlate, and get retained under the same rules as the rest of your infrastructure instead of in a separate tab someone has to remember to check. Log Drains are available on request, our team can turn it on for your account. The documentation has the full picture on supported endpoints.

XML File Destinations Write Partner-Ready Documents Straight From a Pipeline

Partners and older systems that only accept XML used to force a conversion script between a pipeline's output and the file drop. File Storage destinations on Amazon S3, SFTP, and FTPS write well-formed XML directly, including nested sections, element names drawn from your data, and repeated groups. The document a partner's spec describes comes out of the job itself, so there is no reformatting step to maintain or to break when the spec changes. See the documentation for the options that shape each document.

New Connectors

• Salesforce Data Cloud Destination: Pipelines load records into Data Cloud objects through customer-managed Salesforce connections, with upsert and delete support and rejected rows routed to Problem Records. Pipeline data reaches Data Cloud segmentation and activation without a custom Ingestion API integration to build and maintain (documentation).
• OneTouch Health Source: OneTouch Health brings client, carer, invoice, location, status, and tag data into a pipeline, paging through full result sets. Username and password connections renew access on their own, so long-running jobs finish instead of failing when a token expires (documentation).

New Features

• Excel Workbooks on the SharePoint Destination: The SharePoint destination writes .xlsx workbooks from a template, and several destinations in one package can fill sheets of the same workbook. Formatted reports come straight from the job instead of being manually pasted into last month's file (documentation). This functionality will be live on all file storage destination connectors in the coming weeks.
• NetSuite RESTlets: The NetSuite REST source reads from RESTlet scripts, addressed by script and deployment ID or by full URL. Custom business objects your NetSuite team exposes through a script become a pipeline source instead of a separate export.

Improvements

• Job errors name a real cause and points to a failed component, instead of an AI-written summary.
• Azure Blob Storage connections can authenticate with a SAS token, so you can grant access scoped to the containers and time window a pipeline needs.
• The HubSpot source adds Campaigns and Users as objects, and existing OAuth connections need reauthorizing before the new objects appear.
• The Ometria destination maps every standard field Ometria documents for Contact, Order, and Custom Event, including @force_optin, @collection, custom properties, and SMS consent.
• The Ometria destination can write an optional CSV of accepted records to cloud storage, so you have a record of what Ometria took in.
• The Trustpilot destination sends product review invitations alongside service reviews, with productReviewTemplateId, productReviewProducts, and the other product review fields available in mapping.
• File Mover delivers files to Google Drive and Shared Drives, including over service-account connections, so output lands where business teams already work.
• SharePoint source and destination components pick up an authorized connection when the job runs, so cloned packages move between accounts and environments without reconnecting.
• The Salesforce source offers Source Action selection in Query mode, so Bulk query all, archived records included, runs on existing SOQL without rebuilding the field list in Object mode.
• Long-running Salesforce jobs, previews, schema detection, and Bulk upserts recover on their own when the org's session expires mid-run.
• NetSuite source JDBC connections run on version 8.10.190.0 of the NetSuite JDBC driver, up from 8.10.184.0.
• The expression and variables editors accept functions in any capitalization, so tOdATE(test) is corrected to ToDate(test) automatically.
• Users added to an account through Single Sign-On for the first time join with the read-only Reader role instead of Operator, so assign a higher role where one is needed.
• New accounts start with fewer automatic retries and a 24-hour execution timeout by default

Fixes

• Salesforce connections save and reconnect without an "At least one attribute is not allowed" error.
• Opening or editing a Join no longer changes the input field names that downstream selection, validation, and previews rely on.
• SugarCRM paginated pulls deliver each record exactly once, with no duplicates or gaps.
• File sources with underscore-prefixed column headers work with Detect header row automatically, and re-detecting existing schemas picks up the real names.
• Detect header row automatically handles files with colliding column names.
• Packages built through MCP inside a package group with connection restrictions save without an error.
• Packages built in an MCP chat open in the dashboard with their components laid out correctly.
• Salesforce SOAP destination jobs that write date fields complete instead of failing.
• SFTP and cloud storage destinations set to copy files to an existing directory overwrite on re-runs instead of failing or leaving partial temporary files.
• Redshift destinations with Automatically add missing columns enabled handle existing mixed-case columns instead of failing.
• Job failure summaries keep the log lines that identify the cause, including deep stack frames and long line tails.

Tell us which partner file specs and observability tools you want covered next, and where field changes still catch you out.