Changelog

October 12, 2026: Integration apps and templates

Shopify–NetSuite billing flow GraphQL migration

The billing sync flow from NetSuite to Shopify moves from the REST transactions endpoint to the Shopify Admin GraphQL API, keeping billing flows working as Shopify deprecates its REST Admin API. Learn more about configuring the GraphQL billing flow.

Shopify–NetSuite SuiteTax compatibility

The Shopify–NetSuite integration app now supports NetSuite SuiteTax, so merchants using SuiteTax as their tax engine can sync orders, refunds, billing, returns, and cancellations without tax handling failures. Previously, the shared eTail engine never enabled SuiteTax behavior for Shopify, which meant import failures, incorrect tax postings, and manual workarounds for anyone on a SuiteTax account. SuiteTax handling now applies across order import, auto-billing for cash sales and invoices, refund import, returns and RMA, cancellation, and order export from NetSuite to Shopify. All three NetSuite tax preferences are supported — NETSUITE_CALCULATES, OVERRIDE_TAX_TOTALS, and TOTAL_TAX_AGAINST_SINGLE_LINE — including tax-inclusive pricing and the breakUpShopifyTaxLines setting. 

Variant-level sales channel publishing for Shopify–NetSuite 

Merchants control sales channel publishing at the product variant level rather than only at the product level.

Shopify–NetSuite refund import fix for third-party return apps 

Resolves under-credited NetSuite credit memos for multi-unit refunds processed through third-party return apps such as ReturnZap and Loop Returns.

Shopify–NetSuite customer deposit fix 

Resolves a long-standing issue where customer deposits were never created in NetSuite for Shopify orders imported while payment was still authorized but uncaptured.

Shopify–NetSuite GL account dropdown fix for GraphQL payout mappings

Resolves an issue where the NetSuite GL account dropdown in the Business entity transaction type to account mapping setting showed only the first 100 accounts. Merchants couldn’t select the accounts they needed when configuring GraphQL payout mappings. The dropdown now includes all eligible accounts, and the refresh controls for Business entity and NetSuite GL account have moved from individual mapping rows to the column headings. Learn more about the refresh options.

Shopify–NetSuite GraphQL payout account mapping fix

Resolves issues with the Shopify payout to NetSuite payout and deposit flow when account mappings are missing. The Business entity transaction type to account mapping setting isn’t populated automatically and must be configured manually. Before enabling the flow, ensure that you must map Charge, Refund, Adjustment, and Variance (catch-all) to NetSuite GL accounts for every business entity that processes payouts, including the primary business entity. Learn more about configuring payout account mappings.

Magento 2 NetSuite integration app SuiteApp migration

The Magento 2 NetSuite integration app moves from bundle-based distribution to a NetSuite SuiteApp, meeting NetSuite's current distribution requirement. Celigo migrates existing customers, and new customers onboard through the SuiteApp. Learn more about Magento 2 - NetSuite integration app SuiteApp migration.

Salesforce NetSuite integration app SuiteApp migration

The Salesforce NetSuite integration app moves from bundle-based distribution to a NetSuite SuiteApp, meeting NetSuite's current distribution requirement. Celigo migrates existing customers, and new customers onboard through the SuiteApp. Learn more about Salesforce - NetSuite integration app SuiteApp migration.
 

October 5, 2026: BYOK agents run code, alerts for long running flows, Mapper & Transformations improvements

Note: These features will roll out throughout the week of October 5, 2026.

💻Code execution for BYOK AI agents

Agents on a bring-your-own-key model connection can run code as a built-in tool, so they compute, transform data, or run logic mid-task without a custom script step.

⏰Alerts for long running flows

Configure email alerts for flows that run longer than expected, rather than discovering a stuck or slow flow from a downstream partner. Set a runtime threshold per flow or as an integration-wide default, where the per-flow value takes precedence. A historical runtime chart covering the last 24 hours, 7 days, 30 days, or 90 days helps you pick a defensible threshold based on how the flow has actually behaved. Learn more about setting alerts for long running flows.

