Integrate.io logo

Integrate.io Release Notes & Product Updates

An overview of the latest updates and product improvements. Got a product update or feature you'd like to see supported? Let us know - support@integrate.io

October 2026: Sync your packages to GitHub, and promote them to Prod by pull request

ETL & Reverse ETL

October's release cycle gave teams more control over how packages reach production and clearer sight of what each run actually did. New connectors on both ends of the pipeline and steady connector work rounded out the month.

Sync Packages to GitHub and Promote Them by Pull Request

Packages have lived only inside the platform, so keeping their history in Git meant exporting JSON by hand and remembering to do it after every change. The GitHub integration syncs your packages and workflows to a repository you choose, so each saved version is tracked in Git next to the rest of your code. Teams running separate Dev, QA, and Prod accounts can go a step further with package promotion, which carries changes from one account to the next through reviewed pull requests, and Prod changes only after someone approves. We are rolling out this feature gradually, and if you want it now, let our team know. The documentation covers the integration, and package promotion has its own page.

Job Insights Shows Where Every Run Spends Its Time

Working out why a job ran long, or where its row counts went wrong, used to mean reading through logs and guessing from the totals at the end. Job Insights lays out each completed dataflow run as a timeline, with record counts for every component. A slow step or a source that read fewer rows than expected stands out at a glance, so tuning a package or answering a data question starts from evidence instead of a log search. See the documentation for what each part of the view reports.

Filters Put Advanced Search One Click Away in Every List View

Search bar modifiers have long let you narrow a list of jobs, packages, or connections, but only if you knew the syntax by heart. A Filters button beside the search bar puts those same options on screen in seven list views, from Jobs and Packages to Connections and Clusters. Anyone on the team can pull up failed runs on one package, or packages changed this month, without learning a query language first. Each choice lands in the search bar as a modifier, so typed searches keep working as before. The documentation lists the filters each view offers.

New Connectors

  • Outlook Source and Destination: The Outlook source reads calendar events and mail from a signed-in or shared mailbox, and the Outlook Calendar destination creates and updates events from pipeline records. Dates from a CRM or database land on a shared calendar and stay in step with their source instead of being copied over by hand (source and destination documentation).
  • NetSuite REST Destination: The NetSuite REST destination completes the pair with the existing NetSuite REST source and writes standard and custom records, transactions with line items included, by insert, update, or upsert. Upserts match on external ID, so a load can run again after a failure instead of leaving duplicate records to clean up (documentation).
  • ServiceNow Destination: The ServiceNow destination completes the pair with the existing ServiceNow source and writes records into an import set table or straight into a table over the same connection. Import sets run through your instance's transform maps, so records land under the rules your ServiceNow team already set instead of a parallel load path (documentation).
  • Oracle Fusion Source: The Oracle Fusion source reads objects across Financials, Procurement, CRM, HCM, and more from payables and receivables invoices to suppliers, purchase orders, customer accounts, and workers, all with incremental loads. Fusion data reaches the warehouse on a schedule instead of through report exports saved as CSV files (documentation).
  • Square Source: The Square source reads 14 objects, including payments, refunds, payouts, customers, and catalog items, with incremental loads on payments and refunds. Sales and customer data from Square joins the rest of your reporting on a schedule instead of through a manual export (documentation).
  • Fundraise Up Source: The Fundraise Up source reads nine objects, including donations, recurring plans, supporters, and the event log, with incremental loads on six of them. Donation and supporter data sits in the same warehouse as your CRM and finance data instead of in a separate export (documentation).
  • OneTouch Health Destination: Following September's OneTouch Health source, the destination creates and updates carer records through the OneTouch API over the same connection. Carer records maintained in another system reach OneTouch from a pipeline instead of being re-entered by hand (documentation).

New Features

  • ZIP Extraction in File Mover: File Mover can unpack ZIP archives at the destination and deliver the extracted files, into one folder per archive or all into one folder. Partner drops that arrive zipped reach their folder ready to load instead of waiting on a separate unzip step (documentation).
  • Excel Output on File Storage Destinations: SFTP, Amazon S3, Google Cloud Storage, and Azure Blob Storage destinations write Excel (.xlsx) files. Teams that expect a spreadsheet get one straight from the job instead of converting a CSV by hand.

