Integrate.io Release Notes & Product Updates

August's release cycle focused on regulated file workflows, encryption at the storage boundary, and improved job failure debugging through component attribution. Authentication enhancements, connector coverage, and a broad range of other updates took up the rest of the month.

Component Error Names the Step That Failed

A failed job used to hand you a stack trace and leave you to work out which of a dozen components produced it. Job errors now name the component that failed and explain it in language you can act on, so triage starts at the cause instead of a search through the log. A stable error code makes the failure recognizable across runs, so a one-off debugging session becomes something that can be answered in a sentence.

User-Defined Schemas: Centralize the Layouts You Map To

Describing a destination layout used to mean rebuilding it field by field in every package that wrote to it, with no shared definition to point at. User-defined Schemas make that layout a first-class object on the account, owned and versioned in one place, so a change to the destination is one edit rather than a sweep through every package that feeds it. Smart Mapping then has something authoritative to map to: field matching, renames, and type conversions run against the layout you published rather than one inferred from whatever sits upstream. Our team can enable schema management for your account upon request.

PGP Encryption Closes the Gap at the Storage Boundary

Exchanging encrypted files with a partner meant a decryption or encryption step outside the platform, so plaintext sat on intermediate storage and a private key lived on somebody's laptop. File storage sources now read PGP-encrypted files directly and destinations encrypt output before it lands, so the data is only ever in the clear inside a running job. That closes the gap auditors ask about on regulated exchanges, and it removes the local scripting step that used to sit between a partner drop and a pipeline. Check out the documentation for the file storage source and the file storage destination for key selection on each side.

The EDI (X12) Source Puts Enrollment Data Where the Rest of Your Data Lives

Benefit enrollment has lived outside the data stack, locked in a format that only a dedicated EDI translator or a clearinghouse subscription could read. The EDI (X12) source brings 834 enrollment into the platform as ordinary rows, so member and coverage data lands in the same warehouse, reports, and pipelines as everything else. Eligibility reconciliation against HR and payroll, coverage audits, and downstream loads stop being a separate manual process that lives in a spreadsheet. For a health plan or a benefits administrator, enrollment becomes something the data team can own rather than something routed around them. The documentation has the full picture on what the source parses.

New Connectors

• Ometria Source and Destination: A native Ometria source imports profiles, orders, products, and lists from the Data API, and a matching destination pushes contacts, orders, and custom events back with batching, throttling, and merge control.
  (source and destination documentation).
• Trustpilot Destination: July's Trustpilot source covered reading reviews, and the destination adds the write side: service-review invitations sent from an ETL job with templates, field mappings, rate controls, sender validation, and an audit file of what went out. Trustpilot works in both directions on the same platform instead of a read-only feed (documentation).

New Features

• Ask Helm Auto Mode: Ask, Build, and Auto sit on one Ask Helm surface, and Auto routes a natural-language request to a documentation answer or a package-building action. Picking the right mode before you type is no longer part of the job (documentation).
• Fixed-Width File Destinations: File storage destinations write positional records with per-field widths, alignment, padding, overflow handling, and numeric formatting, and a preview renders the layout against real data. Fixed-width exports for banks and clearinghouses stop needing a downstream reformatting script (documentation).
• Benefits Hub: Trading partner management arrived in Account Settings with delivery settings, profile versions, effective dates, inheritance, and filename previews. Partner delivery rules live on the account rather than inside every package that serves them, and our team can turn the hub on for your account.
• Snowflake Database Overrides: Snowflake source and destination components each take an optional database value, and the connection form accepts an empty database. One connection covers every database on the account instead of one connection per database.
• Schedule Skipped Hook Event: A Schedule Skipped hook event fires when a scheduled run is passed over because the previous run is still active, or after repeated cluster failures. Skipped runs surface as a notification instead of a gap in the job history.
• NormalizeState Function: NormalizeState converts a full US state or territory name, the District of Columbia, or an already-valid two-letter code into its USPS abbreviation, including values carrying pasted whitespace. Address normalization fits in one expression instead of a nested conditional (documentation).

Improvements

