Enterprise-grade logging captures a complete picture of each flow run to provide visibility into how each record was processed. This enhancement aids in troubleshooting and auditing by exposing a unified and consistent view of flow execution across development, testing, and production phases.
Run history now includes details for all “retry jobs” (which previously appeared only in error management), as well as “in-progress jobs” (which previously appeared only in the Run console). These changes allow the Run history view to serve as the single place to go for visibility for all current and historical runs.
We’ve refined the preview section to give you more flexibility, clarity, and visibility when working with data.
-
Improved record exploration: You have the flexibility to view one or all records and explore individual records in a tree structure for better readability and easy drill down into arrays.
-
Resizable configuration pane: You can now resize the configuration pane to view more of the record or configuration details, reducing the need for scrolling and improving focus on specific sections.
-
Clearer Simple/HTTP toggle placement : The Simple/HTTP toggle has been repositioned to clearly indicate which parts of the configuration are affected when switching modes.
-
Mock data difference indicator: Additionally, a new visual indicator highlights when saved mock data differs from the input received from the application, improving visibility into discrepancies that may cause variations in downstream results.
We’re introducing a visual editor for multi-instance flows, a more user friendly way to select customizable fields and create instances. With multi-instance flows, you can:
-
Define the primary business logic: Create a single base flow that captures your core business requirements and mark it as ready to support instances.
-
Select the properties you want to override in each instance: Property picker lets you select the list of properties, such as connections and mappings, from your base flow. You can then change these settings for each instance.
-
Create an instance: Create the instance by providing values only for the properties that you select as customizable.
-
Operate independently: Run, schedule, and manage errors in each instance on its own, while still part of a unified design.
-
Simplify maintenance: Roll out common changes across all instances in one go by updating the base flow, while still keeping the option to make updates unique to a specific instance.
We’ve optimized lookup caches behind the scenes, especially for larger datasets. No setup is required on your side.
As part of this update, the endpoint v1/lookupcaches/<lookupCacheId>/getdata?startAfterKey=... is deprecated. Pagination via nextPageURL remains unchanged and fully supported. You may notice a different ordering of key-value pairs in results, though it doesn’t reflect any changes to the data accuracy or pagination.
-
We’ve updated the left navigation menu by renaming Tools to Build to better reflect its purpose and make it easier for you to find integration-development features.
-
We’ve also renamed Agents to On-premise agents throughout the product to provide clearer context on their role and usage.
-
You can now customize table layouts by resizing and reordering columns. Drag columns to change their position and adjust column widths as needed; your preferred column order is saved as a user-specific preference, so tables will remember your layout the next time you return.
Role behavior has been updated to better align monitor and manage access with how teams actually work:
-
Monitor users can run delta flows: Monitor all and monitor custom users can now run automatic and custom delta flows from the existing Run options anywhere they already have monitor access (no new setting).
-
Manage users can delete integrations: Users with the manage role now see the standard Delete integration action with the same confirmation dialog and safeguards as admins.
-
New “Users can edit retry data” setting: Under My account > Users > Manage user > Additional permissions, admins now see a Users can edit retry data option for monitor all and custom roles; when turned off, monitor users can still view retry data, retry flows, and resolve errors, but cannot edit the retry data itself.
We’ve updated how releases are distributed so that you always get the latest version without losing work. The platform now detects new builds in the background and silently reloads only when you navigate away from work you had in flight, so your session stays active and any in-progress changes are preserved.
As part of ongoing platform upgrades, Celigo has updated its JavaScript engine to the latest long-term support (LTS) version. You now have access to a wide range of modern JavaScript features, including optional chaining; replaceAll; nullish coalescing; logical assignment operators; new array methods .at, .toSorted, .toReversed, .toSpliced, .with; findLast and findLastIndex; and Object.groupBy and Map.groupBy. With this update, you can write cleaner, more powerful scripts while ensuring long-term compatibility with the latest JavaScript standards.
The on-prem file connector allows you to access files stored in a secure environment, such as private networks that can’t be accessed directly. With this new connector, you can build automations that retrieve files from local storage and push them to a cloud system
Easily debug connection issues with access to the log file. Now you can view the underlying API calls, including requests, responses, and status codes made during connection establishment for all HTTP connectors.
For eligible subscriptions, we’ve increased the maximum configurable concurrency per connection from 25 to 50, providing additional capacity for high-volume integrations and enabling faster end-to-end processing. This change does not affect existing connections. To take advantage of the higher limit, update Max concurrency in the connection settings — now configurable from 1 – 50.
-
Included with Enterprise accounts
-
Available as an add-on for Professional accounts
Some APIs require extra authentication to access files stored in cloud locations, while others do not. Previously, the Celigo platform always attempted authentication, causing errors for APIs that didn’t expect it. This enhancement lets you avoid those conflicts and ensure smoother file downloads.
-
New checkbox controls whether authentication is required when downloading files/attachments from API response URLs.
-
This option appears only when Path to file URLs in the HTTP response body is configured.
-
Prevents unnecessary auth attempts that cause download failures.
-
Ensures compatibility with a wider range of APIs.
-
Improves reliability and user experience.
-
Checked: Send additional authentication before downloading files.
-
Unchecked (default): Skip extra auth.
Change Data Capture (CDC) for SQL Server is now available in Celigo integrator.io, giving you a low-impact alternative to heavy full-table scans and frequent polling on production databases. CDC streams only row-level inserts, updates, and deletes in near real time, so you can use the same change feed both to drive app-to-app integrations and to land before/after versions of each row into your analytics database or warehouse for history tracking and reporting.
Webhook listeners now support PUT requests in addition to POST, enabling seamless integrations with SaaS platforms, such as Zoho, that use PUT for record updates. PUT requests are handled the same way as POST—including payload processing, filters, authentication, size limits, and downstream logic—while existing POST-only configurations continue to work without any changes.
-
BarTender: Enhanced the connector to support multiple APIs and added endpoints.
-
Bill.com: Enhanced the connector to support multiple APIs and added endpoints.
-
Chargify: Rebranded the Chargify connector to Maxio, added Subdomain and Environment settings, along with new endpoints.
-
Greenhouse: Enhanced the connector to support multiple API.
-
Microsoft Planner: Celigo is hosting the iClient details for this connector. Therefore, the iClient setting has been removed from the connection, and you do not have to provide iClient details for these connections.
-
Seismic: Enhanced the connector by adding the Environment setting to the Seismic API type and removing deprecated endpoints.
-
Walmart: Enhanced connector with OAuth 2.0 authentication support for all API types.
-
Zoho Desk: Enhanced the connector by adding the Region setting.
You can now keep track of your API entitlements and monitor your usage without leaving the Celigo platform. Navigate to Account > Subscription to track your API call usage, including the following activity:
-
Custom APIs built with API Builder or JavaScript
-
Import and export APIs
-
APIs proxied in API Management
You’ll also see a breakdown of API call usage, allowing you to sort and filter by environment and API type (API builder, JavaScript, or other resources), to identify your most frequently used APIs and uncover valuable insights.
Each account includes a built-in monthly allotment of API calls, with the flexibility to scale through additional API call add-ons or API Management. Historical usage data is also available, making it easy to choose the plan that best fits your needs.
Integration app developers can now provision licenses across multiple environments at a global level, allowing greater flexibility in license allocation. Register and maintain your apps more efficiently, reduce manual overhead and complexity for RevOps, and allow customers to deploy apps across environments with consistent licensing.
We're excited to announce the general availability of the Celigo MCP Server, the standardized way to expose your Celigo APIs, integrations, and logic to AI Agents securely, using the Model Context Protocol (MCP). The MCP Server transforms your internal automations into a stable, scalable foundation for AI-powered flows, enabling your AI assistants and agents to reliably discover, understand, and invoke your business capabilities with clarity and control.
-
Access thousands of apps: Power AI assistants and agents with governed access to thousands of apps by leveraging the comprehensive library of Celigo prebuilt connectors.
-
Expose custom business capabilities: Because every business operates differently, you can expose APIs and contextual business logic (built in API Builder) so your AI agents can act with precision tailored to your workflows.
-
Managed MCP Gateway: Publish your APIs safely using a managed MCP gateway that enforces governance.
-
Fine-grain security: Safely expose your Celigo APIs as MCP tools, complete with necessary scopes and authentication.
-
Full compliance: Maintain full governance, safety, and control with comprehensive audit logging of all agent interactions.
-
Isolate by use case: Create any number of MCP Server endpoints, each with a curated tool catalog and environment isolation for specific AI applications.
-
Broadly compatible: Invoke your MCP Server from any MCP-compatible assistant, IDE, or agent framework, regardless of where the agent is built (such as in OpenAI or Claude). Your business logic and APIs become universally accessible to AI systems without custom adapters or lock-in.
-
Simple licensing: All platform editions will include entitlement to create MCP Servers, metered simply as API calls within your existing entitlement.