Improvements

  • File Storage destinations default to intermediate storage, with a copy into an existing directory as the destination action.
  • Downstream Field Propagation shows a compact summary of fields not carried into child components, and newly added source fields appear in full until the next refresh.
  • Source and destination editors collapse Advanced settings by default, with a header that shows which options are switched on, and every component shares one settings layout.
  • File sources replace three header checkboxes with a single Header choice and add Semicolon and Pipe as delimiters.
  • Import and Export JSON is available to custom roles on accounts that have Source Control enabled.
  • Helm builds Salesforce to Snowflake pipelines, including packages that move several Salesforce objects at once.
  • The MCP server adds a save_package_version tool, so an agent can save a package's draft as a new version.
  • The MCP get_run_summary tool returns the records each source read and each destination wrote, per flow and in total, in one call (documentation).
  • Salesforce connections add Client Credentials as a connection option, so a pipeline can connect without signing in as a named user.
  • Salesforce destinations can write their success and error files to SharePoint.
  • The Snowflake destination supports Query Tags, so you can find the queries a job ran in Snowflake's query history.
  • The REST API destination accepts fields and variables in Custom Input mode, so you can build any JSON body from pipeline data.
  • File sources add a file_modified_at metadata field holding each file's last modification time in the source file system.
  • Two package variables tune SFTP writes: _FS_SFTP_WRITE_CHUNK_SIZE sets the chunk size, and _FS_SFTP_WRITE_MAX_UNCONFIRMED set to 0 suits servers that fail on several writes at once.
  • The SharePoint source reads files stored in Microsoft Teams as well as SharePoint sites.
  • The HubSpot source reads associations between objects, such as the companies and deals linked to a contact.
  • The Facebook Ads source retries temporary Graph API errors for up to 30 minutes, slows down near Facebook's rate limits, and re-creates reports Facebook marks as failed.
  • The Google Ads source runs on API versions v23 to v25, and v20 and v21 are removed after Google deprecated them.
  • The Google Ads source adds the Lead Form Submission Data report, so lead form entries load alongside your campaign data.
  • The Bing Ads source runs on a new connector that authenticates with a developer token.
  • The REST API source pages through DocuSign results, so full result sets arrive instead of only the first page.

Fixes

  • Incremental loads that use a variable as the reference date send the variable's value, so jobs no longer fail or skip the date filter.
  • _PACKAGE_LAST_SUCCESSFUL_JOB_SUBMISSION_TIMESTAMP, _WORKFLOW_PACKAGE_LAST_SUCCESSFUL_JOB_SUBMISSION_TIMESTAMP and their S3-escaped versions no longer skip data when a workflow child starts late.
  • Scheduler auto-retry works on schedules that run every 5 minutes or less, and auto-retry schedules no longer drop runs silently.
  • File Mover deletes source files only after they are confirmed delivered, and keeps them when any step fails or a file changes mid-job.
  • File Mover moves from Azure delete their source files again after delivery.
  • Long-running Salesforce source jobs finish instead of failing on a timeout error.
  • Concurrent jobs writing to the same file storage folder no longer collide over shared staging files.
  • Jobs that clean up intermediate storage on Amazon S3, such as Snowflake loads, fail quickly on a timeout.
  • Workflow variables that use AddToDate and other newer expression functions parse at job start.
  • The REST API destination accepts special characters in payloads and settings and sends single-field values, so writing rows to Google Sheets works.
  • The Salesforce API destination works on accounts that route traffic through the Integrate.io egress proxy.
  • Redshift connections that drop during connection setup retry automatically instead of failing the job.
  • The GA4 source retries temporary API errors on every call instead of failing the job.
  • API keys stay valid when someone signs in through SSO for the first time.
  • CSV imports work with Detect header row automatically when a source path field is also in use.

Tell us how package promotion fits your release process, and where Job Insights still leaves a support question unanswered.

10 days ago

October 2026: Replicate straight into Azure Databricks, plus Grubhub and Salesforce updates

ELT & CDC

October's release cycle carried replication to more clouds and more sources, and gave Salesforce pipelines finer control over what they replicate. Load reliability across the warehouse destinations took the rest of the month.

Replicate straight into Azure Databricks

The Databricks destination arrived in July for workspaces on AWS, so teams running their lakehouse on Azure still had to route CDC output through an intermediate cloud storage first. The destination supports Azure Databricks, and those pipelines replicate straight into Delta tables in the workspace your analysts already query. The detour drops out of the pipeline, and so does the second copy of the data it left behind. Full setup details are in the documentation.

The Grubhub Source Carries Order and Reporting Data to Your Warehouse

Restaurant and food service teams selling through Grubhub have pulled its numbers out by hand, usually as exports that go stale the day they are downloaded. The Grubhub source replicates order and reporting data from Grubhub's Connect and Reporting APIs into your warehouse on every sync. Grubhub revenue sits next to point-of-sale, inventory, and finance data, so channel comparisons and reconciliation run on current figures instead of last week's export.

Salesforce Pipelines Decide How Deletes and Syncs Behave

Salesforce deletions used to reach the destination one fixed way, and teams that needed deleted records gone from their tables had to clean them up downstream. A deleted-record setting gives you the choice: soft keeps the row and marks it deleted for audit and history, while hard removes it so the table matches Salesforce. Pipelines can also switch between Full Sync and Incremental Sync, so you decide where a full reload is worth its cost instead of living with the default. Our team enables the sync mode choice on request, and the documentation has the full picture.

New Features

  • Job Load Sync Method for BigQuery: The BigQuery destination can load data through BigQuery load jobs as an alternative to streaming inserts. Large initial syncs and backfills get a load path built for volume instead of relying on the streaming API alone.
  • Automatic PostgreSQL Publications: When the connecting user holds the needed rights, PostgreSQL pipelines create and maintain their own publication. New tables join the publication as the pipeline grows instead of waiting on a DBA to update it by hand. (documentation)