↔️Mapper 2.0 and Transformations 2.0 improvements

Each mapping row gains an overflow menu with Clone row, Clone object/objectArray, and Set inactive. Cloning copies the configuration and leaves destination fields empty, while inactive rows and their children are skipped in preview and flow execution and marked visually; required rows can't be cloned or deactivated. You can name each object inside an object array rather than telling them apart by $, and fields added under one nested object stay scoped to it instead of applying to its siblings. A new Cause record to fail option appears under Action to take if source field has no value in Mapper 2.0 and Action to take if input field has no value in Transformations 2.0, for all import adaptor types. Preview now reflects your latest mapping and body parameter edits immediately, and empty mapping rows are dropped on save. Existing mappings keep their current behavior. Learn more about Mapper 2.0 and Transformation 2.0.

🎫Service principal authentication for Azure Synapse 

The Azure Synapse connector now supports Microsoft Entra service principal authentication using the client secret method. Previously, teams whose Entra ID policies prohibit database-level SQL authentication had to fall back on the Universal JDBC connector with an on-premise agent; now they connect natively. Azure Synapse connections add an Auth type field offering Database user (existing behavior) or Service principal, and service principal connections reuse the same iClient configuration already available on the MS SQL connector. Existing connections continue to work as database user by default, so no migration is required. Learn more about creating an Azure Service Principal iClient. 

📜Certificate-based service principal authentication for MS SQL

The MS SQL connector supports certificate-based authentication for Microsoft Entra service principals, matching Microsoft's guidance to use certificates rather than client secrets. Learn more about the MS SQL connection.

🎚️Simple and HTTP views for webhook listeners

Webhook listener forms add a Simple/HTTP toggle matching the pattern on HTTP connections and exports. Named providers such as Slack, Shopify, GitHub, and Stripe — more than 30 in all — default to the Simple view showing only the required fields, while generic webhooks keep the HTTP view. Switch to HTTP view at any time for verification, challenge responses, and other HTTP-level settings; toggling reveals all stored configuration values. Existing listeners continue to work without changes. Learn more about universal vs. application connectors. 

🏷️XML parser metadata in the HTTP connection view

Exports built on an HTTP connection can configure a custom XML parser directly on the export form. Previously, exports returning XML failed with parser errors because the HTTP connection view had no way to attach parser metadata, forcing a switch to the Simple connection type and back. Learn more about creating an HTTP connection.

🔏PGP encryption for transferred files

PGP-encrypt existing files on transfer, not only files integrator.io generates from records. Imports with Generate files from records set to No now honor Encrypt files, across supported file providers rather than FTP alone, using the connection's existing PGP settings. If you've been pre-encrypting externally, validate output at the destination before removing that step. Learn more about PGP encryption.

🪄Automatic request parameter configuration in API Builder

Query parameters, path parameters, and headers configured on the API request node are added as transformation rules automatically, removing a repetitive mapping step that every API needed before downstream steps could use those values.

B2B - Automated VAN mailbox creation

Setting up a VAN connection is now self-serve. Previously the connection form told you to email Celigo to have a mailbox provisioned by hand; now you create the connection and Celigo provisions the ECGrid account automatically, then emails you its details and setup guidance so you can finish configuring the mailbox yourself. Saving the connection confirms what to expect next rather than leaving you waiting on support. Learn how to set up a VAN connection.

🕵️Rate limit detection for GraphQL connections 

HTTP connections can detect throttling that a GraphQL API reports inside the response body rather than through the HTTP status code. Some GraphQL APIs, most commonly Shopify's, return HTTP 200 even when a request has been throttled.

🖥️Fit-to-screen error management grids

Error management grids auto-fit column widths to your screen by default, so a wide Message column no longer forces horizontal scrolling on smaller displays. 

🐞Step-level debug logs in Tool Builder

Turn on and view runtime debug logs for individual steps while building a tool.

