Show details for Connect your storefront to HubSpot

Connect your storefront to HubSpot

Send customers, departments and orders from your storefront to HubSpot automatically, as Contacts, Companies and Deals.

Connect your storefront to HubSpot

Send customers, departments and orders from your storefront to HubSpot automatically, as Contacts, Companies and Deals.

Guide10 min readVideo12-step guideUpdated 4 Nov 2026

Overview

Connect: HubSpotConnect: HubSpot is a Connect plugin that sends your storefront's data to HubSpot CRM automatically. links your storefront to your HubSpot account. Customers, departments and orders are sent to HubSpot as they happen, so nobody has to copy them across by hand.

What it does

  • Customers become Contacts - a customer who registers is sent with their email, name, phone, company and address. If HubSpot already has a contact with the same email, that contact is reused and its details are not changed.
  • Departments become Companies - a new department is sent as a Company when its first customer is sent, and its customers' Contacts are linked to it. You can switch this off to send Contacts only.
  • Orders become Deals (optional) - with deals on, every order placed on your storefront creates a Deal on the customer's Contact, with the order total as the amount, in the pipeline and stage you choose.
  • Your own fields (optional, advanced) - if your storefront has the MegaScripts module, a MegaScriptA MegaScript is a custom script built in Infigo's Connect: Scripting workflow engine that runs on storefront events (such as Place Order) to drive advanced, bespoke logic — for example pushing order... can replace the standard fields for Contacts, Companies or Deals with the HubSpot properties you need. MegaScripts are an additional module that not every storefront has, and nothing else here needs one, so skip this if you do not have it. A MegaScript only appears in the list if Trigger on Event is switched on for it, and the property names it returns must already exist in HubSpot. If the script is switched off, fails or returns nothing, the standard fields are sent instead. New to MegaScripts? See the MegaScripts documentation and, for a worked example of setting one up, the form-to-order example in the Academy's MegaEdit Problem Solvers: MegaScripts page.

How it works

  • One way - data goes from your storefront to HubSpot. Nothing in your storefront is changed from HubSpot.
  • In the background - records are sent after the registration or order is complete, so nobody waits for HubSpot and a record can arrive a little after the event, not at the same moment. If HubSpot cannot be reached, registrations and orders still go through and the problem is logged.
  • An access token - you connect with an access token from your HubSpot account that can read and write contacts and write companies and deals. The Step-by-step tab lists the four permissions it needs.

Good to know

  • Records are created once. Later changes to a customer, department or order are not sent, and no records are deleted in HubSpot. Re-sending an order does not create a second Deal.
  • Existing records are not sent on their own. Only departments created while Create companies is ticked get a Company; departments created before that, or before you connected, do not, and ticking it later does not add them. New customers in those departments are sent as Contacts without a Company. Customers who existed before are not sent when you connect, but with Create deals on, their next order creates their Contact.
  • Products and order lines are not sent. A Deal carries the order total, not the individual items.
  • Deals link to the Contact. A Deal is associated with the customer's Contact, not directly with the Company.
  • Moving a customer to another department links their Contact to the new department's Company, if that department has one in HubSpot, and removes the link the plugin made to the old Company. Links to other Companies made by hand in HubSpot are kept.
  • Customers without an email address are not sent. Customers whose registration needs approval, or whom an administrator creates without ticking Notify MISManagement Information System, which is a computer-based system that provides managers with tools to organize, evaluate, and efficiently manage information within an organization, aiding in... about customer registration, are not sent as Contacts when they register or when they are approved; with Create deals on, their first order creates the Contact.
  • Already sending orders to HubSpot another way? If your storefront uses an earlier HubSpot MegaScript, switch that MegaScript off when you turn on Create deals, or every order will create two Deals.

Before you begin

  • Connect: HubSpot must be installed on your storefront. In Configuration > Plugins > Connect Plugins it is on the Installed Plugins tab; if it is on the Unlock More Powerful Integrations tab instead, use its Purchase button to enquire.
  • You need an access token from your HubSpot account, with the permissions listed on the Step-by-step tab.
  • If you send orders as Deals, you need the IDs HubSpot uses for the pipeline and stage you want.

