Overview
Connect: Flow is designed to push data, artwork and metadata from Infigo directly into your internal systems. To support this, it sends secure HTTPS POST requests to an endpoint that you provide.
This article explains how Connect: Flow communicates, how your firewall interacts with it, and what this means for security within your environment.
How Connect: Flow Communicates
Connect: Flow sends secure HTTPS POST calls from Infigo into your system.
This means the request always originates from Infigo’s servers and is delivered to a specific URL that you control.
Your environment never has to open unrestricted inbound access. You decide exactly what Infigo can connect to.
Firewall Behaviour
You stay fully in control of your security setup. Your team can restrict access by:
• Allowing only Infigo’s IP ranges
• Requiring authentication (API key, token, Basic Auth, etc.)
• Ensuring the endpoint only accepts HTTPS traffic
• Limiting the endpoint to specific routes or paths
When configured this way, nothing else can access the endpoint. Connect: Flow does not expose your server to general incoming traffic, it only accepts the secure calls you permit.
Is Connect: Flow Secure?
Yes. Connect: Flow is secure when you:
• Lock down the receiving endpoint
• Allow only Infigo’s outbound IPs
• Require authentication
• Use HTTPS exclusively
Many customers with strict IT policies use Connect: Flow safely by controlling exactly what their server receives.
When to Use Connect: Flow
Use Connect: Flow when you want:
• Infigo to push order updates into your system
• Artwork files to be delivered automatically
• Metadata and job information sent directly into your MIS or workflow tool
Need Further Detail?
If your IT department needs additional technical clarification, firewall considerations, or IP ranges, please contact the Infigo Support Team.