September 25, 2026: Celigo storage query, prebuilt MCP servers in Marketplace

🧮 Query Celigo Storage files

Introduces a read-only REST API for querying and transforming data in Celigo Storage files with SQL. Run queries directly against CSV, JSON, NDJSON, and Parquet files stored in Celigo Storage without impacting existing flows. It eliminates complex multi-flow or data warehouse workarounds by supporting joins, aggregations, window functions, CTEs, subqueries, and folder references (e.g., /staging/orders/). The API delivers fully typed JSON outputs without silent row truncation, provides granular file-parsing configuration, and enforces pre-execution token scope validation to safely reject unauthorized or invalid queries. Learn more about querying Celigo Storage files.

🏪Prebuilt MCP servers in the Marketplace

Browse and search the Marketplace for prebuilt MCP servers, then open a listing to see its tools, prompts, and connections and read any individual tool's input and output schema before you commit. Previously, getting a useful MCP server in front of an AI assistant meant building it yourself, with no way to judge someone else's without recreating it first. Install into your account with prompts for the connection and configuration values the server needs, validated before it goes live, or publish your own server as a Marketplace template. Credentials never travel with a template — sensitive values become placeholders you supply at install. Servers you already built are unaffected. Templates cover tools and prompts; MCP resources aren't included yet, so a server that defines them publishes without them. Learn how to find and install an MCP server template from the Marketplace.

🌊Data ingestion - Chunk-based streaming for merge imports

Merge operations now load to your warehouse in 250 MB chunks, so records become queryable in the destination as each chunk lands rather than only when the full sync finishes. Previously a large merge sync meant hours with nothing available and a restart from scratch if it failed late in the run. Append and replace mode imports are unaffected.

🗂️API group assignment during create, clone, and move

Assign an API to a group when you create, clone, or move it, even before the relative URI is defined. Previously, new APIs landed in the Unassigned group and had to be moved afterward.

September 18, 2026: MCP and Data ingestion

🧩 MCP server upstream connections

Connect a Celigo MCP server to third-party native MCP servers such as Salesforce, HubSpot, and Snowflake, and govern all of their capabilities from one place. Attach an upstream MCP connection to bring in its tools, resources, and prompts, which are discovered automatically and can be enabled or disabled individually. Override the name, description, and annotations on a proxied capability so AI agents see your organization's guidance rather than the generic upstream text, and add Celigo-built capabilities alongside proxied ones on the same server. Your existing governance applies to every call: authentication, end-user groups, capability sets, and request logging. Existing MCP servers are unaffected. Learn more about the MCP server proxy.

🙋 MCP server end-user connections

End users authenticate to downstream apps with their own credentials. A connection can be marked as requiring end-user credentials, and child connections store only the end user's credentials while referencing the parent at runtime. Learn more about MCP server end user connections.

📥Data ingestion - NetSuite JDBC as a Celigo Sync source

Connect NetSuite JDBC as a native source application in the Celigo Sync wizard and select multiple NetSuite objects for a pipeline in a single pass, rather than hand-writing a separate query per object. For detailed information on sync, see Create a sync from NetSuite JDBC.

📥Data ingestion - Microsoft SQL Server as a Celigo Sync destination

Load data through Celigo Sync into Microsoft SQL Server, which joins Snowflake and NetSuite Analytics Warehouse as a destination for sync pipelines. For detailed information on the sync, see Create a sync to Microsoft SQL.

📥Data ingestion - Object-level selection for manual runs and full resyncs 

Choose which objects to include when you start a manual run or a full resync on a sync, instead of running every object each time. Resync a single object after adding a column at the source, or re-run only the objects that failed. The selection list shows each object's last-run status, and objects you don't select keep their data, sync state, and last-run status untouched. Run details reflect only what you selected, so record counts, durations, and errors match the actual run. Running with all objects selected behaves as it does today, and scheduled runs continue to process every object on the sync. Learn how to choose objects to include in a sync.

September 16, 2026: SFTP file server, Celigo Topics, SCIM, MCP rate limits, network policies, and more

