What this article covers

This article explains how to configure the new HubSpot CRM integration using Infigo MegaScripts.
You’ll learn how the integration works, what’s included, and how to set it up to automatically create or update contacts, deals, and order data in HubSpot when a customer places an order.

About this feature

The HubSpot CRM integration allows you to automatically synchronise Infigo customer and order information with your HubSpot environment.
When configured, Infigo uses a MegaScript to connect with the HubSpot API — creating or updating contacts, deals, and related records whenever an order is placed.

This ensures your sales and marketing teams can track live order progress directly in HubSpot without manual data entry, maintaining a single, accurate source of truth between systems.

What’s included

• A new integration workflow between Infigo and HubSpot CRM

• Ability to create or update contacts, deals, and orders automatically

• Integration built on MegaScripts, giving you full control over mapping and behaviour

• Support for affiliate-based deal naming and linking

• Configurable success and error handling pages

Key settings

• MegaScript trigger: Set to run On Place Order so HubSpot receives data when orders are confirmed.

• HubSpot Properties: Define mapping for deal and contact objects (pipeline, deal stage, owner ID, etc.).

• Affiliates: Links orders to affiliate data for structured deal naming and tracking.

• Plugin Connection: Managed through Connect: Scripting to tie your MegaScript instance to storefront events.

Use cases

• Sales automation: Automatically create a HubSpot deal whenever a customer places an order.

• Customer management: Keep customer and contact details in sync between HubSpot and Infigo.

• Marketing visibility: Give sales and marketing teams a unified view of order status and pipeline performance.

• Affiliate tracking: Use affiliate links to group deals or attribute them to sales partners.

Step-by-step implementation

Step 1 – Create the MegaScript

1. Ask our support team for the needed MegaScript and they will provide this. Then go to Admin → MegaScript Management and click Add New. Create a new script using the MegaScript our support team provided.

2. Navigate to Admin → MegaScript Instances and create a new instance based off of the script you created above

3. Choose Trigger on Event and set it to Place Order.

4. Enter your configuration JSON, including HubSpot connection details, for example:

    

   {
logLevel: 4,
pluginSystemName: 'mis.scripting',
hubSpotProperties: {
deal: {
pipeline: 'default',
dealStage: 'closedwon',
associationCategory: 'HUBSPOT_DEFINED',
associationTypeId: 3,
// hubspot_owner_id: xxx,
},
contact: {
// hubspot_owner_id: xxx
}
}
}

5. Save the MegaScript.

Step 2 – Connect the MegaScript to your storefront

1. Navigate to Connect Plugins → Connect Scripting.

2. Select your storefront and assign the MegaScript you just created to the Place Order event.

3. Save changes.

Step 3 – Set up affiliate tracking (optional)

1. Go to Admin → Affiliates and create a new affiliate.

2. Copy the generated affiliate URL.

3. Share this URL or use it in campaigns — orders placed through it will automatically link to the affiliate ID.

Step 4 – Test the integration

1. Place a test order in your storefront.

2. In HubSpot, verify that:

   • A contact is created or updated for the customer’s email address.

   • A deal is created in the correct pipeline and stage.

   • The deal name matches your affiliate or customer mapping.

3. Confirm no duplicate records are created.

Step 5 – (Optional) Customise error handling

1. Use the success and error configuration options in your MegaScript to display different pages depending on API response.

2. This helps provide clear messaging to users or trigger internal notifications if synchronisation fails.

Tips & best practice

• Test your configuration with a sandbox HubSpot account before going live.

• Keep API credentials secure — do not hardcode keys in plain text.

• Review HubSpot rate limits if you expect high order volumes.

• Use MegaScript logging (logLevel 4) for detailed troubleshooting.

This is a quick reference for bulk linking Infigo customers to a Connect integration user by setting the customer’s External ID during Customer CSV Import.

It applies to any Connect plugin that exposes a customer external reference field via the CSV Import page or when clicking the Connect Link button on a customer entry. Common examples include Connect: printIQ, Connect: Tharstern, Connect: CERM, and Connect: Veracore.

