# How to connect Celigo to OpenClaw (paste one key, 117 tools) > Connect Celigo to OpenClaw with ClawLink: paste your Celigo key once and 117 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/celigo The usual route to Celigo access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Celigo setup: install one ClawHub skill, connect Celigo in the browser, and OpenClaw can call real Celigo actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/celigo ## Setup It takes three steps to connect OpenClaw to Celigo. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Celigo** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect celigo # connect Celigo (browser OAuth) npx -y @useclawlink/cli actions celigo # list available actions npx -y @useclawlink/cli run celigo --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Celigo in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Celigo API key once. Verify the connection by asking OpenClaw: > Use Celigo to assign export error and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Celigo is connected in the dashboard, that agent calls the same 117 Celigo tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Celigo MCP for OpenClaw Looking for a Celigo MCP server for OpenClaw? ClawLink connects Celigo to OpenClaw and exposes 117 Celigo tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Celigo integration](https://claw-link.dev/hermes/celigo) works the same way. ## What the OpenClaw Celigo integration can do 117 Celigo tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 117. ### 30 of 117 Celigo tools for OpenClaw | Tool | What it does | |---|---| | **Assign export error** `celigo_assign_export_error` | Assign an export error to a user in Celigo | | **Clone export** `celigo_clone_export` | Clone a specific export to create a copy | | **Clone flow** `celigo_clone_flow` | Clone a specific flow to create a copy | | **Clone import** `celigo_clone_import` | Clone a specific import to create a copy with remapped connections | | **Evaluate virtual import map** `celigo_evaluate_virtual_import_map` | Evaluate the mapping step of a virtual import and return post-mapped records | | **Execute virtual export** `celigo_execute_virtual_export` | Execute a virtual export using a connection by posting the export model | | **Export virtual paged** `celigo_export_virtual_paged` | Execute a virtual export with paging support for Celigo connections | | **Generate structured file** `celigo_generate_structured_file` | Generate sample EDI data or structured files from input data | | **Get connection** `celigo_get_connection` | Get a specific connection by its ID | | **Get connection audit** `celigo_get_connection_audit` | Retrieve audit logs for a specific connection | | **Get connection debug logs** `celigo_get_connection_debug_logs` | Retrieve debug logs for a connection by its ID | | **Get connection dependencies** `celigo_get_connection_dependencies` | Retrieve all resources using or used by a specific connection | | **Get edi profiles** `celigo_get_edi_profiles` | Retrieve all EDI profiles for the account | | **Get export** `celigo_get_export` | Retrieve a specific export by its ID from Celigo Integrator.io | | **Get export audit** `celigo_get_export_audit` | Retrieve audit logs for a specific export in Celigo | | **Get export errors** `celigo_get_export_errors` | Retrieve all open errors for a specific export within a flow | | **Get file definition** `celigo_get_file_definition` | Retrieve a specific file definition by its ID from Celigo Integrator.io | | **Get file definitions** `celigo_get_file_definitions` | Retrieve all file definitions from Celigo | | **Get flow** `celigo_get_flow` | Retrieve a specific Celigo flow by its ID | | **Get flow audit** `celigo_get_flow_audit` | Retrieve audit logs for a specific flow | | **Get flow dependencies** `celigo_get_flow_dependencies` | Retrieve all resources using or used by a specific flow | | **Get flow descendants** `celigo_get_flow_descendants` | Retrieve all descendant resources of a specific flow | | **Get flow last export datetime** `celigo_get_flow_last_export_datetime` | Retrieve the last export datetime for a specific Celigo flow | | **Get flow latest jobs** `celigo_get_flow_latest_jobs` | Retrieve the latest job executions for a specific flow | | **Get flow template** `celigo_get_flow_template` | Download a Celigo flow as a template | | **Get i client** `celigo_get_i_client` | Get a specific iClient by its ID | | **Get import** `celigo_get_import` | Retrieve a specific import by its ID from the Celigo Integrator API | | **Get import audit** `celigo_get_import_audit` | Retrieve audit logs for a specific import | | **Get import dependencies** `celigo_get_import_dependencies` | Retrieve all resources using or used by a specific import | | **Get integration audit** `celigo_get_integration_audit` | Retrieve audit logs for a specific integration | ## Example prompts **Assign Export Error** > Use Celigo to assign export error and walk me through the result in plain English. **Clone Export** > Use Celigo to clone export and walk me through the result in plain English. **Clone Flow** > Use Celigo to clone flow and walk me through the result in plain English. **Clone Import** > Use Celigo to clone import and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Celigo working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Celigo API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Celigo account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Celigo. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Celigo actions to the runtime in a format your agent can reliably use. | 117 tools for Celigo are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Celigo to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Celigo in the browser, and the 117 tools above work from chat. There is no SDK and no config file, and the Celigo key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Celigo skill but can't call the tools The ClawHub skill teaches OpenClaw about Celigo, but the calls run through the ClawLink plugin and your connected account. Make sure Celigo is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Celigo from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Celigo tools Celigo tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Celigo call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Celigo returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Celigo has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Celigo integration? Yes. ClawLink is the fastest way to connect OpenClaw to Celigo: link your Celigo account once in the browser and OpenClaw can call the Celigo API through 117 ready-made tools — no custom code or token handling. ### How do I add Celigo to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Celigo skill from ClawHub, then you click Connect in the dashboard to authorize Celigo. OpenClaw calls the tools from the next message — no config files, and the Celigo key you paste is stored server-side instead of in your environment. ### How long does it take to connect Celigo to OpenClaw? About two minutes. Sign in, click Connect next to Celigo in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Celigo up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Celigo working from chat. ### OpenClaw installed the Celigo skill but can't call the tools The ClawHub skill teaches OpenClaw about Celigo, but the calls run through the ClawLink plugin and your connected account. Make sure Celigo is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.