📁 Celigo-hosted SFTP file server

Give every trading partner a secure SFTP endpoint hosted by Celigo, with no servers to run on either side. Enable a hosted file server per environment, then create an isolated account per partner with its own password and a Celigo Storage folder as its locked home directory. Partners connect with any standard SFTP client on port 22, and the files they upload become ordinary Celigo Storage files the moment they arrive — visible in the Storage UI, governed by storage usage, and consumable by flows through the Celigo APIs connector. Learn more about the Celigo-hosted file server.

📡 Celigo Topics

🪪 SCIM provisioning

Automate user lifecycle management from your identity provider. Provision and deprovision the people who build and operate integrations from a new SCIM Provisioning section in the account's Security and SSO settings, and manage end users from a matching section in each external IdP configuration. Learn more about provisioning users with SCIM.

🚦MCP server rate limits and usage quotas

Configure three optional traffic limits on each MCP server. A rate limit caps the total tool calls the server accepts in a time interval, protecting downstream systems from bursts. A per-user rate limit gives every end user their own allowance, so a single runaway AI agent can't consume the server's capacity and degrade service for everyone else. A usage quota caps cumulative tool calls over a longer period. When a limit is reached, requests receive a standard 429 response telling the client when to retry, and throttled requests appear in the MCP server logs with the consumer's identity. All three are optional — leave them blank for unlimited access.  Learn more about MCP server rate limits and usage.

Intelligent document processing for AI agents

AI agents extract structured data from invoices, purchase orders, and Excel files into a schema you define, with field-level confidence signals. Agents detect document extraction intent and invoke processing automatically, with no setup beyond the existing agent schema. Learn how to extract data from documents with an AI agent.

🧱Network policies

Administrators can now define reusable IPv4/IPv6 allow and deny lists under Settings > Security and apply them across workspace logins, MCP servers, end-user authentication, and API tokens without re-entering ranges (PATs inherit workspace policies automatically). Deny lists take precedence, empty allow lists leave access unrestricted, and enforcement only begins once a CIDR is configured, ensuring existing endpoints experience no immediate behavior changes. Blocked logins and calls are recorded in audit and request logs, and full CRUD API support is available for programmatic management.  Learn more about network policies.

📑B2B - EDI support for file provider connectors

Parse and generate EDI X12 and EDIFACT documents on file provider connectors, including Google Drive, Box, Dropbox, Azure Blob Storage, Google Cloud Storage, and Celigo Storage. EDI profiles were previously available only on FTP, S3, AS2, and VAN, so EDI flows had to route through one of those systems regardless of where the trading partner actually exchanged files. Choose EDI X12 or EDIFACT as the file type on a file provider export, import, or lookup, then select an EDI profile exactly as you would on an FTP or S3 flow step. Parsing and generator definitions, processing of parsed data, and functional acknowledgement generation behave the same as on FTP and S3, and Celigo Storage now handles EDI, so you can stage EDI documents between flows without external file infrastructure. Configure it through the UI or the v1 API. Existing EDI flows on FTP, S3, AS2, and VAN are unchanged. Read about the EDI connectors for B2B manager.

🔐Tenant-wide SSO enforcement

A new account-level setting requires every user to sign in through the identity provider, so no one is left on optional SSO. Account owners can now require SSO for themselves as well, which was previously impossible and removes the last username and password path into the account; that change is confirmed with a live SSO re-authentication first to protect against lockout. If the identity provider becomes unavailable, access is restored through a support-assisted, identity-verified recovery process. Both settings are off by default. Learn more about requiring SSO for the account owner and all account users.

☑️ Object-level selection for manual runs and full resyncs 

Choose which objects to include when you start a manual run or a full resync on a sync, instead of running every object each time. Resync a single object after adding a column at the source, or re-run only the objects that failed. The selection list shows each object's last-run status, and objects you don't select keep their data, sync state, and last-run status untouched. Run details reflect only what you selected, so record counts, durations, and errors match the actual run. Running with all objects selected behaves as it does today, and scheduled runs continue to process every object on the sync. Learn how to choose objects to include in a sync.

