celigo

Build automations and assets, triage errors, execute admin tasks, and more, all through the Celigo Platform MCP connector's 30+ tools.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • List Exports: Data source steps (page generators) that fetch records from external systems. Each export is tied to a connection and defines what data to pull. adaptorType (e.g. HTTPExport, NetSuiteExp
  • Upsert Export: Create or update Data source steps (page generators) that fetch records from external systems. Each export is tied to a connection and defines what data to pull. adaptorType (e.g. HTTPE
  • List Imports: Data destination steps (page processors) that write records to external systems. Each import is tied to a connection and defines how to push data. adaptorType (e.g. HTTPImport, NetSuiteD

What data it sees

Do you need an account

No: the server works without sign-in

Build automations and assets, triage errors, execute admin tasks, and more, all through the Celigo Platform MCP connector's 30+ tools. This brings the full power of Celigo directly into your LLM, so you can tap into the entire platform right from where you're already working, using natural language. A personal access token means you inherit the exact same permissions and controls you already have in Celigo, so you're never compromising on security.

Server tool list (49)

Raw names from tools/list. Only developers need these.

list_exportsData source steps (page generators) that fetch records from external systems. Each export is tied to a connection and defines what data to pull. adaptorType (e.g. HTTPExport, NetSuiteExport) determines the connector. Exports live inside flows as pageGenerators[]. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified,_connectionId,adaptorType,draft (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/exports
upsert_exportCreate or update Data source steps (page generators) that fetch records from external systems. Each export is tied to a connection and defines what data to pull. adaptorType (e.g. HTTPExport, NetSuiteExport) determines the connector. Exports live inside flows as pageGenerators[]. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/exports
list_importsData destination steps (page processors) that write records to external systems. Each import is tied to a connection and defines how to push data. adaptorType (e.g. HTTPImport, NetSuiteDistributedImport, AiAgentImport) determines the connector. Imports live inside flows as pageProcessors[]. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified,_connectionId,adaptorType (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/imports
upsert_importCreate or update Data destination steps (page processors) that write records to external systems. Each import is tied to a connection and defines how to push data. adaptorType (e.g. HTTPImport, NetSuiteDistributedImport, AiAgentImport) determines the connector. Imports live inside flows as pageProcessors[]. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/imports
list_flowsPipelines that move data from source (exports) to destination (imports). A flow contains pageGenerators[] (exports) and pageProcessors[] (imports/lookups), optionally with routers[] for branching. Flows can be scheduled via cron or triggered by webhooks. Always create flows with disabled: true until verified. For error triage, use list_flows with hasOpenErrors or includeErrorCounts before drilling into list_flow_errors. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): disabled,lastModified,_integrationId,schedule (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
upsert_flowCreate or update Pipelines that move data from source (exports) to destination (imports). A flow contains pageGenerators[] (exports) and pageProcessors[] (imports/lookups), optionally with routers[] for branching. Flows can be scheduled via cron or triggered by webhooks. Always create flows with disabled: true until verified. For error triage, use list_flows with hasOpenErrors or includeErrorCounts before drilling into list_flow_errors. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
run_flowRun a flow — queues an on-demand execution and returns `_jobId`. Use `list_jobs` with `_id` set to that `_jobId` to poll status and inspect results (parent job + per-step children). The flow must be enabled (`disabled: false`) and belong to an enabled integration. Optional `body` parameters: - `export.startDate` / `export.endDate` — override the delta window for this run only (useful for backfills). - `_exportIds` — array of export ids to run only specific generators (useful for multi-source flows). Omit `body` or send `{}` to run with the flow's configured behavior. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
list_flow_errorsList open errors for flow steps. Four modes: 1. With `_id` + `_stepId`: errors for a specific step (body-paginated, returns `{ errors, nextCursor?, hasMore }`) 2. With `_id` only: errors for all steps in that flow (grouped by step, each with its own nextCursor). Empty steps (no errors) are omitted. 3. With `_stepId` only: finds the flow containing that step, then returns errors for that step 4. Without `_id` or `_stepId`: errors across all flows, optionally filtered by `_integrationId`. - Default (`summary` omitted or `true`): returns `{ summary: true, totalErrors, affectedFlows, flows: [{ flowId, flowName, steps: [{ stepId, stepName, stepType, numError, lastErrorAt? }] }] }`. Only flows/steps with errors are included. Use this to locate problems, then drill into specific flows with mode 1 or 2. - `summary=false`: returns full error objects per step (same shape as modes 2-3). Empty flows and steps are omitted. Modes 2-4 (detail): `{ flows: [{ flowId, flowName, steps: [{ stepId, stepName, stepType, errors, nextCursor?, hasMore }] }] }`. Each step's `nextCursor` can be used with mode 1 (`_id` + `_stepId` + `cursor`) to fetch more errors for that step. Each error object includes: - `errorId` — use in `triage_flow_errors` actions: `resolve` (`errors`), `assign` (`errorIds`), `tag` (`errors[].id`) - `retryDataKey` — use in `triage_flow_errors` actions: `retry` (`retryDataKeys`), `tag` (`errors[].rdk`); also pass to `get_flow_error_retry_data` - `message`, `code`, `traceKey`, `occurredAt` — diagnostic info For the full retry snapshot, call `get_flow_error_retry_data` with `_id`, `_stepId`, and `retryDataKey`. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
get_flow_error_retry_dataGet the stored retry-data snapshot for one error (`retryDataKey` from `list_flow_errors`). Returns the envelope the runtime captured at failure (`data`, `stage`, request/response fields where applicable). Use before `update_flow_error_retry_data` when fixing staged payload. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
update_flow_error_retry_dataFull-replace of the stored retry-data snapshot for one error. Body is the complete envelope from `get_flow_error_retry_data` (mutate `data` as needed). Does not reprocess — call `triage_flow_errors` with action `retry` afterward. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
list_execution_logsFlow run execution logs (debug/trace). Requires `_id` (flow) and `_jobId` (parent job from `run_flow` or `list_jobs`). Flow must have debug logging armed (`logging.debugUntil` on the flow). Three modes: 1. **Index** — `_id` + `_jobId` only → `GET /v1/flows/{id}/jobs/{jobId}/logs`. Returns entries with `recordId`, `groupId`, `traceKey`, `_expOrImpId`. Optional client filters: `_stepId`, `traceKey` (substring). 2. **Metadata** — `_id` + `_jobId` + `_stepId` + `recordId` + `groupId` (+ optional `traceKey`) → `POST .../logs/metadata/query`. Step execution timeline without full payloads. 3. **Data** — same as metadata + `stage` → `POST .../logs/data/query`. Returns request/response payloads for one stage (can be large). Typical path: `run_flow` → `_jobId` → mode 1 → pick a row → mode 2 or 3. `traceKey` from `list_flow_errors` can narrow index results or enable cross-step trace in metadata mode. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows
list_connectionsCredentials and configuration for external systems. Each connection holds auth details (API keys, OAuth tokens, etc.) and is shared across exports and imports. Name connections after the system, not the operation (e.g. 'Shopify - my-store', not 'Shopify - Customer Upsert'). The type field determines the connector (e.g. http, netsuite, salesforce). Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/connections
upsert_connectionCreate or update a connection. Without `_id`, POSTs a new connection (the server assigns an id). With `_id`, PUTs the full document (replace). SAFETY (PUT branch only): payloads containing the API's masked-credential placeholder (`******`) are rejected unless `force: true` is set, so a re-PUT of a previously read connection cannot wipe stored writeOnly secrets. To edit a non-credential field, omit credential fields from `body` entirely — Celigo preserves writeOnly values when they're absent from the PUT. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/connections
list_integrationsTop-level containers that group flows, connections, and resources into a logical project. Every flow belongs to an integration. Use list_integrations to see all projects in the account. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): mode,sandbox,lastModified,description (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/integrations
upsert_integrationCreate or update Top-level containers that group flows, connections, and resources into a logical project. Every flow belongs to an integration. Use list_integrations to see all projects in the account. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/integrations
list_scriptsJavaScript hook scripts for data transformation and custom logic. Scripts are referenced by exports/imports via the hooks object (preSavePage, preMap, postMap, postSubmit, postResponseMap). The content field holds the JS code. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/scripts
upsert_scriptCreate or update JavaScript hook scripts for data transformation and custom logic. Scripts are referenced by exports/imports via the hooks object (preSavePage, preMap, postMap, postSubmit, postResponseMap). The content field holds the JS code. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/scripts
list_ai_agentsCeligo AI Agents (import steps with adaptorType AiAgentImport). Configure via `aiAgent` — provider (openai/gemini), model, system instructions, tools (Celigo tools and/or MCP). POST/PUT /v1/imports. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified,_connectionId,adaptorType (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/ai-agents
upsert_ai_agentCreate or update Celigo AI Agents (import steps with adaptorType AiAgentImport). Configure via `aiAgent` — provider (openai/gemini), model, system instructions, tools (Celigo tools and/or MCP). POST/PUT /v1/imports. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/ai-agents
list_guardrailsGuardrails (PII detection, content moderation, AI safety checks) Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified,_connectionId,adaptorType (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/guardrails
upsert_guardrailCreate or update Guardrails (PII detection, content moderation, AI safety checks) Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/guardrails
list_apisCustom API endpoints for external integrations Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/apis
upsert_apiCreate or update Custom API endpoints for external integrations Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/apis
list_environmentsSandbox and staging environments Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/environments
list_iclientsOAuth2 iClients (app registrations for OAuth flows) Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/iclients
upsert_iclientCreate or update OAuth2 iClients (app registrations for OAuth flows) Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/iclients
list_lookup_cachesIn-memory key-value stores for lookups and deduplication. Use `list_lookup_caches` (Phase 1) to find a cache `_id`; `upsert_lookup_cache` (Phase 2) creates the cache resource. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/lookup-caches
upsert_lookup_cacheCreate or update In-memory key-value stores for lookups and deduplication. Use `list_lookup_caches` (Phase 1) to find a cache `_id`; `upsert_lookup_cache` (Phase 2) creates the cache resource. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/lookup-caches
list_lookup_cache_dataRead entries from an existing lookup cache. Requires cache `_id` from `list_lookup_caches`. Omit filters for the first page (~1000 entries); pass `key` (single entry), `keys` (array), or `startsWith` (prefix). Response includes `data[]` with `value` or `error` per key. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/lookup-caches
upsert_lookup_cache_dataLoad or replace entries in an existing lookup cache. Body: `{ data: [{ key, value }, ...] }`. Automatically splits into batches of 1000 entries (API limit per request). Returns merged per-key results; includes `batches` when more than one request was sent. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/lookup-caches
delete_lookup_cache_dataRemove entries from a lookup cache. Pass `key` or `keys` to delete specific entries (`DELETE .../data` with `{ keys }`). Omit both to purge all entries (cache resource is kept). Does not delete the cache itself — use `delete_resource` for that. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/lookup-caches
list_toolsReusable building blocks for integrations Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/tools
upsert_toolCreate or update Reusable building blocks for integrations Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/tools
list_mcp_serversMCP server resources exposing tools and APIs Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/mcp-servers
upsert_mcp_serverCreate or update MCP server resources exposing tools and APIs Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/mcp-servers
list_tagsList all error tags in the account. Use each entry's `tagId` short code (not Mongo `_id`) in `triage_flow_errors` (`tagIds` on action `tag`). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/tags
list_audit_log_entriesList audit log entries (newest first). Returns a page `{ items, hasMore, paginationNote }` where each item includes `resourceType`, `_resourceId`, `fieldChanges[]` (fieldPath, oldValue, newValue), `byUser`, and `time`. Defaults to `limit=50` when omitted (API max 1000). Filter by `resourceType` (and optional `_resourceId`), `_byUserId` (or `support` for Celigo support), and date range (`from`, `to` ISO-8601). Optional `source`, `action`. Page forward in time using `to` — see `paginationNote` in the response. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/audit-logs
list_edi_profilesEDI interchange envelope profiles for B2B Manager (X12 ISA/GS and EDIFACT UNB control fields). Define sender/receiver IDs, qualifiers, and standards versions used when exchanging EDI documents with trading partners. Required to configure B2B EDI flows. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/edi-profiles
upsert_edi_profileCreate or update EDI interchange envelope profiles for B2B Manager (X12 ISA/GS and EDIFACT UNB control fields). Define sender/receiver IDs, qualifiers, and standards versions used when exchanging EDI documents with trading partners. Required to configure B2B EDI flows. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/edi-profiles
list_file_definitionsFile structure and parsing rules for structured files (CSV, fixed-width, EDI X12, EDI EDIFACT). Exports and imports reference a file definition to control how rows, columns, segments, and elements are parsed or generated. Required alongside EDI profiles when building B2B flows. Dual-purpose tool: omit `_id` to list the collection (summary metadata via Celigo `include` projection when supported; optional pagination via `limit`/`cursor`); set `_id` to fetch the full resource configuration. Pagination and `include`/`exclude` are ignored when `_id` is set. Default list projection (when you omit include/exclude): lastModified,format,version (plus _id and name from the API). Override with `include` or `exclude` as needed. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/file-definitions
upsert_file_definitionCreate or update File structure and parsing rules for structured files (CSV, fixed-width, EDI X12, EDI EDIFACT). Exports and imports reference a file definition to control how rows, columns, segments, and elements are parsed or generated. Required alongside EDI profiles when building B2B flows. Omit `_id` to create (POST — server assigns id); provide `_id` to update (PUT — full-document replace). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/file-definitions
list_edi_transactionsQuery the B2B Manager EDI transaction log. Dual-purpose: omit `_id` to list (POST /v1/ediTransactions/query); set `_id` to return one transaction (scans the query log). With `_id`, list defaults (`fileType=X12`, `limit=100`, 30-day `startDate`) are not applied; optional filters you pass (`fileType`, `documentType`, `startDate`, …) narrow the scan. `fileType` is the EDI standard family (`X12` or `EDIFACT`, default `X12`). `documentType` is the specific document code (X12: `"850"`, `"810"`, `"997"`; EDIFACT: `"ORDERS"`, `"INVOIC"`, …). **`X12` and `EDIFACT` are not valid `documentType` values** — the API rejects them. Defaults: `fileType=X12`, `limit=100`, `startDate` = last 30 days. Dates accept ISO-8601 strings or epoch milliseconds. Set `includeFaDetails` and/or `includeMdn` to fetch extra GETs (`/faDetails`, `/mdn`) per returned transaction — one (or two) additional API call **per row** on the current page, run in parallel. With default `limit=100` and both flags set, that can mean 1 query POST plus up to 200 GETs. Prefer `_id` for a single transaction, or use a smaller `limit`, when you need FA/MDN detail on list results. FA details require `fileType` on the record (from the query result or your `fileType` arg). List mode always returns `{ ediTransactions, hasMore, nextCursor? }`. Use `nextCursor` from the response as `cursor` on the next call (maps to API `pageToken`). Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/edi-transactions
update_edi_fa_statusUpdate functional-acknowledgement status on a batch of EDI transactions (PATCH /v1/ediTransactions). Body: `{ "fileType": "X12"|"EDIFACT", "ediTransactions": [{ "_id": "...", "faStatus": "accepted"|"rejected" }, ...] }`. Only `accepted` and `rejected` are writable — other `faStatus` values are system-managed and records are silently skipped. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/edi-transactions
list_marketplaceBrowse the published marketplace catalog or preview one template's full blueprint. **List** (omit `_id`): `POST /v1/published/combined` sorted by `numInstalls` (default). The API returns the **full published catalog** in one call; `docType` and `includeConnectors` filter that result client-side (the upstream API has no server-side type filter). Returns lightweight rows `{ _id, name, description, summary }` where `summary` carries `docType`, `numInstalls`, `applications`, and `lastModified`. **Templates only by default** — Connectors (integration apps) are excluded unless `includeConnectors` is true or `docType` is set. Prefer preview mode (`_id` set) when you already know which template you need. **Preview one template** (set `_id`): `GET /v1/templates/{_id}/preview` — full install blueprint (`objects[]` with `{ model, doc }` per resource, plus `stackRequired`). Use Connection entries' `_id` values to build `connectionMap` for `deploy_template`. Only works for `docType=Template` marketplace ids — Connector ids return 404. Distinct from account-owned template CRUD at `/v1/templates` (partner publishing); this tool targets the **published** catalog only. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/marketplace
deploy_templateInstall a published marketplace template, creating a new integration (POST /v1/integrations/template/{_id}). **Requires `connectionMap`** in `body`: maps each template Connection `_id` (from `list_marketplace(_id)` preview `objects` where `model=Connection`) to a real connection `_id` in your account. Example: `{ "connectionMap": { "61f92026dd053843b5d72350": "64a1234567890abcdef12345" } }` Run `list_marketplace` with `_id` first to discover which connections the template expects and to review example flow/export/import configs before deploying. **Response:** On success the API returns either: - `{ "_integrationId": "<id>" }` — most common; use this id with `list_integrations`, `list_flows`, etc., or - An array of created resources `[{ "model": "Integration", "_id": "..." }, { "model": "Flow", "_id": "..." }, ...]` — find the entry with `model: "Integration"` and use its `_id` as the new integration id. There is no top-level `_id` on the object form; do not assume the response is the integration document itself. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/templates
delete_resourceDelete a resource by `_id`. Pass `resourceType` to select the resource family (allowed values: exports, imports, flows, connections, integrations, scripts, ai-agents, guardrails, async-helpers, apis, iclients, lookup-caches, tools, mcp-servers, edi-profiles, file-definitions). For `connections`, a dependency pre-flight runs first and dependents are returned in `warnings[]` — but the delete **always proceeds** (warnings are advisory only). All other resource types delete immediately with no dependency scan. Returns `{ deleted, id, warnings, response }`. The `force` flag is reserved for future blocking behavior; today it is a no-op. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference
get_schema**Essential companion to upsert_* tools.** Returns exact field structures, required properties, enum values, and array vs object distinctions. Call BEFORE creating or updating resources to avoid validation errors. **Targets:** `target='resource'` — Platform resource schemas (flow, export, import, connection, script, etc.). Use 'resource/sub' for adaptor-specific shapes (e.g., 'connection/netsuite', 'import/http'). Examples: `get_schema(target='resource', name='flow')` before `upsert_flow`. `target='connector'` — **Discover fields before building an export.** Two modes: - Pass a **connection `_id`** (NetSuite, Salesforce, RDBMS, etc.) to retrieve native application metadata — record types, fields, picklist values. This is the "what can I pull from this system?" discovery step before constructing export queries. - Pass an **HTTP connector ID or name** to get catalog connector definitions. `target='connector_openapi'` — OpenAPI document fragment for an HTTP connector's REST surface. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference
search_knowledge_baseSearch the Celigo Knowledge Base and get AI-generated answers about integrator.io. Uses RAG (Retrieval-Augmented Generation) to search relevant documentation (help center, community, guides) and synthesize answers. Supports conversational follow-ups using thread_id for context continuity. Enable context_aware mode with a url parameter to get answers specific to a UI location. Queries the Celigo Knowledge Base — see https://docs.celigo.com
triage_flow_errorsPerform one flow-step error action. Requires `_id` (flow), `_stepId` (export/import id), `action`, and `body`. Field mapping from `list_flow_errors` response: - `errorId` — unique error identifier, use in `resolve` and `assign` actions - `retryDataKey` (alias `rdk`) — retry snapshot key, use in `retry` and `tag` actions Actions and their body schemas: - `retry` — `{ retryDataKeys: [<retryDataKey>, ...] }` — reprocess errors (**writes to destinations; confirm with user first**) - `resolve` — `{ errors: [<errorId>, ...] }` — mark errors as resolved/handled - `tag` — `{ errors: [{ id: <errorId>, rdk: <retryDataKey> }, ...], tagIds: [<tagId>, ...] }` — apply tags (codes from `list_tags`) - `assign` — `{ errorIds: [<errorId>, ...], email: "<user@example.com>" }` — assign errors to a user Typical workflow: `list_flow_errors` → (optional) `get_flow_error_retry_data` / `update_flow_error_retry_data` → `triage_flow_errors`. Calls the Celigo integrator.io REST API — see https://developer.celigo.com/api/api-reference/flows