Step-by-step

  1. Open Connect Plugins

    Go to Configuration > Plugins > Connect Plugins. Connect: HubSpot is listed on the Installed Plugins tab with two buttons: Configure opens its settings, and Check Connection tests the link to HubSpot. If it is not installed on your storefront yet, it appears on the Unlock More Powerful Integrations tab instead, with a Purchase button you can use to enquire about it.

    Connect: HubSpot - Configure / Check Connection

    Connect: HubSpot - Configure / Check Connection
  2. Turn it on for your storefront

    Go to Configuration > Settings > Integrations > Connect Settings. Under Enabled Connect PluginInfigo's Connect Plugins facilitate seamless integration with third-party Management Information Systems (MIS) and other production platforms, allowing order data and artwork to flow between Infigo..., tick Connect: HubSpot and click Save. Back on Connect Plugins it now shows Enabled.

    Enabled Connect Plugin: Connect: HubSpot

    Enabled Connect Plugin: Connect: HubSpot
  3. Get an access token from HubSpot

    Your storefront connects to HubSpot with an access token from your HubSpot account. Create one in HubSpot that is allowed to read and write contacts, write companies and write deals; HubSpot's own documentation explains how to create a token. The four permissions are named crm.objects.contacts.read, crm.objects.contacts.write, crm.objects.companies.write and crm.objects.deals.write. Copy the token and treat it like a password.

    The four permissions the token needs

    The four permissions the token needs
  4. Paste the access token

    On Connect Plugins, click Configure next to Connect: HubSpot to open Connect: HubSpot Settings. Under HubSpot connection, paste the token into Access token. Leave APIA programmatic interface that lets one system talk to another using structured requests and responses. URL as it is.

    Access token: paste your HubSpot token

    Access token: paste your HubSpot token
  5. Choose whether departments become companies

    Create companies is ticked by default. Each department created from now on then gets a HubSpot Company, made when the first customer in it is sent, and that department's Contacts are linked to it. Only departments created while Create companies is ticked get a Company: departments created before that, or before you connected, do not, and ticking it later does not add them. A new customer in such a department is sent as a Contact without a Company. Untick it to send Contacts only. Leave Association category and Association type id as they are.

    Create companies (on by default)

    Create companies (on by default)
  6. Leave field mapping on None (optional, advanced)

    Field mapping is optional and more advanced, and most storefronts leave it on None. With None, the standard fields are sent: email, name, phone, company and address for a Contact; the department name for a Company; and name, amount, pipeline and stage for a Deal. To send different fields, you can choose a MegaScript for each of Customer to Contact, Department to Company and Order to Deal. MegaScripts are an additional module that not every storefront has, so if yours does not, leave this on None: nothing else in this guide needs it. A MegaScript replaces the standard fields for that record type entirely, and More Information shows an example. It is only listed if Trigger on Event is switched on for it. The property names it returns must already exist in HubSpot, or HubSpot rejects the record, and a rejected record is not re-sent with the standard fields. If the script is switched off, fails or returns nothing, the standard fields are sent instead. New to MegaScripts? See the Academy's MegaScripts documentation and, for a worked example of setting one up, the form-to-order example in the Academy's MegaEdit Problem Solvers: MegaScripts page.

    Optional: replace the default fields

    Optional: replace the default fields
  7. Optional: turn on deals for placed orders

    Deals are off by default. Tick Create deals to create a HubSpot Deal for every order placed on your storefront. Enter Deal pipeline and Deal stage as the IDs HubSpot uses for them, not their display names. The defaults are default and closedwon; HubSpot's documentation explains where to find the IDs for your own pipelines. The stage must belong to the pipeline, and both are required while deals are on. Leave the deal association settings as they are. If your storefront already sends orders to HubSpot with an earlier MegaScript, switch that MegaScript off first, or each order will create two Deals.

    Create deals + pipeline and stage ids

    Create deals + pipeline and stage ids
  8. Save and check the connection

    Click Save, then go back to Connect Plugins and click Check Connection next to Connect: HubSpot. Your storefront makes a test call to HubSpot with your token. If it works, you see Connect Connection was successful for plugin: Mis.HubSpot. The check only confirms the token can read contacts. It does not test creating contacts, companies or deals, so make sure the token has all four permissions. If the check fails, see step 12.

    Check Connection

    Check Connection
  9. Know what is sent, and when

    From now on, a new department becomes a Company (created when its first customer is sent), a customer who registers becomes a Contact, and, with deals on, each placed order becomes a Deal. If new registrations need approval, or an administrator creates a customer without ticking Notify MIS about customer registration, no Contact is created when they register or are approved; with deals on, that customer's first order creates it. Contacts are matched on email first: if HubSpot already has a contact with that email, it is reused and its details are not changed. Everything is sent in the background, so customers never wait for HubSpot, and a record can arrive a little after the event rather than at the same moment. If HubSpot cannot be reached, registrations and orders still go through and the problem is logged.

    What is sent, and when

    What is sent, and when
  10. See a new customer arrive as a Contact and Company

    To test, create a new department in Customers > Departments and register a new customer into it: a department or customer that existed before you connected is not sent. When a customer registers into a department, HubSpot gets a Contact with the email, name, phone, company and address from the customer's account, linked to the department's Company if it has one. Blank fields are left out. The Company is made when the department's first customer is sent. Departments are normally created by administrators. If your storefront also lets customers create a new department when they register (Allow customers to create a new department in Configuration > Settings > Customer Settings, with Department selection enabled on) or from their account page (which also needs Allow for customers to set their own departments), that new department gets a Company in the same way.

    Each new department -> a HubSpot Company

    Each new department -> a HubSpot Company

    Example: the Contact and Company

    Example: the Contact and Company
  11. See a placed order arrive as a Deal

    With Create deals on, each placed order creates one Deal, linked to the customer's Contact. The Deal is named after the billing company, else the customer's company, else Order and the order ID. Its amount is the order total, and its pipeline and stage come from your settings. If the customer has no Contact yet, for example because they registered before you connected, the Contact is created from the order's billing details first.

    Example: the Deal

    Example: the Deal
  12. If the check fails, read HubSpot's reason

    When Check Connection fails, the message includes HubSpot's own reason. INVALID_AUTHENTICATION means HubSpot did not accept the token: it is missing or not valid. Paste a fresh token, save and check again. Ignore the generic first part of the message: HubSpot's reason follows it.

    HubSpot's own reason is shown here

    HubSpot's own reason is shown here

