# 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.

- Page: https://www.agent200.com/connectors/celigo/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `celigo`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## Celigo tools

- **List integrations** (`celigo_list_integrations`, read): List the integrations in the user's account.
- **List flows** (`celigo_list_flows`, read): List the flows and whether they are enabled.
- **Run a flow** (`celigo_run_flow`, write): Run a flow on demand.
- **List jobs** (`celigo_list_jobs`, read): List recent jobs with their status and error counts.

## Limits you can set

**Turn single tools on or off.** Let the agent read flows and job results, and switch off `celigo_run_flow` so 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "Did the NetSuite order sync run without errors today"
- "Run the customer import flow now"
- "Which flows are turned off"

## Guides: Celigo with your AI framework

- [Celigo + Claude](https://www.agent200.com/connectors/celigo/framework/claude.md): Set up Celigo for Claude with Agent200, then check which tools are available to your agent.
- [Celigo + ChatGPT](https://www.agent200.com/connectors/celigo/framework/chatgpt.md): Set up Celigo for ChatGPT with Agent200, then check which tools are available to your agent.
- [Celigo + Claude Code](https://www.agent200.com/connectors/celigo/framework/claude-code.md): Set up Celigo for Claude Code with Agent200, then check which tools are available to your agent.
- [Celigo + Muse](https://www.agent200.com/connectors/celigo/framework/muse.md): Set up Celigo for Muse with Agent200, then check which tools are available to your agent.
- [Celigo + Grok Bot](https://www.agent200.com/connectors/celigo/framework/grok-bot.md): Set up Celigo for Grok Bot with Agent200, then check which tools are available to your agent.
- [Celigo + OpenAI Dots](https://www.agent200.com/connectors/celigo/framework/openai-dots.md): Set up Celigo for OpenAI Dots with Agent200, then check which tools are available to your agent.
- [Celigo + Claude Duet](https://www.agent200.com/connectors/celigo/framework/claude-duet.md): Set up Celigo for Claude Duet with Agent200, then check which tools are available to your agent.
- [Celigo + Hermes Agent](https://www.agent200.com/connectors/celigo/framework/hermes-agent.md): Set up Celigo for Hermes Agent with Agent200, then check which tools are available to your agent.
- [Celigo + OpenClaw](https://www.agent200.com/connectors/celigo/framework/openclaw.md): Set up Celigo for OpenClaw with Agent200, then check which tools are available to your agent.

## FAQ

### 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.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