💾 Shift JIS file encoding on FTP and file connectors

Choose Shift JIS as the file encoding when you export, look up, import, or transfer files on FTP, SFTP, FTPS, and other file connectors. Japanese files encoded in Shift JIS show the correct characters in preview and in your flow, and files you write back use the encoding the destination system expects. See File transfers. 

September 2, 2026: Celigo Storage, AI agent models

📁 Celigo Storage integration folders and token path scoping

Each integration now gets its own system folder, with permissions inherited from your existing access control, so Manage All, Monitor All, and Custom-role users reach Storage through their integrations rather than needing account-wide access. API tokens can be scoped to specific folder paths, limiting what a given credential can read or write.

Celigo Storage overview

Work with files and folders in integrator.io

Restrict an API token to specific Celigo Storage paths

Four more model providers for AI agents and guardrails

• Mistral, xAI, Hugging Face, and DeepSeek join OpenAI, Gemini, and Anthropic in the model picker — BYOK via your own provider connection, and AI Credits are not charged for BYOK runs
• Agent and guardrail settings adapt to the selected model — you only see the controls that model supports
• Existing agents are untouched, and invalid provider/model/option combos are rejected on save with an error that names the problem

August 31, 2026: NetSuite REST API support, Anthropic in Celigo AI

🛠️ NetSuite REST API Support (SuiteTalk + Custom RESTlets)

The NetSuite connector now supports REST APIs as a first-class API type for record-based exports, lookups, and imports — covering both SuiteTalk REST Web Services and Custom RESTlets, directly within the NetSuite connector without requiring a separate generic HTTP connection.

Why it matters:

NetSuite’s Saved Search — the basis of most existing NetSuite exports — is known to be inefficient at high volumes. SuiteTalk REST Web Services provide a faster, simpler alternative for large-volume and data warehousing workflows, and don’t require the additional SuiteAnalytics Connect license that the JDBC approach requires. REST also gives builders simpler access to custom records and fields. With this addition, Celigo now supports all three major ways to integrate with NetSuite: Celigo RESTlets, SOAP Web Services, and SuiteTalk REST.

Who it's for:

Builders running high-volume NetSuite integrations or data warehousing workflows, and developers who prefer REST over SOAP or need direct access to custom NetSuite record types.

What changed:

New API type in the NetSuite connector. A REST APIs option is now available in the “How would you like the records exported/imported?” selector on record-based NetSuite export, lookup, and import steps. Selecting REST APIs exposes two sub-options: SuiteTalk (configurable via a NetSuite-oriented Simple view or an HTTP view for advanced control) and Custom RESTlets (configurable via HTTP view). The platform automatically sets the appropriate NetSuite REST base URI based on the selection. File-based flows are unaffected. Existing Celigo RESTlets, SOAP Web Services, and generic HTTP-based integrations continue to work unchanged.

Import NetSuite data

Export NetSuite data

🛠️ Anthropic (Claude) in Celigo AI [Improved]

You can now run AI agents on Claude models without bringing your own Anthropic API key. 

Why it matters:

Until now, using Claude in Celigo meant BYOK — your own Anthropic account, key management, and separate billing. That's gone: Claude is now hosted under Celigo AI, selectable just like OpenAI and Gemini, with usage billed through Celigo.

Who it's for:

Anyone building with AI agents, guardrails, or AI chat — especially teams without their own Anthropic agreement 

What changed:

• Claude models (Opus, Sonnet, and Haiku) are now selectable under the Celigo AI source for AI agents, guardrails, and chat.
• Full parity with OpenAI and Gemini — tool calls (IO tools and MCP servers), structured outputs, streaming, extended thinking, and Anthropic web search.
• BYOK is unchanged — existing Anthropic, OpenAI, and Gemini setups keep working as-is.

Learn about Celigo AI agents