• Salesforce customer-managed OAuth connections coordinate refresh-token rotation, so schema discovery, tests, previews, and jobs share short-lived access tokens instead of competing for a single-use token.
• New Salesforce OAuth connections use the configured proxy server.
• The Universal OAuth connector tests Custom Auth connections against a custom token URL and detects expired tokens correctly.
• Excel sources select a worksheet by tab position rather than by name, and previews, schema detection, and job runs all read the same sheet.
• Cloud storage and file upload sources accept an optional workbook password, so previews and scheduled jobs read protected .xlsx and .xlsm files.
• The HubSpot source adds Calls, Emails, Meetings, Notes, and Tasks as objects, and Contacts incremental loads sync on lastmodifieddate.
• The GA4 source adds Session, First user, and Event channel-group dimensions to the field picker.
• The Xero connector requests the accounting.budgets.read scope, so budget data comes through on new connections.
• The Oracle source resolves DB links in Table mode, so a table on a remote database is addressable with the @ character.
• The Oracle destination writes non-key text columns as NVARCHAR2 rather than NCLOB when the account sets _ORACLE_STRING_DATATYPE to NVARCHAR2.
• File Storage and File Upload sources append a literal string, a job variable, or both to filenames when archiving processed files, and keep the original if renaming fails.
• File destinations gained a third step for reordering, removing, and adding fields, with a five-row preview of the generated file.
• The REST API destination previews real payloads and headers from component previewer data.
• The Select component shows a warning when a mapped field is no longer available because a parent component changed.
• A failed job on the write-files-directly and replace-files-in-directory destination actions leaves the target directory in place instead of deleting it.
• Smart Transform runs by default on every account.
• Changing a BigQuery V2 connection's region or service account restores temporary-file access automatically, and administrators get tools to review and repair affected connections.

Fixes

• Package groups delete correctly when a custom role uses the group as a restriction, and permission scopes cannot widen when their last workspace is removed.
• The Join component passes the correct input fields to the Select component.
• Join type and optimization changes appear in the component previewer without a save first.
• The Universal OAuth connector's Test Connection button works for the Custom Auth type.
• Universal OAuth tokens refresh correctly on long-running jobs and ahead of schema-importer calls.
• The Salesforce Own Auth connector stays authorised instead of transitioning to an unauthorised state.
• Job variables such as _WORKFLOW_PACKAGE_LAST_SUCCESSFUL_JOB_SUBMISSION_TIMESTAMP carry their intended value rather than an incorrect timestamp.
• The workflow job details Variables tab shows a plain value rather than a DeserializeFromJson wrapper.
• The Aggregate and Cube components save after an upstream field is removed, and unused calculations clear automatically.
• The AI Transformation component works for users holding Editor and Operator roles.
• The REST API source drops other auth parameters when following an HTTP redirect, as do other components that make outbound API calls.
• File source components apply Detect header row automatically during job runs, not only in the schema importer and previewer.
• File Mover with a wildcard source and delete-from-source leaves files in subfolders it was never pointed at.
• Database source and destination, REST API source, and SharePoint source components report missing connections or record settings as a validation error, not a crash.
• The Region field in the Admin dropdown and in Account Settings shows regions outside the default list.
• The HubSpot source syncs objects carrying large numbers of custom fields, and the full-load previewer returns actual records.
• The SugarCRM source refreshes access tokens that expire in the middle of a job run.
• Ask Helm stays visible beside component modals and the expression editor rather than sitting underneath them.
• Reopening a Helm conversation restores its history without adding a blank assistant bubble.
• The API Transformation component's JSONPath expression input evaluates correctly, and response fields no longer collide with same-named fields from the parent component.
• The Slack webhook form works correctly when the browser is in fullscreen mode.
• The schema importer keeps read-only aliases aligned without stretching row height.

Performance Enhancements

• Worksheet selection reads an Excel workbook once rather than repeatedly, and large shared-string tables can be sampled for schema inference without exhausting memory.
• Error summaries load without transferring the full job log, and REST API and fixed-width previews run on real sample data.

Tell us which file formats and partner exchanges you need next, and where the new error pages still leave you guessing.