This pathway teaches you how to get Connect: Flow up and running end-to-end, allowing you to push data out of Infigo into a wide variety of third party systems. This series covers: enabling the plugin, confirming it generates outputs, configuring the general settings (including output structure and which products can trigger Flow), selecting and setting up distribution methods (FTP, API, Email, Hotfolder, Webhooks), and tailoring outputs per supplier when different downstream partners have different requirements.
By the end, a learner should be able to:
- Enable Connect: Flow and validate that it’s producing outputs.
- Configure general settings, including output configuration and controlling which products can trigger Flow.
- Choose and configure one or more output distribution methods (FTP, API, Email, Hotfolder, Webhooks) based on what the third-party system can accept.
- Route/configure different behaviour per supplier (e.g., one supplier via email, another via FTP).
Intended for Infigo admins / implementers / technical ops who are responsible for getting order/job data out of Infigo via Connect: Flow to downstream systems (suppliers, MIS/ERP, automation, hotfolders, webhook consumers).
- Admin access to your Infigo storefront or platform.
- Basic understanding of XML vs JSON and what an endpoint is (FTP/API/webhook).
- Awareness of how suppliers are represented in Infigo (even if supplier creation isn’t the focus here).
- For full configuration, skills with the creation of XSLT scripts will be required, allowing you to change Infigo formatted data into that of your third party system.
Extra resources to deepen your understanding.
Spotted something outdated, unclear, or not working as expected? Send us a quick note — we’ll take a look and keep things current.