Celigo platform 2026.4.1 release notes

The Resources menu is now visible to users with Custom (integration-level access) and Monitor all roles. Previously, these users couldn’t see critical shared assets – connections, imports, exports, scripts, lookup caches, on-premise agents, iClients, stacks, APIs, and API tokens – under Resources. Now, their visibility is limited to the integration workspaces to which they have been granted access. Users with manage-level access get full capabilities (edit, debug, clone, delete, view audit logs), while monitor-level users get read-only access with the ability to view details, audit logs, and usage references. This change ensures that every team member can find and inspect the resources used in their integrations, properly scoped to their permissions.

Avoid rebuilding the same logic twice. You can now use a tool as an import step within APIs, making it easy to reuse the business logic you’ve already built with Tools.

Previously, tools were limited to agents and MCP servers. This enhancement brings that same logic into your APIs and keeps your integrations consistent across experiences.

Endpoints used within tools will count toward your supported endpoint limit.

Learn more about tools.

You can now create and manage APIs directly inside an integration using the new APIs tab.

Flow builder and API builder now support direct URL navigation to views at the flow/API level and below:

It’s now easier to bookmark or share an exact builder view and return to work faster without re-navigating through the platform. If a user opens a URL they don’t have access to, an error message is displayed, and the editor experience remains the same.

Mapper 2.0 and Transformation 2.0 now support an expanded Input context option, which lets you reference runtime metadata to access execution details using JSONPath, without relying on handlebars. When you set Input context to...

Mapper 2.0 and Transformation 2.0 now offer a faster, cleaner mapping experience that makes it easier to build, review, and maintain mappings. The mapping workspace is simpler to scan (clearer structure and nesting), quicker to edit (less clicking, easier reordering, smoother row-by-row mapping), and more comfortable for larger mappings and expressions (better use of space and less intrusive layout). Mapping settings have also been streamlined into a lightweight pop-up, and a new Date data type is available for date-specific mapping needs.

Mapper 2.0 now supports converting primitive arrays (string, number, Boolean) into object arrays, so you can turn raw lists into structured records without scripting. When converting, you can map each element into a single key (user-defined or a constant key `value`). Indexing continues to work with this capability, making it easier to reference array elements and complete downstream transformations where unique keys aren’t available.

We’ve added a new hook, preParse, that lets you modify incoming data before it’s parsed. It gives you more control to ensure cleaner, standardized inputs and reduces the need for external pre-processing. You can now convert formats, enrich records, add metadata, or restructure data in real time to handle complex or nonstandard inputs more efficiently.

Building and running flows is now simpler and more predictable. Flow builder introduces a cleaner, responsive header and a streamlined Run experience – so you can focus on building, not figuring out what to click next.

Multifactor authentication (MFA) and single sign-on (SSO) can now coexist on a single user profile with destination-driven enforcement. Previously, enabling SSO effectively overrode MFA settings, creating gaps for users who belong to multiple accounts with different security policies. Now, MFA evaluation is always based on the destination account's policy — not the SSO account’s settings. If you sign in via SSO and the destination account requires MFA, you'll be prompted for MFA after SSO completes; if the destination doesn't require it, you won't be. Trusted-device rules, trust periods, and Do not allow trusted devices settings are all evaluated per destination. When switching between accounts after sign-in, MFA is re-evaluated against the new destination’s policy. The combination ensures consistent, predictable security enforcement no matter how many accounts you work in.

HTTP header name-value pairs now display a handlebars button: {}, making it easier to discover and use dynamic expressions in your header configurations. Click to open the Handlebars expression editor directly from the header row, so you can insert tokens, environment variables, or runtime data into header values without memorizing syntax. This addition standardizes the header configuration experience and encourages safer configurations by making it easier to use dynamic values instead of hard-coded secrets.

Pop-up and panel (sliding overlay) dialogs throughout the Celigo platform now respond consistently to keyboard shortcuts. Press Esc to close any drawer or modal, and press Enter to trigger the primary action, such as Save and Confirm. These shortcuts are context-aware: they won’t interfere when you’re typing in input fields, code editors, list boxes, or other interactive controls. This functionality restores expected keyboard behavior that had regressed during a recent design system update, speeds up common workflows for power users, and brings the platform closer to accessibility standards.

Flow builder just got a major speed boost. Large, complex flows that previously took a while to load now open in under 5 seconds, so you can jump straight into building and editing without the wait. Under the hood, we’ve overhauled Flow builder's rendering architecture — optimizing how steps, connections, and layout are loaded and drawn — so even your most ambitious flows feel snappy and responsive from the moment you open them.