This does not bulk create customers in your MIS or other external system. It links customers across systems using the external identifier.

For the full customer import walkthrough and troubleshooting, use the main guides here:

• https://academy.infigo.net/p/2428

• https://academy.infigo.net/p/291

When to use this

Use this when you are implementing an MIS or integration alongside Infigo and you want to:

• Bulk import customers into Infigo.

• Bulk update existing Infigo customers.

• Avoid opening each customer record just to press a Connect button, by supplying the external ID in the import instead.

Before you start

1. Ensure your Connect plugin is enabled and configured. Use the Academy setup guide for your plugin.

2. Gather the correct external identifier for each customer from the connected system. The exact value depends on the integration and the customer record structure in that system.

3. Keep imports manageable. We recommend 200 customers per CSV, then upload multiple files one after another if needed.

Step by step: bulk link customers to a Connect plugin via CSV Import

1) Download the Customer Template CSV

Go to Admin → Customers → Customer Management → CSV Import, then select Download Customer Template CSV.

2) Find the correct External ID column header for your Connect plugin

On the same CSV Import page, look for the info section that lists plugin link columns. It will show you the exact header text to use for each enabled Connect plugin.

Important notes:

• The headings are case sensitive.

• The value is usually not required, so you can include it only for customers you want to link.

3) Add a new column to your CSV using that exact header

Add a new column to the template CSV. The column header must match what the page shows for your plugin.

Example only: if you are using Connect: printIQ, the header shown is Mis.PrintIQ. Your environment may show different headers depending on which plugins are enabled.

Then populate each row with the customer’s external ID from the connected system.

4) Populate the rest of the customer rows as normal

Fill out the customer details you want to import or update. You do not need to fill every field. The importer validates the rows and reports any issues so you can fix and re upload.

For the full field list and import behaviour, use:

• https://academy.infigo.net/p/2428

• https://academy.infigo.net/p/291

5) Upload the CSV and run the import

Upload your CSV in the CSV Import tab and run the import. Infigo will create or update the customers, and store the external ID values so the customers are linked to the relevant Connect integration without needing per customer manual linking.

This article explains how to diagnose and resolve issues where product pages load slowly and external stock levels are not displayed in the storefront.

It is based on a resolved case where the integration failed to retrieve an authentication token from the external stock system after a network change. The guidance below walks through structured checks to quickly isolate whether the issue lies with configuration, connectivity, or endpoint changes.

Before escalating, complete the checks outlined below and collect supporting evidence (HAR files, screenshots, connector settings) to assist investigation.

Use Cases

• Product pages take significantly longer than normal to load.

• External stock levels do not display on product pages.

• The Add to Basket button is disabled or unavailable.

• The issue began after a broadband, firewall, or network infrastructure change.

• One storefront works correctly while another does not.

Key Settings to Review

• Connect Plugin – API URL
  Confirm the endpoint used to contact the external stock service.

• Connect Plugin – Credentials
  Verify the application ID/email/password used to request an authentication token.

• Handle Stock Setting
  Ensure the product or connector setting instructs the system to use the external connector for stock handling.

• Storefront Connector Mapping
  Confirm the connector is enabled for the affected storefront.

• Connection Test / Integration Logs
  Use the built-in test function to attempt token retrieval and review any error responses.

Step-by-Step Troubleshooting Guide

1. Confirm the Symptom

Open an affected product page and observe:

• Page load time

• Whether stock appears

• Whether Add to Basket is enabled

Document the behaviour.

2. Capture Browser Evidence

• Generate a HAR file from the browser Network tab.

• Check the Console tab for JavaScript errors.

• Capture screenshots showing missing stock or disabled purchase controls.

3. Compare Working vs Non-Working Storefronts

If another storefront is functioning correctly:

• Compare connector assignment

• Compare API URL configuration

• Compare stock handling flags

Differences here often identify misconfiguration.

4. Test the Connector

Use the Connect plugin’s Test Connection feature.

Expected outcome:

• A successful authentication token is returned.

If the response is null, empty, or errors:

• The integration cannot reach the external service

• The endpoint may be incorrect

• Credentials may be invalid

5. Verify the API Endpoint

If token retrieval fails, confirm:

• The external stock system’s public address has not changed.

• The connector is not pointing to an outdated IP address.

• The correct hostname or current public IP is configured.

In the referenced case, the external system’s public IP changed following a network migration, and the connector continued referencing the previous address. Updating the API URL resolved the issue.

6. Confirm Network and Firewall Rules

If the endpoint is correct but connection still fails:

• Confirm outbound traffic from the integration environment is not blocked.

• Confirm inbound firewall rules on the external system allow requests from the integration server.

• Verify no recent security rule changes were introduced.

Firewall allowlisting may be required depending on hosting setup.

7. Prefer DNS Over Raw IP (Best Practice)

If the external stock system is hosted on a connection where public IPs may change:

• Use a stable DNS hostname rather than a fixed IP address.

• This reduces risk of future outages following ISP or infrastructure changes.

8. Re-Test End-to-End

After configuration changes:

1. Re-run the connector test.

2. Reload a product page.

3. Confirm:

   • Stock loads promptly

   • Add to Basket is enabled

   • No console/network errors appear

9. When Escalating to Support

Provide:

• Product URLs

• HAR files

• Console logs

• Screenshots

• Connector configuration (obscure passwords)

• Details of any recent network or ISP changes

Including this information significantly reduces investigation time.

Summary of Confirmed Root Cause (From Resolved Case)

In the validated incident:

• The external stock system’s public IP changed following a network migration.

• The Connect plugin API URL still referenced the previous IP.

• The system could not retrieve an authentication token.

• Updating the endpoint resolved both slow loading and missing stock display.

Additional Resources

For further guidance, consult your internal integration documentation or contact your Support team for assistance.

Related links

• Infigo Academy – Connect plugin and third-party integration guides
  https://academy.infigo.net

Please watch our video tutorial here for a visual walkthrough: https://youtu.be/nB2bdcWOtgU?si=IZKPPcoLrp_rUIiL 

Important, please note: 

1. You cannot have 2 instances of Infigo Sync on the same computer or server. If you would like the sync to run on many storefronts, then you will require a platform API key. If you're running the sync on one storefront, then you can configure it at storefront level with a storefront API key. 

2. Before you start the installation process please switch off all other programs and processes (including antivirus software, and if installing on a sever, the firewall). These services interrupt the installation process and prevent install. 

InfigoSync is a Windows based service which polls your Infigo Platform and downloads any print ready jobs to hotfolders.

It is a two way service that identifies files have successfully reached their destination on your internal network, and automatically updates the status of the order in Shared Print Operations.

InfigoSync can also upload files to the Infigo system.

Installation

To Install InfigoSync, firstly you require an API token. In order to attain one, simply contact the support team and they will produce one for you. When requesting a token, please confirm whether you would like it to be created on the platform level, or confirm which storefront you would like it to be created on.

You will now see a string of letters and numbers. Copy this value to your clipboard.

1. Download InfigoSync

2. Run the installer you have downloaded from above. Note, this is a Windows ONLY installer

3. Paste your newly created API Token into the Infigo API Key field (shown below)

4. Enter the full site URL of your platform (using HTTP only)

5. Clicking Next allows the installer to search your platform for available print locations.

6. Select the Print Location relevant to you and complete the install.

7. Set your Download folder to the directory you require your jobs to be copied into.

Please note: basic installation is recommended for users, please contact Support for the guided installation of Advanced configurations (For use with: Upload Group, Batch CSV Group and Local Sync)

If your install is unsuccessful and it says "Catfish Sync Installer Setup Wizard ended prematurely because of an error...". The please switch off all other programs and processes (including antivirus software, and if installing on a sever, the firewall). These services interrupt the installation process and prevent install. 

The InfigoSync service does not start automatically. To start the service,

1. Go to Control Panel > Administrative Tools > Services

Locate Services:

