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...
This article describes how to import files and records to Azure Data Lake Storage Gen2 (ADLS Gen2). Create an Azure Data Lake Storage Gen2 import Start creating an import to Azure Data Lake Stor...
Scheduling and running a sync in Celigo ensures seamless, automated data flow between your critical business applications, eliminating manual data entry and preventing operational bottlenecks. By c...
The Celigo platform offers scalable editions that cater to a range of automation needs, from basic workflows to enterprise-wide integrations. Each edition offers varying levels of performance, sec...
Using a multi-environment structure with API Management (APIM) gives you more control over how your API changes are developed, tested, and released to your API consumers. Your environments in the...
You can automate purchase orders from trading partners that send orders as PDF or spreadsheet files — by email or file upload, instead of EDI — with a flow that reads each order with intelligent do...