🚀 Connect: Flow Problem Solvers 🚀

Overview

As well as a substantial library of specific MIS plugins, we also offer our own Infigo Connect: Flow plugin. This plugin was developed as more of a general catch all for integrations where a JSON or XML file is required to be created on order placement and then absorbed by a third party system.
This article aims to explain the basics around what our Infigo Connect: Flow plugin does and how you can use it within your Infigo setup.

What does the plugin do?

The Infigo Connect: Flow plugin provides job information in a specified file type and format that can then be handled externally by a third party software.

When does it get triggered?

This depends on the product types that are being ordered but fundamentally when an order is placed.
If you are ordering variable products (MegaEdit or Infigo Editor) then it will wait until the dynamic output files have been created. 

If you are ordering standard products or static products that do not require an output then it will trigger as soon as the order is placed and paid for.

What file types are supported?

As part of the configuration you have the option to generate either an XML or a JSON file. These are in a specified format and structure that we have pre-determined and examples of both can be found below.

What if these formats are not what we require?

As part of the configuration we allow for an XSLT file to be applied to the XML so that it can be transformed into any format. This means that you can take our standard XML format we create and from that generate a different XML, HTML, XHTML, plain text etc. What we export will then be in a format you expect and can handle.

How do I get the data I want?

At the bottom of this article is a sample XML that you can use to assist in creating your XSLT. Additionally in the configuration page there is a download example XML link.

By default, data is received in JSON format. To change this, simply enable XML Data format:

You can also automatically escape special characters by enabling the setting, and pause order processing with the setting enabled:

We can also send only specified products and product attributes via external IDs. This may useful if you only need certain products to be sent to your 3rd party system.

Can I download assets from an XML?

Yes, we can send asset links into the XML. This scenario would be useful if you did not want to use our hotfolders; the XML will contain a link per orderline of the assets to be downloaded. To enable this simple toggle on these asset settings under Asset Configuration:

Your received XML will then have a link to the artwork that can be open and downloaded.

We can also send links for Job Tickets, Invoices, and Packing Slips. Just enable the files you want to receive in the XML as links:

Where can the files be placed?

The Infigo Connect: Flow plugin supports downloading the data file into a specific hot folder, this can be configured per storefront and will then allow you to download it through Infigo Sync.

To set this up, simply enable Drop to Hotfolder, then route the XML to the folder of your choice:

OR we support exporting the file to an FTP location. This can be done by enabling Post to FTP then inserting your FTP details:

OR we support the ability to post the file to an API endpoint, along with credentials, so that it can be sent directly to a third party system.

Can I email my JSON or XML directly to someone?

Yes - under Email Details simply check Send to Emails and insert the email address(es), you can also BCC an email if needed. 

We have a predefined Email ESLT you may use called Email, or, write your own for your needs. 

Want help from Infigo Software to generate the transformation files?

This is a professional service that we offer at an additional development charge.
If you want to request assistance then please provide us with the following:
* Download our example XML file, take a look at all the fields provided
* Generate an XML file in the format that you require
* Add the mapping for the fields that we provide in your structure, so that each field in your structure is mapped to a field from our structure.
* If you want it posted to an API end point then please supply us with the credentials and ensure that we have access.

What is the extra data node?

Extra data is an additional data attached to the order and/or order line. It is a key/value property which can be set using MegaScript or API mechanism.
Once the order/orderline contains the extra data, Infigo Connect: Flow will include it in json/xml request.

What is the "Exclusion list for Extra Data" setting?

The exclusion list is a list of extra data which are ignored for order/orderline request.
To exclude a specific extra data you need to write the extra data key in the textbox.
Each new extra data should be separated by a new line.
There is a possibility to exclude the extra data by a regular expression.

Many customers’ downstream systems (ERPs, fulfilment hubs, reporting tools, etc.) need the Stripe CaptureRequestId to reconcile payments.
This artfcle introduces:

1. Database support – a CaptureRequestId column is present on the Transaction table.

2. Connect: Flow “Payment” node – an optional block of detailed payment data (including CaptureRequestId) that can be added to every MIS.Generic XML/JSON payload.

