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

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