Celigo Ora is an AI assistant built into the Celigo platform that helps you create and update integration resources, investigate and resolve errors, and monitor your account through a conversational interface. Ora draws on context from your Celigo account, proposes changes as reviewable drafts, and applies them only after you explicitly approve.
Ora is currently in BETA mode and can make mistakes. Always review changes before approving them.
Warning
Ora is not available in legacy Sandbox accounts. Learn more about migrating to a multi-environment license.
Ora's available actions depend on your Celigo account role and permissions:
-
Monitor: Ora focuses on visibility and troubleshooting.
-
Manage: Ora can help you make configuration changes and run components you are authorized to run.
-
Admin/Owner: Ora can assist with broader administrative actions your account allows.
Ora does not have a separate permission set. It operates within whatever roles and scopes have been assigned to you at the account level and per integration.
To open Ora, select the Ora sparkle () at the bottom right of the integrator.io screen.
Ora can be dragged anywhere on the screen. Hover over the header to see the option to minimize Ora so you can keep it out of the way while you work and bring it back when needed.
The following sections define key terms you'll encounter when working with Ora, including how changes are staged, how Ora interprets your prompts, and what its domain capabilities cover.
Ora uses specialized domain capabilities, organized by resource type, to locate resources, stage reviewable changes, and retrieve audit history and dependencies. Ora can help you accomplish many common tasks in Celigo, including:
Resource management
-
Creating, updating, and organizing flows, exports, imports, connections, scripts/hooks, APIs, and others
Error management
-
Retrying, resolving, tagging, and assigning errors
Operational monitoring
-
Reviewing recent changes and audit history
-
Finding where a specific field, URL, or value is hardcoded across configurations
-
Improving mappings, filters, handlebars templates, and JavaScript used in hooks and transformations
You can upload a file by clicking the Add file (+) button or by dragging and dropping it into the text area to give Ora additional context.
For prompt examples and specific use cases, see Practical use cases and prompts using Celigo Ora.
When Ora makes a change, it stages it as a draft in Celigo for your review. Nothing is applied until you explicitly approve it. You can ask Ora, "Show me exactly what will change" at any point to get a summary before approving.
By default, Ora assumes you want it to execute an action; for example, create, update, or run a flow. If you say "how would you…" or "don't make changes yet," Ora switches to a planning approach and explains what it will do without making any changes.
Each Ora chat session is independent. When you start a new chat, Ora has no memory of previous sessions.
In long sessions, Ora uses summarization and compaction (a process that condenses earlier conversation context to free up space) to stay within context limits. Older details may be compressed rather than retained verbatim, while recent details remain strongest. Ora can re-fetch live account and resource data through its tools, so it does not rely solely on compressed chat history. If you are working in a long session, restate any critical details or ask Ora to re-inspect a resource before making changes.
Select History () in Ora's header to view your conversation history. All conversations from the last 30 days are available, and you can continue querying Ora from any of them. You can rename, delete, or clear individual conversations.
To leave feedback on an Ora response, select the Thumbs up or Thumbs down icon that appears below each response in the Ora panel. In the explanation box, include:
-
What you were trying to do
-
What went well or didn't
-
The relevant resource or step name
-
Any error text so the team can reproduce the issue
If you are reporting a suggestion, describe the desired behavior and how it would improve your workflow.
Use Ora when you want to:
-
Build or modify a flow without navigating through multiple configuration screens
-
Troubleshoot a flow failure by analyzing an error message and getting fix recommendations
-
Find where a specific field, URL, or value is hardcoded across your configurations
-
Review recent changes and audit history for a flow or integration
-
Improve mappings, filters, Handlebars templates, or JavaScript used in hooks and transformations
-
Retry, resolve, or triage errors across your account
Ora is not the right tool when:
-
The outcome depends on business rules it doesn't have context for; for example, which system is the source of truth, or how to handle duplicate records
-
The underlying issue involves invalid credentials, unreachable endpoints, or data constraints outside Celigo's control
You tell Ora the outcome you want, and it uses context from your Celigo account to translate your intent into concrete, reviewable actions.
When you submit a prompt, Ora uses its domain capabilities to locate the relevant resources, propose changes as staged drafts, and summarize the impact before you approve anything.
For general how-to questions, Ora can consult up-to-date documentation. For troubleshooting, Ora analyzes error payloads and execution context to recommend fixes.
If Ora needs more information to proceed, it will ask a clarifying question in the chat rather than making an assumption. This might include questions about which system is the source of truth or whether you want to upsert vs. update.
Before you begin using Celigo Ora, check these best practices and tips:
-
State your intent upfront. Say whether you want a plan or execution. "Don't make changes yet" triggers a planning approach; otherwise, Ora assumes execution and stages changes for approval.
-
Be specific and detailed. Include what you want Ora to do, how you want it executed, and in what order.
-
Be explicit about the target. Include the exact resource name and, when possible, the '_id' (flow, import, connection, integration). This prevents back-and-forth about which resource you mean.
-
When you say "this," include context. If you are not on the resource page, "this flow/connection" can be ambiguous. Add the name or '_id'.
-
Provide environment details up front. For anything involving credentials or endpoints, specify prod vs. sandbox, region (NA/EU), and which tenant or subdomain.
-
State the outcome and the guardrails. Example: "Update this flow to do X, but don't change schedules, mappings, or step order." Clear constraints help avoid unintended edits.
-
Give the time window and scope. For questions like "recent changes" or "errors," specify "last 24 hours / 7 days / 60 days" and whether you mean one flow, one integration, or the whole account.
-
Expect drafts for anything that modifies configurations. Ask "Show me exactly what will change" if you want a summary before approving.
-
Break large changes into milestones. For complex, multi-step requests, ask Ora to proceed step-by-step with checkpoints so you can validate each stage before moving forward.
If Ora modifies a production flow and the result isn't what you intended, there is no built-in way to revert the changes. Use the following approach to test changes safely before applying them to production:
-
Clone the integration you want to modify.
-
On the cloned integration's Admin tab, enable Allow Ora to apply changes automatically.
-
Use Ora to make and test changes on the clone.
-
Use Integration Lifecycle Management (ILM) to merge approved changes back to the original integration.
-
Copy and paste errors verbatim. Include the full error message, any error code, and the step name. Small differences in error text often matter.
Ora is currently in BETA mode and can make mistakes. Always review changes before approving them.
-
Missing business rules: Ora cannot infer domain-specific decisions you haven't provided, such as which system is the source of truth, whether to create, update, or upsert, or how to handle duplicate records. When the outcome depends on a choice that materially changes behavior, Ora will ask for clarification rather than assume.
-
Unresolvable underlying issues: Ora can help diagnose and explain failures, but cannot guarantee a fix when the root cause involves invalid connections, unreachable endpoints, or data constraints outside Celigo's control.
-
No snapshot or rollback for configuration changes: Ora does not take a snapshot before modifying a resource, and there is no built-in rollback. Review all staged changes carefully before approving, and consider using the workaround described in the Safely modify production flows section when working with critical integrations.
-
Not available in legacy sandbox accounts: Ora is not available in legacy sandbox accounts. To use Ora in a non-production environment, see Migrate your sandbox environment to a non-production environment.
Ora does not learn from your conversations, and Celigo's data protection policies apply to Ora. All activity is fully contained within your account, and Ora can only perform actions that you are authorized to perform.
Ora operates within your Celigo account permissions — whatever roles and scopes have been assigned to you at the account level and per integration.
Any changes Ora executes are recorded through Celigo's audit logs, the same way changes are recorded when you do them directly in the UI. Audit logs capture who made the change, when it happened, what was changed (including old/new values), and the source of the change (for example, UI vs API vs System/Stack, depending on the action). Sensitive data (like a password/token) isn't exposed in the audit trail, and you can filter and export audit log data when you need to review history or support an internal change-control process.