Changelog

Michelle Welch

Updated September 08, 2026 17:28

September 4, 2026:

✨ Celigo Ora release notes

This week, Ora expands what admins can do with MCP end users, sees deeper into API and Tool run history, and works more fluidly across multi-instance flows and multi-environment accounts. It also speaks the platform's newest Handlebars additions and recognizes three new file providers, with clearer file-metadata handling across the board.

Know and manage who's using your MCP servers

See who's using your MCP servers: Ask "who are my end users," "did Jane accept her invite," or "who's in the Finance group," and Ora answers from live rosters and group membership across the account.
Understand exactly what access someone has: Ask what a specific end user or MCP server grants, and Ora shows which direct, group, or role grant delivers each permission, and flags access that's granted but unusable.
Find and trace end users from any page: Search the account for an end user or group by name or email and see their groups, servers, and invite status. Ask what would be affected if you deleted an MCP server, and Ora lists every end user and group that would lose access. This data stays visible to admins only.
Invite, revoke, and manage end users and groups from chat: Ask Ora to invite or revoke an end user, or create, update, and manage end-user groups and membership. Every change stages as an approval card first, and the audit log attributes it to Ora.
Grant MCP server access by group: Ask Ora to give a group access to an MCP server, and it stages the grant with a before-and-after summary.

Review your history

Ask about API and Tool run history: Ask Ora to show an API's failed requests from last week, its busiest hours, or when a specific record came through. Ora walks a single request step by step with the exact payloads, and can turn log capture on or off or purge logs on request. The same capability extends to Tools, and activates automatically once the platform's Tool invocation history feature is live.
See exactly what Ora has changed: Ask "what has Ora changed recently," and Ora now queries the audit log using the platform's dedicated attribution source, so its own changes are correctly identified.

Work across flows and environments

Work with multi-instance flows: Ask about a multi-instance (template) flow, and Ora lists every instance and which are enabled. Ask Ora to run every instance of a flow, and it starts each enabled instance, skips paused ones and the template itself, and reports what actually ran.
Work across production and sandbox: Ora now knows that environments are separate accounts under the hood. Point it at a resource in another environment, and it explains the boundary instead of guessing wrong. Ask it to copy your sandbox mappings to production, and Ora writes a ready-to-paste handoff message for the Ora session in that environment, which does the work and replies with an answer to paste back.
Trace exactly where a flow's data stops: Ask why data isn't reaching a step, and Ora runs the flow in test mode and narrates the record's journey, including which branch it took, which filter dropped it, and where it stalled, even on flows that have never run. Ora can show the exact request a step would send without leaving the building, or, only when you say so, actually send it and show the real response.

Write smarter templates and imports

Author date math with readable units: Ask Ora to add three days to a date, and it produces {{dateAdd date 3 "d"}} with readable interval units instead of raw milliseconds.
Read a lookup cache directly in a template: Templates can now pull a value straight from a lookup cache with {{getLookupCacheData}}, and the template editor validates the result against your real integration and flow context.
Fan out AI agent and guardrail imports: Ora now understands one-to-many fan-out for AI agent and guardrail imports, where a single incoming record with an array becomes one agent invocation per child element.

Handle more files, more precisely

Move files from more providers: Ora now treats Google Cloud Storage, ADLS Gen2, and Celigo APIs as full file providers. Ask it to move files from a GCS bucket, and it builds the correct folder-transfer flow, including GCS's own bucket-and-key-prefix addressing.
Stamp file provenance on more exports: File-reading exports and lookups across FTP, S3, AS2, local file system, NetSuite file cabinet, and cloud-storage folders can now stamp each record with the source file's name, size, and last-modified date.
Get a clear answer when a stamp isn't possible: If you ask for a file-provenance stamp on a step that doesn't read files, Ora explains why that can't work and offers a record-field alternative instead of quietly saving something broken.
Retarget file exports by folder: Ora can now point a file-provider export at a new folder ID directly, updating the real directory binding rather than the display path alone.

September 2, 2026:

✨ Celigo Ora release notes: Beta through GA

From the March 2026 beta to general availability, new Celigo Ora capabilities brought major enhancements to the integrator.io platform. You can now leverage flexible interaction options, deeper account-specific context, dynamic error diagnosis, and tighter change guardrails. Additionally, these features deliver expanded search, approval, and audit capabilities across the entire environment. The following sections outline what shipped by capability area.

Talk to Ora your way

Run multiple conversations at once: Open Ora in several browser tabs, or start several conversations in one tab, and keep separate pieces of work moving in parallel.
Dictate instead of typing: Speak your prompt, and Ora transcribes it, including long dictations, in your language.
Attach files and screenshots: Drop an error screenshot, a CSV, or an API spec into the chat, and have Ora work from it. You can add references to Celigo Storage files in your chats.
Ora inside the mapping and expression editors: Mapping and expression editors now have Ora built in, replacing the legacy AI helpers. Ask "what does this field do?" for an explanation, or ask for a change and review it as a diff before it's applied.

What Ora knows about your account

