Developer tools
Celigo for AI agents.
Managed auth, ready-made tools.
List integrations and flows, run flows and check job results in Celigo on behalf of each of your users.
About Celigo
With the Celigo connector, your agent works in each user’s own Celigo integrator.io account. It can list integrations and flows, run a flow on demand and check how recent jobs went, using only the tools your project allows.
Celigo is an integration platform for connecting business apps and automating data flows between them.
Tools
What your agent can do in Celigo.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Celigo connection.
-
List integrations
Readceligo_list_integrationsList the integrations in the user's account.
-
List flows
Readceligo_list_flowsList the flows and whether they are enabled.
-
Run a flow
Writeceligo_run_flowRun a flow on demand.
-
List jobs
Readceligo_list_jobsList recent jobs with their status and error counts.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Celigo, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read flows and job results, and switch off
celigo_run_flowso it can never start one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example jobs but not flows. A call outside them is refused.
Get started
Connect Celigo
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Celigo
Each end user authorizes their own Celigo account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Celigo account, once. const connection = await agent200 .user("user_123") .connect("celigo"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Celigo tools
Name the user, the model and the tools. The model decides which Celigo tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Did the NetSuite order sync run without errors today", tools: ["celigo"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own Celigo account. Each connection is their own.
-
What access is requested
The connection acts with that user's access in integrator.io, such as reading flows, reading jobs or running flows. Users can revoke the connection later from their Celigo account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Celigo connector and how to use it.
Connector: Celigo, through Agent200. In code: "celigo". What it does: List integrations and flows, run flows and check job results in Celigo on behalf of each of your users. Page: https://www.agent200.com/connectors/celigo/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Celigo's own page, through the authorization link Agent200 returns. Never ask a user for a Celigo password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: celigo_list_integrations, celigo_list_flows, celigo_list_jobs. Write tools: celigo_run_flow. Name "celigo" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/celigo/framework/claude/ https://www.agent200.com/connectors/celigo/framework/chatgpt/ https://www.agent200.com/connectors/celigo/framework/claude-code/ https://www.agent200.com/connectors/celigo/framework/muse/ https://www.agent200.com/connectors/celigo/framework/grok-bot/ https://www.agent200.com/connectors/celigo/framework/openai-dots/ https://www.agent200.com/connectors/celigo/framework/claude-duet/ https://www.agent200.com/connectors/celigo/framework/hermes-agent/ https://www.agent200.com/connectors/celigo/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/celigo.md
Guides
Use Celigo with the AI you build on.
Step-by-step setup for Celigo with a specific model, assistant or agent framework.
-
Celigo + Claude
How to connect Celigo to Claude
-
Celigo + ChatGPT
How to connect Celigo to ChatGPT
-
Celigo + Claude Code
How to connect Celigo to Claude Code
-
Celigo + Muse
How to connect Celigo to Muse
-
Celigo + Grok Bot
How to connect Celigo to Grok Bot
-
Celigo + OpenAI Dots
How to connect Celigo to OpenAI Dots
-
Celigo + Claude Duet
How to connect Celigo to Claude Duet
-
Celigo + Hermes Agent
How to connect Celigo to Hermes Agent
-
Celigo + OpenClaw
How to connect Celigo to OpenClaw
FAQ
Celigo and Agent200, answered.
Who handles the Celigo OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Celigo.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Celigo connection, never another user's. It cannot reach anything the user or Celigo has not authorized.
Can I limit what my agent can do in Celigo?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.