The July 2026.7.1 release expands Celigo's agentic and analytics capabilities while deepening platform lifecycle management. Celigo Sync introduces app-driven data ingestion into analytical destinations, the Celigo MCP Server gains full create, update, and delete operations, and the AI Agent adds Anthropic Claude as a provider. Platform updates bring Handlebars expressions to filters and branching, and lifecycle management for APIs and Tools, alongside faster bulk loading, expanded connectivity, and a new first-party command-line tool.
-
Celigo Sync: Introduces a new, app-driven data ingestion experience that replicates large-volume operational data from Salesforce and NetSuite (plus 600+ connectors in export mode) directly into analytical destinations like Snowflake and NetSuite Analytics Warehouse. It automates historical backfills, manages incremental syncs, and adapts automatically to schema drift and data type changes from source systems. Out-of-the-box normalization, flattening, and masking options ensure data arrives ready for analysis. Learn more about Celigo Sync.
-
Celigo MCP Server phase 2 — full CRUD: The Celigo MCP Server now supports full create, update, and delete operations across all core integration resources — connections, flows, scripts, APIs, and tools — allowing compatible AI agents to build and manage integrations end-to-end via natural language. A masked-credential guard prevents accidental overwrites, a dry-run step catches invalid configurations before they are written, and a new kb_answer tool lets agents query the Celigo Knowledge Base inline. All operations respect existing role-based access control RBAC permissions. Learn more about Celigo MCP server and CLI.
-
Anthropic (Claude) provider support for AI Agent — BYOK: Anthropic provider support to Celigo AI Agent - BYOK): Celigo AI Agent now supports Anthropic Claude as a third LLM provider alongside OpenAI and Gemini. Connect your own Anthropic API key to run AI Agent flows powered by Claude with full feature parity, including tool invocation, structured outputs, multi-step reasoning, and guardrails. Claude-specific capabilities such as extended thinking and hosted web search are also available. Note: this release is BYOK only — Celigo-hosted Anthropic billing will follow in a future release. Learn more about AI agent - BYOK.
-
Governed MCP resources for AI agents: MCP servers now support governed, read-only resources, and you can add those resources to an AI agent so it pulls reference content — policies, schemas, documentation, and other static context — from connected MCP servers without a custom integration per data source. Teams define a secure source of truth once and control which agents can access it, so agents discover and use the same context consistently. Learn more about resources for MCP server and AI agents.
-
Developer platform: One home for building on integrator.io: the REST API, the Celigo CLI, and Platform MCP, all sharing a single API token. Guides, full references, and a running changelog sit side by side, so you can go from your first API call to a fully scripted or AI-driven integration without leaving the docs. Everything is continuously published from version-controlled sources through automated pipelines — and the same specs and skills that power the docs also drive the CLI and MCP tools, so references, command help, and AI-agent tooling never drift out of sync. Full documentation at developer.celigo.com.
-
REST APIs: The entire integrator.io REST API is documented: every endpoint typed, versioned, and browsable, with guides for authentication, pagination, rate limits, errors, and EU/region routing. The reference is generated straight from the OpenAPI specifications that define the API and synced automatically, so it updates the moment the platform does — no manual drift. Those same specs power the CLI's bundled skills and Platform MCP's schema tools, keeping code, terminal, and AI agents working from one source of truth. Full documentation at developer.celigo.com/api.
-
Platform MCP: Celigo Platform MCP Server phase 1 feedback & phase 2 development): A new hosted, remote MCP server that connects AI agents — Claude, Cursor, VS Code, ChatGPT, and any MCP-compatible client — to your integrator.io account. Agents inspect, build, run, and troubleshoot integrations end-to-end in natural language, with full CRUD, flow runs, and error triage — protected by masked-credential and dry-run safeguards and your existing RBAC. Full documentation at developer.celigo.com/mcp.
-
CLI: A new first-party command-line tool for driving integrator.io. Anything available through the REST API is accessible via celigo <cmd>, with support for profiles, safer writes, and account-wide utilities. Available on npm as @celigo/celigo-cli, requires Node.js 22, and licensed under MIT. Full documentation at developer.celigo.com/cli.
-
Handlebars expressions in filters and branching: Builders can now use Handlebars expressions in input filters, branching, and output filters to format or manipulate record values without writing scripts. Select
Expressionas the operand type to build and preview expressions with inline suggestions and validation. This works across flows, APIs, and tools and is backward compatible with existing expressions. Learn more about filters or branch rules -
API lifecycle management: APIs now participate in the same Integration Lifecycle Management model as flows, with full support for revisions, cloning, pull/merge, and environment promotion. APIs travel with integration bundles during download/upload, and configurable ignore fields let teams exclude environment-specific values during promotion. Learn more about Integration Lifecycle Management.
-
Standalone flows consolidation: Flows are now always created and managed within integrations. Existing standalone flows are automatically migrated into a new "Standalone flows" integration. The Detach/Attach action is replaced with a Move action, and new connections include an integrated multiselect field to bind them to specific integrations on setup.
-
Tool cloning: You can now clone Tools created with Tool Builder to quickly generate a copy for editing or to promote a Tool across environments — from QA to staging or staging to production — without manually rebuilding its configuration. Dependencies such as connections, scripts, nested tools, and lookup caches are resolved automatically during promotion. Learn more about tool cloning.
-
Mapper 2.0 support for complex field types: Mapper 2.0 now supports Handlebars expressions for
Object,ObjectArray, and primitive array fields across exports, lookups, and imports. Expressions can be validated and previewed directly in the Mapper UI, enabling more flexible data transformations for complex API requirements. Learn more about Mapper 2.0. -
Integration Lifecycle Management (ILM) for Tools: Tools are now fully integrated into the ILM workflows. You can create snapshots, clone Tools within or across environments, promote changes via pull/merge, and download/upload integration bundles that include Tools — the same pattern teams already use for flows. Learn more about ILM for tools.
-
Personal access tokens: You can now create Personal Access Tokens (PATs) to authenticate with the Celigo API using your own user permissions. Unlike standard API tokens, PATs inherit your account permissions automatically, so there's no scope to configure. PATs are available to all users (including manage and monitor roles), and they default to a 90-day expiration to encourage regular rotation. Admins can revoke PATs across the account for security oversight, but they cannot view PATs they did not create. Learn more about Personal access tokens.
-
Optimized bulk load for SQL server imports: SQL Server imports now support file-based optimized bulk loading. Previously, integrator.io inserted records one at a time; now it aggregates them into files and loads them in bulk, running up to 5x faster or more on imports over 100K records. The new optimized bulk load query type is the default for new imports and supports automatic upsert through a MERGE. No migration is required — existing imports keep their current query type. Learn more about the optimized bulk load option
-
Celigo storage for MCP servers: Introduces a platform-managed file storage resource under Resources → File storage that allows you to store, organize, and browse MCP server files directly inside integrator.io — no external SFTP servers or S3 buckets required.
-
Global flows and APIs pages: Centralized Flows and APIs pages are now accessible directly from the left navigation, letting you search, sort, filter, and take operational actions across all integrations simultaneously from a unified layout.
-
Error management UX improvements : The error management page now remembers your preferred layout — visible columns, column order, column widths, and error details pane state — so you can resume triage without reconfiguring each session. Previously, you reset your view at the start of every session; now layout preferences save automatically per user and persist across sessions and environments. Learn more about the errors page
-
“Used by” indicator for shared resources: A new indicator now appears in the header when editing shared resources that are referenced by more than one flow or step, alerting you that changes will affect multiple areas and providing a direct link to view all impacted locations before you save.
-
File metadata in Transformation 2.0: Expose
fileMetain Transformation 2.0 envelope context for file provider exports and lookups): File name, file size, and last modified time are now accessible directly in Transformation 2.0 rules and JavaScript tasks on file provider steps, letting no-code builders reference these attributes inline without apreSavePagehook. Supported across FTP/SFTP, Amazon S3, AS2, Google Drive, Box, Dropbox, NetSuite File Cabinet, and HTTP File. Learn more about Transformation 2.0. -
Redesigned account settings: The Account area has been reorganized into focused sections — My profile, Company, Users, Subscription, Security, Environments, and Transfer — replacing the previous mixed list of settings. Each section uses in-page side navigation to group related settings.
-
Trace key uniqueness: Enhance trace key uniqueness logic (Extend max length to 256 and truncate from middle, if it exceeds 256)): Trace keys in integrator.io now support up to 256 characters (previously 128), and when a key exceeds that limit, truncation removes characters from the middle rather than the end — keeping both the start and end of the key visible. This prevents different keys from appearing identical after truncation, reducing false duplicate detection and misleading error logs. Learn more about trace key.
-
Shopify OAuth 2.0 connection setup in shared accounts: Fixed an issue where users in shared-account setups couldn't create a Shopify OAuth 2.0 connection in production. The shared-account context was lost during the OAuth callback flow, causing connection setup to fail. The fix carries the shared-account context through to the final connection save.
-
Consistent date formatting for job object fields: Date fields on the job object, such as
job.parentJob.startedAt, now use one consistent format in both the preview and at runtime. Previously, the preview showed ISO 8601 (for example,2025-03-13T06:02:06.609Z) while a flow run produced a long-form format (Thu Mar 13 2025 05:46:43 GMT+0000 (Coordinated Universal Time)), so mappings that looked correct in the preview could behave unexpectedly when the flow ran. What you see in the preview now matches what you see in the run.Note
-
If your flows require the data in the old date format and you haven't applied any date formatting, then they will be impacted by this change. You must update the date field to the long form format by using
{{dateFormat job.parentJob.startedAt 'ddd MMM DD YYYY HH:mm:ss [GMT+0000] (Coordinated Universal Time)' 'UTC'}}to avoid your flows from breaking or producing bad data. -
If your flows pass the data using the handlebars format, then they will not be impacted by this change.
-
-
Mapper 2.0 instant editor load : The Mapper 2.0 editor now opens your saved mapping configuration instantly. You can now map rows, expressions, hardcoded values, and the toolbar right away while preview data loads in the background. If preview fails, the editor stays functional with a Retry action.
-
Google BigQuery optimized bulk load: BigQuery imports now support file-based optimized bulk loading, delivering up to 5x speed improvements for imports over 100K records. A new "Use optimized bulk load" query type is the default for new imports and supports automatic MERGE (upsert) behavior via optional primary key configuration. Learn more about the optimized bulk load option
-
PostgreSQL real-time CDC exports: The PostgreSQL connector now supports a real-time export mode that listens for change data capture (CDC) events — inserts, updates, and deletes — without polling or batch queries, enabling near-instant propagation to downstream systems. SAP S/4HANA IP-based connection reliability (T3 IO-144089: Support IP-based SAP S/4HANA connections with app-aware CSRF handling): Celigo now applies CSRF token handling and cookie management based on application type rather than domain name detection. Integrations connecting to SAP S/4HANA via IP address will no longer fail with "CSRF token validation failed" errors. Learn how to listen for real-time changes from PostgreSQL.
-
Visual folder browsing for cloud storage — Browse Mode: Browse mode is now available for Google Drive, Box, and Dropbox, letting you visually navigate and select folders without typing paths. Browse mode is the default for new file-based configurations on these providers and stores the folder's unique identifier internally, eliminating runtime path resolution errors. Azure Blob Storage gets a Browse button alongside the Handlebars button.
-
NetSuite REST API support: The NetSuite connector now supports REST APIs for record-based exports and imports, adding support for SuiteTalk and Custom RESTlets directly within the connector without requiring a separate HTTP connection.
-
Salesforce related list Order By fix: The Order By field in Salesforce listener related list configuration now includes child sObject fields such as CreatedDate, Name, and lookup fields, restoring expected sort behavior for related list data.
-
Amazon S3 IAM role authentication: Amazon S3 connections now support IAM role-based authentication as an alternative to static access keys. Provide a Role ARN and Celigo-generated External ID, and Celigo assumes the role via AWS STS using temporary, short-lived credentials — eliminating the need to store or rotate long-lived keys.
-
Ryder: Freight and logistics management, shipment tracking, and cartonization.
-
Salesforce Marketing Cloud: Email campaign management, customer journey automation, and audience segmentation.
-
Unbounce: Landing page management, lead capture, and conversion optimization.
-
Veeqo: Multi-channel order management, shipping label generation, and inventory sync.
-
Microsoft Fabric: Added API types and endpoints
-
Nodus Payfabric: Expanded API coverage with additional endpoints.
-
Sage Intacct: Expanded API coverage with additional endpoints.
-
Shopee: Expanded API coverage with additional endpoints.
-
TikTok: Expanded API coverage with additional TikTok Ads endpoints.
-
TikTok Shop: Expanded API coverage with additional endpoints.
APIs now participate in the same Integration Lifecycle Management model as flows - with full support for revisions, cloning, pull/ merge, and environment promotion.
Until now, APIs lived outside the integration lifecycle — teams couldn't snapshot, clone, or promote API changes alongside their flows. This forced manual tracking, increased the risk of configuration drift across environments, and slowed down teams iterating on APIs and flows together.
With full ILM support, APIs now follow the same workflows teams already use for flows. Environment promotions are safer because APIs travel with the integration bundle, parallel development works because clones capture complete integration state, and rollbacks are reliable because revisions include APIs — not just flows. For teams operating across multiple environments or coordinating API changes across developers, this eliminates a significant operational gap.
All users managing APIs within integrations will be able to use this functionality. The following platform capabilities are added to manage the API lifecycle in an Integration tile:
-
Revisions: Create a snapshot/revision for an integration including APIs. Revert to a previous snapshot which restores the API state along with flows.
Download/upload: Download and upload integration bundles (.zip) that include APIs, with source IDs preserved.
-
Cloning: Clone an API within an integration, or clone an entire integration containing APIs.
-
Pull/merge: Promote API changes from a clone to the original integration using the same pull/merge workflow used for flows. A new APIs section appears on the Review Changes page, and changed API details are visible in the "View resource changed" tab.
-
Parallel development: Multiple clones can be used for parallel API development without relying on external tracking - the same pattern teams already use for flows.
-
Configurable ignore fields: Selected API fields (name, version, relative URI) can be excluded from pull/merge to avoid overwriting environment-specific values.
-
-
Update customer deposit mappings to use Shopify paymentId: The etail transaction Id is not coming up for Customer Deposit record): Shopify has deprecated the Order Transaction authorizationCode field and replaced it with the paymentId field. See Deprecation of OrderTransaction.authorizationCode for the Shopify deprecation announcement. In the Post customer deposit to NetSuite import of the Shopify transaction to NetSuite customer deposit (add) flow, replace the mapping from authorizationCode to paymentId for the NetSuite P/N Ref. field. New installations use paymentId by default.
-
-
-
Duplicate customer record fix: When a customer's email is updated in NetSuite, the flow now uses the existing Magento Customer ID to locate and update the correct Magento record instead of creating a duplicate. Fallback to email and website_id lookup is preserved for customers without a Magento Customer ID on file.
-
Adobe Commerce 2.4.9 compatibility for the NetSuite – Adobe Commerce connector: The Celigo NetSuite Connector for Adobe Commerce now runs on Adobe Commerce (Magento) 2.4.9, so you can upgrade to 2.4.9 without losing your Celigo integration. The connector has been validated against the new release, which moves to PHP 8.5/8.4, an updated framework stack, and new infrastructure. Adobe removes any extension that isn't 2.4.9-compatible from the Commerce Marketplace on August 14, 2026, so this update keeps the connector available there.
-