3. A new settings group – lets you turn the Payment node on or off globally and/or per supplier.

   • 
   • 
   • 

Key settings

Fields inside the <Payment> node

PaymentMethod
PaymentTransactionId
CaptureTransactionId
PurchaseOrderNumber
InfigoTransactionId
AuthorizationRequestId
CaptureRequestId   ← new & critical
CurrencyCode
Amount
AuthorizationExpirationDateUtc
TransactionDateUtc

Typical use cases

Step-by-step implementation guide

1 Enable the Payment node

1. Sign in as an administrator.

2. Navigate to Admin ➜ Configuration ➜ Plugins ➜ Connect: Flow [Configure]

3. Toggle “Include payment information” to ON.

   • 

4. Save your changes.

3 Verify the payload

1. Place a test order on a storefront that uses ExternalPayments.

2. Allow the Connect Flow job to post to your test API endpoint

   • or view the “Extra Data” preview in the order details. (Sales ➜ Orders ➜ View [Order] ➜ Extra Data [Section]

   • 

3. Confirm the <Payment> node is present and contains the fields listed above, including a non-null <CaptureRequestId>.

Overview

Connect: Flow can embed two history related, fully-structured data blocks in every order export (XML or JSON):

• Job History – a chronological log of all order-level status changes.

• Approval History – a dedicated log of approval events that captures the approver’s comments (e.g., a billing code) alongside the status that triggered the event.

These optional nodes give your MIS or downstream XSLT transformations immediate visibility of what happened, when it happened, and, for approval events, why it happened. The result is cleaner hand-offs to production, richer reporting, and fewer support calls asking “what changed?”

Key Settings

Good to know:

• Both settings are independent. You can export only job history, only approval history, or both, depending on the needs of each supplier-specific flow.
• Both settings can be applied at a general level for Connect: Flow or on a supplier basis

 

What You’ll See in the Payload

Each history entry is serialised as a HistoryItem with the following fields:

The approval log is automatically filtered to include only: UnapprovedOrder, AwaitingApproval, PartiallyApproved, Approved, and Rejected.

4️⃣ Typical Use Cases

1. Billing-code hand-off to an MIS
   Approver enters a billing code in the approval comment. The MIS extracts it from the Info field of the first Approved entry and routes the job to the correct cost-centre.

2. Shop-floor dashboards
   Production screens poll the job-history node to display live status changes without hitting the storefront API.

3. Supplier-specific compliance logs
   For suppliers that require a full audit trail, enable both settings at supplier level; for low-touch suppliers, leave them disabled to reduce payload size.

5️⃣ Step-by-Step Implementation Guide

1. Open the Connect → Flow plug-in settings

   • In your storefront admin, navigate to Admin ➜ Configuration ➜ Plugins ➜ Connect: Flow [Configure].

   • (If supplier overrides are required) open Admin ➜ Configuration ➜ Plugins ➜ Connect: Flow [Configure] ➜ Suppliers [Section].

   • 

2. Enable the desired history blocks

   • Tick Include job history to insert the <History> node.

   • Tick Include approval history to insert the <ApprovalHistory> node.

   • 

3. Update or create your XSLT / JSON transform

   • Map the new nodes into the target schema.

   • Example XSLT snippet for approval comments (XML):

   <ApprovalComments>
     <xsl:for-each select="ApprovalHistory/HistoryItem">
       <xsl:if test="Status='Approved'">
         <xsl:value-of select="Info"/>
       </xsl:if>
     </xsl:for-each>
   </ApprovalComments>
   

4. Place a test order

   • Use a product that requires approval.

   • Approve the job and enter a distinctive comment.

   • Download the raw export from Admin → Sales→ Orders → [Order] → Extra Data and verify that:

     • The <History> and/or <ApprovalHistory> nodes are present.

     • Your comment appears in the Info field of the Approved entry.

     • Timestamps are in UTC.

5. Validate downstream processing
   Run the export through your MIS or a staging transform to ensure the new data is consumed correctly.