Locate the InfigoSync Service in the list, and start the service.

New jobs will begin to appear in your local Download location (for example C:\InfigoSyncDownload)

How To Fault Find InfigoSync Issues

How do I check if files are uploading successfully?

There is currently no UI to manage files uploaded via InfigoSync, however there are a couple of ways you can see what has been uploaded.

• Check the InfigoSyncUpload Error folder, by default this is C:\InfigoSyncUpload and will contain any PDF's that InfigoSync has been unable to upload.
• Check the local InfigoSync error log C:\Program Files (x86)\[companyreference]\InfigoSync\infigosync.log, again this will detail any files that have errored.

If the above are reporting no errors then files have been successfully uploaded.  

How do I check the InfigoSync error log

• Check the local InfigoSync error log C:\Program Files (x86)\[companyreference]\InfigoSync\infigosync.log, this will detail any errors InfigoSync has reported.

How do I find my configuration file

• Check the same directory as for the log file; C:\Program Files (x86)\[companyreference]\InfigoSync\InfigoSync.exe.config

How do I check which Hotfolders jobs are dropping into

• Go to Shared Print Operations and find the job/s you are searching for, open the entry and check the 'Print Location/Hotfolders section to see where it currently is and manually copy to another hotfolder if necessary.

This article explains how to diagnose and resolve an issue where:

• The Infigo Sync Windows service fails to start with a logon error.

• Files remain in the hotfolder and do not move to the paste/output folder.

• No .lock file is present, yet processing does not occur.

In the referenced case, the root cause was insufficient Windows permissions for the service account, which prevented the service from starting and moving files. The issue was resolved after the machine’s permissions were corrected by IT.

When to Use This Guide

Use this guide if:

• The Infigo Sync service shows a Windows logon failure.

• You cannot modify the service Log On account.

• The Log On tab fields are greyed out.

• Files are stuck in the hotfolder with no .lock file present.

Step-by-Step Troubleshooting

1. Confirm the Service Error

1. Press Win + R

2. Type services.msc

3. Press Enter

4. Locate Infigo Sync

5. Attempt to start the service

If a logon failure appears, continue to the next step.

2. Check the Hotfolder

• Look for a .lock file.

• If one exists, confirm no job is actively processing before removing it.

• If no .lock file exists, continue troubleshooting.

3. Review the Service Log On Account

1. In services.msc, right-click Infigo Sync

2. Select Properties

3. Open the Log On tab

If editable:

• Select This account

• Enter a Windows account that:

  • Has local administrator rights

  • Has read/write access to both the hotfolder and paste/output folder

• Click Browse → Check Names

• Apply and restart the service

Tip: Run whoami in Command Prompt to confirm the current Windows username.

4. If Log On Settings Are Greyed Out

If you cannot change the service account:

• Confirm whether you are logged in as a local administrator

• If not, contact your IT administrator

In the validated case, lack of admin rights prevented the service account from being modified.

5. Verify Folder Permissions

Ask IT to confirm that the service account has:

• Full read/write access to the hotfolder

• Full read/write access to the paste/output folder

Once permissions were corrected in the referenced case, the service started successfully and files moved as expected.

Resolution Summary

The issue was caused by Windows account permissions preventing the Infigo Sync service from running correctly and accessing required folders.

After updating the PC permissions for the service account, the service started normally and file processing resumed.

When to Escalate

Contact Support if:

• The service still fails after permissions are confirmed

• Log files show repeated authentication or access errors

• Files remain stuck despite correct folder permissions

Include:

• Screenshot of the Windows service error

• Screenshot of the Log On tab

• Relevant Infigo Sync log excerpts

Hotjar is a powerful tool designed to track and analyze user behavior on your website. By capturing heatmaps, session recordings, and user feedback, Hotjar enables businesses to improve their website's usability and customer experience. This guide explains how to integrate Hotjar into your Infigo storefront to monitor user interactions effectively.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content.

2. Contents