Video transcript

Overview video

0:00 Connect your storefront to HubSpot

0:02 Connect HubSpot sends customers, departments and orders from your storefront to your HubSpot account, so they're in your CRM without anyone re-keying them.

0:12 A new department becomes a HubSpot Company. A customer who registers becomes a Contact, matched on email first. And, if you turn deals on, every placed order becomes a Deal. It's one way, from your storefront to HubSpot, and it runs in the background.

0:29 Here's what HubSpot receives when the first customer in a new department registers. A Company with the department name, and a Contact with their email, name, phone and address, linked to it.

0:41 With deals on, the order arrives as a Deal on that Contact. It's named after the company, its amount is the order total, and it goes into the pipeline and stage you choose.

0:52 You connect with an access token from your HubSpot account, pasted into the plugin's settings in your admin area.

0:59 Records are created once, and later changes aren't sent. The step-by-step guide on this page shows the full set-up.

Step-by-step video

0:00 Set up Connect HubSpot

0:02 In this tutorial we'll connect your storefront to HubSpot, and look at what arrives there. Before you start, Connect HubSpot needs to be installed on your storefront.

0:12 Go to Configuration, Plugins, then Connect Plugins. Connect HubSpot is listed here, with a Configure button and a Check Connection button.

0:23 Next, in Configuration, Settings, Integrations, Connect Settings, tick Connect HubSpot under Enabled Connect Plugin, and save.

0:33 Now, in HubSpot, create an access token that can read and write contacts, and write companies and deals. HubSpot's own documentation explains how. Copy the token, and treat it like a password.

0:47 Back in Connect Plugins, click Configure next to Connect HubSpot. Paste the token into Access token. Leave the API URL as it is.

0:57 Create companies is on by default, so each department created from now on becomes a HubSpot Company. Untick it if you only want Contacts. The association settings can stay as they are.

1:10 Field mapping is optional, and more advanced. Leave it on None to send the standard fields. A MegaScript can replace them, but MegaScripts are an additional module that not every storefront has. If you don't have it, you can leave this on None. The Academy has MegaScript documentation if you'd like to learn more.

1:30 Deals are optional. To send orders, tick Create deals. Then enter the pipeline and stage as the IDs HubSpot uses for them, not their display names. HubSpot's documentation explains where to find them.

1:44 Save. Then, on Connect Plugins, click Check Connection. A green message confirms your storefront reached HubSpot.

1:53 From now on, new departments become Companies, customers who register become Contacts, and, with deals on, placed orders become Deals. It all happens in the background, so nobody waits for HubSpot.

2:07 Your departments are in Customers, Departments. Each new one becomes a HubSpot Company, together with its first customer.

2:15 When a customer registers into a new department, HubSpot gets the Company, and a Contact linked to it, with their email, name, phone and address. Blank fields are left out. Departments are normally created by administrators, though your storefront can let customers create their own when they register. To test it, use a new department and a new customer: ones that existed before you connected aren't sent.

2:41 And each placed order becomes a Deal on that Contact, with the order total as its amount.

2:48 If the check fails, the message includes HubSpot's own reason. Invalid authentication means HubSpot didn't accept the token. Paste a fresh one, and check again.

2:58 That's it. New customers, departments and orders now arrive in HubSpot. Remember, records are created once, and later changes aren't sent.

Troubleshooting

Troubleshooting

  • Check Connection fails with INVALID_AUTHENTICATION - HubSpot did not accept the token: it is missing or not valid. Paste a fresh token, save and check again.
  • Contacts arrive but Deals do not - make sure Create deals is ticked, that the token has the crm.objects.deals.write permission (Check Connection does not test it), and that the pipeline and stage IDs are the ones HubSpot uses (the stage must belong to the pipeline).
  • A Contact or Company did not arrive first time - if HubSpot could not create it, the attempt is repeated each time that customer's details are saved, up to five attempts in all. With Create deals on, each new order from that customer also tries again to create a missing Contact. A Deal is not repeated automatically: fix the cause, then use the Re-trigger Connect: HubSpot button on the order line in the order's details in Shared Print Operations. It will not create a second Deal. The button only appears while Create deals is on and a token is saved. If it is greyed out, hover over it to see why.

Search terms

Alternate Search Phrases
HubSpotHub SpotCRMConnect: HubSpotcontactsdeals
Guide | Connect your storefront to HubSpotLast updated: 4 Nov 2026
Incomplete
Start the conversation! Have a question? Tutorial out of date? Let us know HERE!