Celigo
Integration platform as a service (iPaaS) for connecting applications and automating workflows
Verdict
Common use cases
- Assign sync errors to engineers from chat
- Clone production flows to staging environment
- Check integration job status during incidents
- Create new API connections without dashboard
- Duplicate export configs for new data sources
Integration
- Vendor
- Celigo
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 50
- Composio slug
celigo
Tools
- Assign Export Error
Tool to assign an export error to a user in Celigo. Use when you need to assign responsibility for fixing or reviewing integration errors to a specific team member.
- Clone Export
Tool to clone a specific export to create a copy. Use when you need to duplicate an existing export configuration with new or same connection mappings.
- Clone Flow
Tool to clone a specific flow to create a copy. Use when you need to duplicate an existing flow configuration to a different integration.
- Clone Import
Tool to clone a specific import to create a copy with remapped connections. Use when you need to duplicate an existing import configuration with different connection IDs.
- Clone Integration
Tool to clone a specific integration to create a copy. Use when you need to duplicate an existing integration and all its flows.
- Create Connection
Tool to create a new connection in Celigo to store credentials and application access information. Use when you need to set up a new API connection, configure authentication, or establish integration endpoints. Supports multiple connection
- Create Export
Tool to create a new export in Celigo for extracting data from an application. Use when you need to set up a new data export configuration, such as webhook exports, delta exports, or test exports.
- Create File Definition
Tool to create a file definition in Celigo for defining data file structure and format. Use when you need to specify how data files should be structured for import or export operations. Supports both fixed-width and delimited (CSV-style) fi
- Create Flow
Tool to create a new flow in Celigo that composes export and import components together. Use when you need to establish a data integration pipeline between systems. A flow connects a source (export) to a destination (import) and can be sche
- Create iClient
Tool to create a new iClient for SmartConnector authentication in Celigo. Use when you need to set up authentication credentials for connecting to external APIs. iClients store provider-specific authentication data required for API integrat
- Create Import
Tool to create a new import for inserting data into an application. Use when you need to set up a data import configuration with HTTP endpoint details.
- Create Integration
Tool to create a new integration in Celigo to group flows together. Use when you need to organize related flows under a single integration container for better management and structure.
- Create Integration Revision
Tool to create a snapshot revision of a specific integration. Use when you need to capture the current state of an integration for version control or backup purposes.
- Create Script
Tool to create a new custom JavaScript script in Celigo for data transformation operations. Use when you need to add a script for custom data processing, validation, or transformation logic.
- Create Tag
Tool to create a new tag in Celigo for organizing and categorizing resources. Use when you need to create a tag that can be applied to integrations, flows, or other Celigo resources.
- Create User
Tool to create a new user in your Celigo integrator.io account by sending an invitation. Use when you need to grant a new user access to your Celigo account with specific permissions.
- Delete All Resource Statedestructive
Tool to delete all state keys and values stored under a specific resource. Use when you need to clear all state data for a resource. This is a destructive operation - be careful!
- Delete All Statedestructive
Tool to delete all global state keys and values in Celigo. Use when you need to clear all stored state data. WARNING: This operation is destructive and irreversible - it removes ALL global state keys and values from the account.
- Delete Connectiondestructive
Tool to delete a specific connection in Celigo. Use when you need to permanently remove a connection from your integration. Returns success status on completion.
- Delete Exportdestructive
Tool to delete a specific export from Celigo. Use when you need to permanently remove an export by its ID. Returns a success confirmation.
- Delete Flowdestructive
Tool to delete a specific flow from Celigo. Use when you need to permanently remove a flow. This operation is destructive and cannot be undone.
- Delete iClientdestructive
Tool to delete a specific iClient from Celigo. Use when you need to permanently remove an iClient by its ID. Returns a success confirmation.
- Delete Importdestructive
Tool to delete a specific import from Celigo integrator.io. Use when you need to remove an import configuration. This operation is destructive and cannot be undone.
- Delete Integrationdestructive
Tool to delete a specific integration from Celigo integrator.io. Use when you need to permanently remove an integration. This operation is destructive and cannot be undone.
- Delete Resolved Errorsdestructive
Tool to delete resolved errors for a specific export in Celigo. Use when you need to clear resolved errors from an export's error log.
- Delete Resource State Valuedestructive
Tool to delete the resource-specific key and value from state. Use when you need to remove state data for a specific resource like imports, exports, flows, or connections.
- Delete Scriptdestructive
Tool to delete a specific script from Celigo. Use when you need to permanently remove a script configuration. This operation is destructive and cannot be undone.
- Delete State Valuedestructive
Tool to delete the specified state key and its value. Use when you need to remove state data from the Celigo Integrator platform. This operation is destructive and cannot be undone.
- Delete Tagdestructive
Tool to delete a specific tag from Celigo integrator.io. Use when you need to permanently remove a tag. This operation is destructive and cannot be undone.
- Delete Userdestructive
Tool to delete a specific user from your Celigo account. Use when you need to remove a user (account share) from the account.
- Evaluate Virtual Import Map
Evaluate the mapping step of a virtual import and return post-mapped records. Use when you need to test field mapping transformations without executing the full import process.
- Execute Virtual Export
Execute a virtual export using a connection by posting the export model. Use when you need to trigger an export operation for a specific connection with custom configuration (HTTP, NetSuite, or Salesforce).
- Execute Virtual Import
Tool to execute a virtual import by posting import configuration and data to a connection. Use when you need to send data to an external API through a Celigo connection with field mapping transformations.
- Generate Structured File
Tool to generate sample EDI data or structured files from input data. Use when you need to convert JSON data into a delimited or fixed-width file format based on defined rules.
- Get Connection Audit Logs
Tool to retrieve audit logs for a specific connection. Use when you need to track changes, view history, or investigate modifications made to a connection.
- Get Connection by ID
Tool to get a specific connection by its ID. Use when you need to retrieve connection details including configuration, authentication settings, and type information.
- Get Connection Debug Logs
Tool to retrieve debug logs for a connection by its ID. Use optional resource_id parameter to filter logs by a specific import or export.
- Get Connection Dependencies
Tool to retrieve all resources using or used by a specific connection. Use when you need to understand the dependencies of a Celigo connection, including imports, flows, and integrations that rely on it.
- Get EDI Profiles
Tool to retrieve all EDI profiles for the account. Use when you need to list Electronic Data Interchange (EDI) and B2B configurations. Returns empty array if no profiles are configured (HTTP 204).
- Get Export
Tool to retrieve a specific export by its ID from Celigo Integrator.io. Use when you need to fetch export configuration details including lifecycle hooks and provider settings.
- Get Export Audit Log
Tool to retrieve audit logs for a specific export in Celigo. Use when you need to track changes, modifications, or events related to an export resource. Returns a detailed history of field changes, events, timestamps, and user information.
- Get Export Errors
Tool to retrieve all open errors for a specific export within a flow. Use when you need to monitor export health, debug issues, or identify failed operations that require attention.
- Get File Definition
Tool to retrieve a specific file definition by its ID from Celigo Integrator.io. Use when you need to fetch file definition details including name, type, and configuration.
- Get File Definitions
Tool to retrieve all file definitions from Celigo. Use when you need to list file format definitions used for data transformation in integrations.
- Get Flow Audit Logs
Tool to retrieve audit logs for a specific flow. Use when you need to track changes, events, and modifications made to a flow resource over time. Returns detailed history including field changes, timestamps, and user information.
- Get Flow by ID
Tool to retrieve a specific Celigo flow by its ID. Use when you need to fetch flow details, configuration, or metadata. Returns complete flow information including name, status, scheduling, and orchestration settings.
- Get Flow Dependencies
Tool to retrieve all resources using or used by a specific flow. Use when you need to understand the dependency graph of a Celigo flow, including imports, exports, connections, and other flows or integrations that reference it.
- Get Flow Descendants
Tool to retrieve all descendant resources of a specific flow. Use when you need to identify imports and exports that are children of a flow.
- Get Flow Last Export Datetime
Tool to retrieve the last export datetime for a specific Celigo flow. Use when you need to check when a flow last exported data. Returns the timestamp or null if no export has occurred yet.
- Virtual Export with Paging
Tool to execute a virtual export with paging support for Celigo connections. Use when you need to retrieve data from external systems in paginated chunks. For subsequent pages, include the pagedExportState from the previous response.
Setup
Setup guide
- 11. In Switchy, open Settings → Integrations → Developer Tools and click Connect next to Celigo. 2. Log into your Celigo account, navigate to Settings → API Tokens, and generate a new token with 'Integration Management' and 'Connection Management' scopes enabled. 3. Copy the token and paste it into the Switchy connection dialog, then click Authorize. 4. Switchy will verify the token and confirm the connection. 5. Open any Space, type '@Celigo list integrations' and send — if you see a list of your active integrations, the connection works. 6. To assign an export error, use '@Celigo assign export error [export_id] to [user_email]' in a message. 7. For cloning a flow, write '@Celigo clone flow [flow_id] to integration [integration_id]' and the MCP handles the rest.
What teammates see: by default, memories from Celigo are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Failed Integrations
@Celigo show me all integrations that have errors in the last 24 hours, grouped by integration nameOpen in a Space →
Clone Flow to Staging
@Celigo clone flow [flow_id] to the staging integration and confirm the new flow ID when doneOpen in a Space →
Assign Export Error
@Celigo assign export error [export_id] to [engineer_email] and add a note that it's blocking the nightly syncOpen in a Space →
Create Webhook Export
@Celigo create a webhook export for the Sales integration that sends new orders to https://example.com/ordersOpen in a Space →
Check Connection Status
@Celigo check the status of the Salesforce connection and tell me if it needs re-authenticationOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@celigo show me all unassigned export errors from the last 48 hours and group them by integration name
Based on the Celigo API response, here's an illustrative summary: 23 unassigned export errors found across 4 integrations in the last 48 hours. **Shopify-to-NetSuite** (12 errors): mostly 'customer record not found' failures. **Salesforce-to-Slack** (7 errors): webhook timeout issues. **HubSpot-to-Mailchimp** (3 errors): duplicate email conflicts. **Stripe-to-QuickBooks** (1 error): invalid tax code mapping. The API returns error IDs, timestamps, and stack traces for each — you can assign these to teammates using the assign-export-error tool.
This example showcases Celigo's error-monitoring strength: surfacing integration failures so teams can triage quickly. Requires API key with read access to flows and errors. Note that error details depend on your account's integration history — a fresh Celigo account may return zero errors.
@celigo create a new webhook export for our Stripe connection that sends payment.succeeded events to our internal analytics endpoint at https://analytics.example.com/webhooks/stripe
Illustrative confirmation: Export created successfully with ID `exp_5a3b9c`. Configuration summary: **Source**: Stripe connection (conn_stripe_prod). **Trigger**: Webhook listening for `payment.succeeded` events. **Destination**: HTTPS POST to `https://analytics.example.com/webhooks/stripe`. **Mapping**: Default Stripe event payload forwarded as-is. The export is now active and will forward matching events in real-time. You can clone this export or adjust field mappings via the Celigo dashboard.
This write-action example demonstrates how Celigo automates data flow between apps. Requires API key with write permissions and a valid connection ID for Stripe. Side-effect: the webhook starts forwarding events immediately — test your endpoint before enabling in production to avoid data loss or duplicate processing.
@celigo review all flows in the 'Order Sync' integration and draft a runbook explaining what each flow does, including error-handling steps
Illustrative synthesis based on Celigo metadata: The **Order Sync** integration contains 5 flows. **Flow 1 (Shopify → NetSuite Orders)**: Exports new orders every 15 minutes; on error, retries 3x then assigns to ops@example.com. **Flow 2 (NetSuite → Shopify Fulfillments)**: Imports fulfillment status; uses delta export to avoid duplicates. **Flow 3 (Inventory Adjustment)**: Runs nightly to sync stock levels; logs discrepancies to Slack. **Flow 4 (Refund Processor)**: Webhook-triggered; creates credit memos in NetSuite. **Flow 5 (Error Reconciliation)**: Weekly batch job that flags unresolved errors. Recommended runbook sections: flow triggers, retry logic, escalation paths, and connection health checks.
This synthesis example pairs Celigo's metadata (flow names, schedules, error configs) with AI reasoning to produce documentation. Useful for onboarding or audit prep. Accuracy depends on descriptive flow names in your Celigo account — generic names like 'Flow 1' yield less useful summaries. No side-effects; read-only operation.
Use-case deep-dives
When Celigo MCP makes sense for client onboarding teams
A 6-person agency team onboards 3-4 SaaS clients per month, each needing custom integrations between their CRM, billing, and support tools. The Celigo MCP wins here because the clone tools (Clone Flow, Clone Integration, Clone Export) let the team templatize proven integration patterns and spin up new client instances in minutes instead of days. The 50-tool scope covers the full lifecycle—create connections for new client credentials, clone the base flow, remap imports to the client's data schema, and assign export errors to the account manager when something breaks. If your agency only onboards one client per quarter, the setup overhead outweighs the benefit. But at 3+ clients per month, this MCP turns integration delivery into a repeatable playbook.
Why this MCP handles one-time data moves poorly
A 12-person ops team just acquired a competitor and needs to migrate 80k customer records from the acquired company's Salesforce into their NetSuite instance. The Celigo MCP is borderline here. The Create Import and Create File Definition tools can scaffold the migration job, and the error assignment tools help triage failed records. But this is a one-time, high-stakes move—you're not iterating on integration patterns, you're babysitting a single bulk transfer. The MCP's real value is in *repeatable* integration workflows, not one-off migrations. If your team runs quarterly data syncs or monthly reconciliation jobs, the MCP pays off. For a single migration, you're better off using Celigo's UI directly and keeping the MCP for ongoing integration maintenance afterward.
When this MCP speeds up integration incident response
A 5-person customer success team supports 20 enterprise clients, each running 4-8 live integrations through Celigo. When a client reports missing invoices or duplicate orders, the team needs to diagnose which integration failed and route the fix to the right engineer. The Celigo MCP's Assign Export Error tool is the hero here—the support rep can query recent errors, assign them to the backend engineer who owns that flow, and add context notes without leaving the Switchy workspace. The Create Connection and Clone Flow tools also matter when a client needs a net-new integration spun up mid-contract. If your team only troubleshoots integrations once a month, the MCP is overkill. But at 3+ incidents per week, this MCP turns integration support from a context-switching nightmare into a triaged queue.
Frequently asked
What does the Celigo MCP let me do in Switchy?
It lets you manage Celigo integration flows, connections, and error assignments without leaving Switchy. You can clone exports and imports, create new connections with stored credentials, assign export errors to teammates, and define file structures for data operations. Useful when you're debugging integration issues or setting up new data pipelines and want AI to handle the API calls.
Do I need admin access to connect Celigo?
You need a Celigo API key with permissions to read and write integrations, connections, and flows. Celigo uses API key auth, not OAuth, so whoever connects it must have access to generate keys in the Celigo account settings. If your team restricts API key creation to admins, you'll need one of them to set it up.
Can the MCP trigger or run Celigo flows directly?
No. The MCP manages flow configuration—cloning flows, creating exports and imports, defining file structures—but it doesn't execute or trigger flows. If you need to run a flow, you still do that in Celigo's UI or via their separate execution API. This MCP is for setup and error triage, not runtime orchestration.
Why use this instead of just logging into Celigo?
Speed when you're already in Switchy working on integration issues. Instead of context-switching to Celigo's UI to assign an error, clone a flow, or check connection settings, you ask the AI and it calls the API. Most valuable during incident response or when onboarding new flows—less valuable for one-off configuration changes you'd rather click through.
Who on the team should connect the Celigo MCP?
Whoever owns your integration ops or has API key access in Celigo. Typically a backend engineer, integration specialist, or ops lead. Once connected in Switchy, anyone in the workspace can use it to assign errors or inspect flows, but the API key's permissions control what actions actually succeed. One connection per workspace is enough.