Teach Ora once, and it remembers: Say "remember this," and Ora saves it either in the integration's readme for team knowledge or as a personal rule that follows you across every account you work in. Every saved instruction is a visible, editable file, not a hidden memory store.
Integration App expertise: For managed apps such as Shopify–NetSuite and Amazon–NetSuite, Ora knows what each flow does, which setting governs each behavior, and the documented fixes, grounded in official Celigo docs and your account's configuration.
Custom integration awareness: Ora builds a working profile of each custom integration, including what it does, which pieces are risky to change, and its normal volumes, and uses that profile to answer questions, diagnose errors, and search your account.
Flexible account search: Search by name, rough description, configuration (for example, "all disabled flows"), relationship ("which flows use this connection"), or count ("how many flows per integration"), and get complete, exact answers instead of a top-10 sample.
Contextual awareness: Ora knows what you're working on and recommends prompts to help you build and troubleshoot quickly.

Diagnose and fix errors

Evidence-based diagnosis: Ora pulls the actual failed record and request/response data, checks whether a recent configuration edit lines up with when errors started, and states what's confirmed versus what's a hypothesis, plus the one check that would settle it. Known Integration App errors surface their documented fixes.
Live fact-checking in connected apps: Ora can read the live record in NetSuite, Salesforce, or your database (read-only) through connections you already have to confirm details such as whether a record still exists or is still open.
Bulk error actions by record content: Describe a group of errors by what's inside the failed payload, such as orders with no line items or records where the country isn't US, preview the count, and act on the whole set.
Plain-language retry fixes: Describe a correction, and Ora applies it across one error or thousands, using the platform's own processor so records aren't reshaped or dropped. Every fix stages for your approval.
Record tracing and replay: Trace a record through a run step by step, or replay a failed record through a step's filters and mappings without sending anything to the destination. Ora can also explain why a record was ignored, check whether a run is stuck, read connection debug logs, and inspect lookup cache contents, all from chat.
Anomaly detection over any time window: Ask about anomalies over any date range, for example "any anomalies in my flow executions in the last 15 days?", and Ora checks every day in that window, catching error spikes, volume drops, and flows that quietly stopped running on the day it happened. Previously, Ora could only assess the last 24 hours.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.

How Ora keeps changes safe

Self-testing before saving: Every mapping, template, query, filter, and script Ora writes runs through Celigo's real processors against your sample data, is judged against what you asked for, and is corrected until it's right. If something can't work, Ora says so instead of saving a broken artifact.
Staged approvals with verification: Every change stages as an approval card, validated against the platform before you accept it, individually or all at once. Ora tracks what you approved, resends any card that didn't land, verifies after acceptance that the change persisted, and attributes every action in your audit log.
Builds that finish the job: Flow, API, and Tool builds are grounded in real sample data at every step, verified end to end, and auto-repaired before delivery. You can keep editing a flow while Ora builds it, since it merges your changes rather than overwriting them. Quick edits such as renames, schedules, and enable/disable now stage in seconds.

Find and install from the Marketplace

Search by meaning and template content: Describe your problem in your own words to find the right Marketplace listing, search inside every template for the specific flow or agent tool you need, and check which candidates actually fit your account before you install.
Marketplace browsing and install visibility: Browse and install AI Agent listings directly from chat, check what's new in the Marketplace, and see upfront during a wizard install which external steps are already complete in your account.

Expanded platform coverage

Real-time database listeners: Build change-data-capture exports from plain language for MongoDB change streams, SQL Server CDC, and PostgreSQL logical replication.
MCP servers and AI agents: Build MCP servers complete with tools and prompts, and publish Celigo Storage documents as read-only MCP resources. You can also create Claude-powered AI agents with your own Anthropic key, subscribe agents to governed MCP resources, and diagnose errors on AI agent flow steps.
Integration lifecycle management for APIs and Tools: Snapshot, pull, and revert now cover APIs and Tools in addition to flows, with previews and field-level diffs before anything merges, plus lifecycle-linked clones that stay connected to their source.
Deeper configuration coverage: Author custom settings forms with live dynamic dropdowns pulled from NetSuite, Salesforce, and your saved searches; manage Integration App settings (1.0 and 2.0); use Handlebars on object and array fields in Mapper 2.0 and directly in filter and branch rules; add JavaScript hooks, filters, transforms, and branching on flows, APIs, and Tools; and create Personal Access Tokens directly from chat.

Celigo Ora overview

Error management with Celigo Ora

📁 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

You can now run AI agents and guardrails on Mistral, xAI, Hugging Face, and DeepSeek models — bring your own API key, with usage billed to your provider account.

Why it matters: Model choice used to mean OpenAI, Gemini, or Anthropic. These four run on our new provider catalog framework (2026.8.2), which turns providers into catalog data instead of platform code — that's why all four landed at once with no release, and it means we can add new providers quickly as they're requested.

Who it's for: Builders who want the right model per agent, and IT admins standardizing on a provider their org already governs

What changed:

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

Learn about Celigo AI agents

August 31, 2026:

🛠️ 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.