Improvements

  • BigQuery destinations move rows larger than 10 MB to a load job automatically, so oversized rows arrive instead of hitting the streaming size limit.
  • Salesforce History objects load OldValue and NewValue as JSON, so values of any field type land in one consistent format.
  • Database sources keep the initial sync running for every other table when one table fails, so a single problem table no longer holds up the rest.

Fixes

  • Databricks destinations keep every row through a restart or resync instead of losing data.
  • Databricks loads keep moving after a source schema change instead of stalling.
  • PostgreSQL parallel initial syncs release their memory when they finish instead of leaking it over time.
  • Redshift and Snowflake merges load a row delivered more than once as a single row instead of a duplicate.
  • BigQuery destinations load boolean and numeric values into correctly typed columns.

Tell us how Azure Databricks and the new Salesforce settings fit your pipelines, and which delivery platforms you want covered next.

10 days ago

September 2026: Streamlined Pipelines and New Partner-Ready Outputs

ETL & Reverse ETL

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.

about 1 month ago

September 2026: More Resilient Loads and Broader Ad Platform Coverage

ELT & CDC

September's release cycle went into keeping data flowing when part of a load goes wrong, and into clean recovery when replication sources are interrupted. Ad platform coverage and initial-sync data fidelity took the rest of the month.

The Snowflake Destination Keeps Healthy Tables Loading When One Fails

One table's failed load into Snowflake used to stop the whole pipeline, so a single bad table held up every healthy one behind it. With a per-pipeline setting, the Snowflake destination keeps the pipeline running while that table is set aside, and a Destination Load Failed notification names the table that needs attention. Failed tables retry on their own, so a transient problem clears without anyone stepping in. The rest of your warehouse stays current while the one problem gets fixed, instead of the whole sync waiting on it.

The OneTouch Health Source Puts Care Operations Data in the Warehouse

Home care teams running on OneTouch Health have had client, carer, and scheduling data locked inside the care management system, reachable only through exports. The OneTouch Health source replicates operational, care, client, scheduling, financial, and residential data into your warehouse. Scheduling, billing, and staffing questions get answered alongside payroll and finance data instead of in a spreadsheet stitched together each month. Operations and finance teams work from the same numbers, refreshed on every sync.

New Features

  • Facebook Ads Lookback Windows: Facebook Ads pipelines can re-read the last 1, 7, 14, or 28 days of Insights on every sync. Conversions Meta attributes after the original sync land in the warehouse instead of leaving spend and return figures short.
  • Source Change Time for DB2 CDC: DB2 CDC pipelines can carry an _iio_changed_at column holding each row's change time at the source. Ordering and freshness checks use when a change happened instead of when it loaded, and our team enables it on request.

Improvements

  • Facebook Pages connect with page-level access, so a connection no longer needs business portfolio administrator permissions.
  • The Facebook connector's schemas follow Meta's new API version, so streams keep loading as Meta retires older fields.
  • Facebook Ads adds daily_budget, lifetime_budget, and budget_remaining on campaigns, and bid_amount and bid_strategy on ad sets.
  • Snapchat discovers every organization and ad account a connection can reach and syncs them all, instead of one organization at a time.
  • Initial syncs of pipelines with many tables allow schema setup time in proportion to the table count, so wide pipelines start instead of timing out.
  • Snowflake connection validation checks only the configured warehouse, database, and schema, so roles with many grants validate instead of timing out.
  • Redshift and Snowflake destinations never run two load cycles against the same table at once, so catch-up after a delay finishes without duplicate work.

Fixes

  • MySQL change tracking resumes after a source restart instead of stalling silently while reporting as healthy.
  • DB2 sources write _iio_start without a container time zone shift, and an unreadable source change time falls back instead of failing the row.
  • Oracle syncs of large tables keep their connection alive through long idle stretches instead of failing on a dropped connection.
  • Oracle unconstrained NUMBER columns keep fractional values as decimals instead of truncating them.
  • Oracle CDC reads text values that look like numbers instead of failing to parse them.
  • BigQuery pipelines treat a transient error as transient instead of failing with a permissions error.
  • PostgreSQL ARRAY columns load into Snowflake as text, and existing affected tables need a resync to pick up the corrected type.
  • MySQL JSON columns load into Redshift during initial syncs that use parallel chunk workers.
  • Snowflake initial syncs complete on tables holding zero dates or text longer than 16 MB.

Performance Enhancements

  • Oracle initial syncs of large tables without a numeric primary key chunk on a suitable indexed column, so the first load runs in parallel instead of as one stream.
  • BigQuery destinations share one schema-propagation wait across tables, so a column change across many tables costs one 5-minute wait instead of 5 minutes per table.

Tell us how table-level failure handling holds up on your busiest Snowflake pipelines, and which ad platforms you want covered more deeply next.

about 1 month ago

August 2026: Clearer Errors, Centralized Schemas, and Secure File Encryption

ETL & Reverse ETL

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.

2 months ago
Loading more updates...