> For the complete documentation index, see [llms.txt](https://developer.celigo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.celigo.com/cli/commands.md).

# Command reference

Every `celigo` command, one page each. Most resource commands share the same shape, so once you know one you know them all.

## The common shape

| Subcommand             | What it does                                                                                                                                                |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `list`                 | List the resources. Add `--integration <id>` where supported to scope to one integration.                                                                   |
| `get <id>`             | Fetch one resource by ID.                                                                                                                                   |
| `create`               | Create from a JSON body. Read it from a file with `-f, --file <path>` (recommended) or pipe it on stdin.                                                    |
| `update <id>`          | Full replace from a JSON body (`--file` or stdin). Pass `--force` to submit a body that still holds masked `***` credential values.                         |
| `set <id> key=value …` | Targeted field edit. Whitelisted fields apply via an atomic `PATCH`; others round-trip GET, modify, PUT. Load a field from a file with `key=file://<path>`. |
| `delete <id>`          | Delete by ID (`-y` to skip the prompt).                                                                                                                     |
| `dependencies <id>`    | List what references the resource, so you know if it is safe to delete.                                                                                     |
| `audit <id>`           | Show the change history for one resource.                                                                                                                   |

Individual commands add their own subcommands on top of this (for example `flows run`, `flows test-run`, `connections ping`, `jobs diagnostics`). Every command accepts the [global flags](/cli/getting-started/global-flags.md).

> File-based input (`-f, --file <path>` on `create` / `update`, and `key=file://<path>` on `set`) shipped in celigo-cli 2026.6.1. It avoids shell escaping and works the same in bash and PowerShell.

## All commands

| Command                                                     | Purpose                                                                                     |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| [account](/cli/commands/account.md)                         | Account-wide operations: snapshot, search, dependencies, lint, stats.                       |
| [ai-agents](/cli/commands/ai-agents.md)                     | Manage AI agents (LLM-powered import steps).                                                |
| [apis](/cli/commands/apis.md)                               | Manage API endpoints (builder and script modes).                                            |
| [async-helpers](/cli/commands/async-helpers.md)             | Manage async helpers (polling configs for long-running API operations).                     |
| [audit](/cli/commands/audit.md)                             | View audit logs.                                                                            |
| [config](/cli/commands/config.md)                           | Manage CLI configuration.                                                                   |
| [connections](/cli/commands/connections.md)                 | Manage connections (credentials and configuration for external systems).                    |
| [connectors](/cli/commands/connectors.md)                   | Manage connectors (installable integration applications).                                   |
| [edi-profiles](/cli/commands/edi-profiles.md)               | Manage EDI document profiles for trading partners.                                          |
| [edi-transactions](/cli/commands/edi-transactions.md)       | Query EDI transaction logs from the B2B Manager dashboard.                                  |
| [environments](/cli/commands/environments.md)               | Manage sandbox and staging environments.                                                    |
| [event-reports](/cli/commands/event-reports.md)             | Manage event reports.                                                                       |
| [exports](/cli/commands/exports.md)                         | Manage exports (data sources that read from external systems).                              |
| [file-definitions](/cli/commands/file-definitions.md)       | Manage file format definitions (CSV, EDI, fixed-width, etc.).                               |
| [flows](/cli/commands/flows.md)                             | Manage flows (data pipelines connecting exports to imports).                                |
| [guardrails](/cli/commands/guardrails.md)                   | Manage guardrails (PII detection, content moderation, AI safety checks).                    |
| [http-connectors](/cli/commands/http-connectors.md)         | Browse and manage HTTP connector definitions.                                               |
| [iclients](/cli/commands/iclients.md)                       | Manage OAuth2 iClients (app registrations for OAuth flows).                                 |
| [imports](/cli/commands/imports.md)                         | Manage imports (data destinations that write to external systems).                          |
| [integrations](/cli/commands/integrations.md)               | Manage integrations (containers for flows, connections, and resources).                     |
| [jobs](/cli/commands/jobs.md)                               | Manage flow execution jobs (status, files, diagnostics, cancellation).                      |
| [lookup-caches](/cli/commands/lookup-caches.md)             | Manage lookup caches (in-memory key-value stores for enrichment and deduplication).         |
| [mcp-oauth-providers](/cli/commands/mcp-oauth-providers.md) | Manage MCP OAuth providers for MCP servers.                                                 |
| [mcp-servers](/cli/commands/mcp-servers.md)                 | Manage MCP servers that expose tools and APIs as MCP endpoints.                             |
| [metadata](/cli/commands/metadata.md)                       | Query metadata via a live connection (NetSuite, Salesforce, RDBMS).                         |
| [notifications](/cli/commands/notifications.md)             | Manage notification subscriptions (integrations, flows, connections).                       |
| [on-premise-agents](/cli/commands/on-premise-agents.md)     | Manage on-premise agents (OPA).                                                             |
| [profile](/cli/commands/profile.md)                         | Manage named config profiles (multiple accounts and environments).                          |
| [recycle-bin](/cli/commands/recycle-bin.md)                 | Browse and restore soft-deleted resources.                                                  |
| [scripts](/cli/commands/scripts.md)                         | Manage scripts (JavaScript hooks: preSavePage, preMap, postMap, postSubmit).                |
| [stacks](/cli/commands/stacks.md)                           | Manage stacks (server and Lambda runtimes for custom code).                                 |
| [state](/cli/commands/state.md)                             | Manage state key-value stores.                                                              |
| [subscriptions](/cli/commands/subscriptions.md)             | View subscription and usage information.                                                    |
| [sync-jobs](/cli/commands/sync-jobs.md)                     | Inspect and cancel sync jobs (the executions produced by `syncs run`).                      |
| [syncs](/cli/commands/syncs.md)                             | Run syncs, review history, and discover supported source and destination apps.              |
| [tags](/cli/commands/tags.md)                               | Manage tags for organizing resources.                                                       |
| [templates](/cli/commands/templates.md)                     | Browse, preview, manage, and install integration templates.                                 |
| [tools](/cli/commands/tools.md)                             | Manage tools (reusable building blocks callable from flows, APIs, agents, and MCP servers). |
| [tp-connectors](/cli/commands/tp-connectors.md)             | Browse trading partner connector definitions (read-only).                                   |
| [users](/cli/commands/users.md)                             | Manage account users and access levels.                                                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.celigo.com/cli/commands.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.