Celigo Ora is a natural language interface 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.
Warning
Ora is not available in legacy Sandbox accounts. Learn more about migrating to a multi-environment license.
Prerequisites
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.
Access Ora
To open Ora, select Ask Ora () at the top right of the integrator.io screen, next to Account.
You can drag Ora anywhere on the screen. Hover over the header to minimize Ora so you can keep it out of the way while you work, then bring it back when needed.
Select + in the text area, then select Upload file or choose a file from Celigo File Storage to give Ora additional context. You can also drag and drop a file into the text area, or type @ to add a File Storage file or a file you used recently. To speak your prompt instead of typing it, select +, then select Dictate.
Key concepts
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 capabilities and use cases
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
- Analyzing and troubleshooting 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
Marketplace installs
- Installing Ora-guided templates from the Marketplace
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
- Install an Ora-guided template from the Marketplace
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
For prompt examples and specific use cases, see Practical use cases and prompts using Celigo Ora.
Staged changes
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.
Ora execution modes
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.
Performance tiers
Set your Ora performance tier at Account > Company info. The Priority tier provides faster, more consistent response times but costs more per interaction. The Standard tier provides normal response times, but a lower cost.
Chat history and session behavior
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 are available according to your data retention plan (calculated from each conversation's last used date), and you can continue querying Ora from any of them. You can rename, delete, or clear individual conversations.
Language support
Ora supports multiple languages, including Spanish, French, and Italian.
Feedback
To leave feedback on an Ora response, select Thumbs up or Thumbs down 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.
Ora request processing
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.
Install an Ora-guided template
Ora-guided templates are Marketplace templates that Ora builds and configures for your account, using your answers and the connections you already have. They don't have a self-serve install wizard. Their tiles show an Ora badge.
To install an Ora-guided template, you need the Manage or Admin/Owner role.
- Go to Marketplace
.
- Under By type, select Ora guided. Keep at least one other type selected, such as Templates.
- On the template's tile, select Install. Ora opens and sends a request to install that template.
- Answer Ora's questions. Ora reuses connections already in your account and prompts you to create any required connection that's missing.
- Review and approve the changes Ora stages.
Ora installs the template into your account, configured from your answers. After installation, the integration appears on your Home page as a new tile.
Note: To install an Ora-guided template, select Install on its tile, not on the preview page.
Ora guided narrows your other By type selections. For more about Marketplace filters, see Jump-start integrations with templates and apps.
Best practices and tips
Before you begin using Celigo Ora, check these best practices and tips:
Write clear prompts
- 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.
Scope changes safely
- 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.
Safely modify production flows
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.
- Go to the cloned integration's Admin, then turn on 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.
Error handling
- Copy and paste errors verbatim — Include the full error message, any error code, and the step name. Small differences in error text often matter.
Context and credentials
- Don't paste secrets — Enter tokens and passwords directly in the Celigo UI. Once you have done that, tell Ora "it's set in the UI" and Ora can proceed.
- Add a file for additional context — Select +, then select Upload file or choose a file from Celigo File Storage. You can also drag and drop a file into the text area, or type @ to add a File Storage file or a recently used file.
- Update the page context — Each conversation uses the page that was open when you started it as context. If you move to another page and want Ora to use that page instead, type @current_page in your prompt.
- Start a new conversation when the context changes — If a conversation runs long or you move on to different work, open a new conversation in a new tab.
Limitations
Ora 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.
Usage credits
Ora is available for all users. If you run out of credits, give it a few minutes to auto-refresh, and you can pick up right where you left off.
Access, agency, and security
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.
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 Ora 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.