1. Overview
2. Contents
3. Key Points and Takeaways
4. Key Settings
5. Step-by-Step Guide to Adding Hotjar
6. FAQs
7. Alternate Search Terms

3. Key Points and Takeaways

• Hotjar can be integrated into Infigo storefronts by adding its tracking script to the appropriate section in the Infigo platform.
• The integration involves no coding experience and can be completed in minutes.
• The script must be added to the PageHeadContainer section under "Infigo Settings."

4. Key Settings

PageHeadContainer

• Path: Infigo Settings → Scroll to the PageHeadContainer section.
• Explanation: This setting allows you to insert custom scripts, such as the Hotjar tracking code, into your storefront's HTML <head> section. This is crucial for tracking user behavior across the site.

5. Step-by-Step Guide to Adding Hotjar

Problem:

You need to add Hotjar to your Infigo storefront to gather user behavior insights but are unsure how to implement the tracking code.

Solution:

1. Retrieve Your Hotjar Tracking Code:
   • Log in to your Hotjar account.
   • Navigate to your dashboard and copy the tracking script provided for your project.
2. Access Infigo Settings:
   • Log in to your Infigo admin dashboard.
   • Go to Infigo Settings.
3. Locate the PageHeadContainer Section:
   • Scroll through the Infigo Settings page until you find the PageHeadContainer section.
4. Insert the Hotjar Script:

   • If there is existing content in the PageHeadContainer, ensure you do not overwrite it. Instead, add your Hotjar tracking script within the <script> tags:

     html

     <script> // Existing content remains untouched // Add your Hotjar script below [Your Hotjar Tracking Code] </script>
5. Save the Settings:
   • Once the script is added, save your changes.
6. Verify the Integration:
   • Return to Hotjar and check the installation status to ensure the script is running correctly.

6. FAQs

Q: What happens if there is already a script in the PageHeadContainer?
A: Ensure you do not delete the existing script. Add your Hotjar tracking code within the <script> tags in a new line.

Q: Do I need coding knowledge to do this?
A: No, the process involves copying and pasting a script provided by Hotjar.

Q: Can I test if Hotjar is working immediately?
A: Yes, log in to Hotjar, and it will confirm whether the script has been successfully installed.

Q: What if I cannot locate the PageHeadContainer section?
A: Contact Infigo support or refer to the Infigo Academy for further guidance.

For additional information and detailed tutorials, the Infigo Academy offers extensive resources on a wide variety of topics. Visit the Infigo Academy to search and browse our content.

When connecting your Instagram account to your website you can follow the below steps: 

1) Purchase SnapWidget Instagram account

Head over to: https://snapwidget.com/ and setup an account, then purchase a monthly plan which is suited to your needs. For most cades the basic plan will do and the rest of the guide will assume you have bought this. 

You will need to have a business / company Instagram account not a personal one.

2) Create a widget

Once you have bought and setup your SnapWidget account it's time to connect the Instagram account.

Click "Create a new widget" in the dashboard. 

From the list of Widgets click the "Instagram" pill to filter them out and then select the type of widget you would like to use. 

Follow the on screen instructions to connect your Instagram account, allow access and then return to SnapWidget. 

3) Edit and create your Widget

Once you have setup your widget you can edit it to change some settings

When you are happy with the settings and the preview looks how you want it click "Update & Get Widget" 

You will get the following popup, copy the embed code to clipboard then navigate to your Infigo website.

3) Embed on website

Navigate to the area on your website you would like to embed the widget.

Here is an example of the embed using content templates: 

Our UK customers can use Postcoder for postcode lookup services on their Storefront.

To set this up on your storefront, go to https://postcoder.com/ and click on "Start a free trial" (https://postcoder.com/sign-up) and create an account 

Once you have done this please open a ticket and send us your new credentials (username and password). We'll input the credentials for you. 

***

Once our Support Team come back to you to - please go into Customer Settings in admin and select poster as the address provider and force the postcode look up. Remember to Save. 

***

Once it is up and running on your storefront, the end user would add a new address, search the postcode and select the correct address from the list. From here the address fields would be auto populated: