When a file-based import writes JSON or XML files, then define each file's structure with a handlebars template. This article is for builders who send records to FTP, SFTP, Amazon S3, Azure Blob St...
B2B - Automated VAN mailbox creationSetting up a VAN connection is now self-serve. Previously the connection form told you to email Celigo to have a mailbox provisioned by hand; now you create the ...
Content-based routing (CBR) decides which flow in integrator.io receives each electronic data interchange (EDI) document that arrives from the value-added network (VAN). All inbound documents from ...
The Alerts page lists every long-runtime alert you have access to in an integration, so you can search, filter, edit, delete, and manage recipients in bulk instead of opening each flow individually...
Long-running flow alerts let you proactively monitor flows that run longer than a limit you set. These alerts inform you about unexpected delays as soon as they happen — even when you're away from ...
The Celigo platform (integrator.io) lets you exchange EDI documents with your trading partners using the Trading Partner Connector Framework (TPCF). TPCF isn't tied to a single connection type — it...
This article explains how B2B shipping label entitlements work in integrator.io — what counts toward your limit, how to monitor your current usage, and how to review your historical usage over time...
The getLookupCacheData helper reads a value from a lookup cache and inserts it in your Handlebars template. A lookup cache is an account-level store of reusable data. Unlike the lookup helper, whic...
Lookup cache usage in integrator.io is measured in units: each read or write request your flows make against a lookup cache is one unit, and your subscription sets a monthly unit limit. This articl...
Error: Celigo did not receive EDI docs such as 850 from Target because of a No connection found error. Explanation: The Target connection fails because our AS2 routing is set to recognize the Recei...