OverviewYou classify documents in integrator.io with an AI agent that reads each document and returns its type from a list you define. A branch then routes each type to its own extraction agent and...
This FAQ answers common questions about the MySQL listener, which streams row changes from MySQL into a flow using change data capture (CDC). It's for builders and database administrators (DBAs) wh...
You can connect a Celigo MCP server to a Microsoft Copilot Studio agent as a tool. Copilot Studio reads the tools the MCP server exposes, shows each tool's inputs, and lets the agent call those too...
Celigo Storage works as a built-in file provider in flows, so you can read and write files without connecting an external service such as Amazon S3, Azure Blob, or SFTP. Using the Celigo APIs conn...
This article describes how to export files from Azure Data Lake Storage Gen2 (ADLS Gen2) and look up files and records on a per-record basis. Create an Azure Data Lake Storage Gen2 export Start ...
Celigo sync determines the data type for each destination field using source application metadata, destination application requirements, and, when needed, the actual values returned during sync con...
Event logs capture phases of a Celigo sync's run to help you analyze its data ingestion progress. To view them, go to the sync's integration, select the sync name, then select Event logs from the t...
Data extracted from documents in integrator.io passes through three layers of checks before it reaches a destination: Celigo validates the AI agent's response against your schema, the agent flags v...
Every table that Celigo sync creates includes system columns alongside your source fields — Celigo-managed metadata that supports soft deletes, merge behavior, and run traceability. This article de...
To follow the principle of least privilege, integrator.io allows you to scope API tokens to designated Celigo Storage folder paths. This restricts external processes to authorized directories, auto...