n8n Shopify to HubSpot kit

n8n Shopify → HubSpot workflows

Six workflow files for n8n that send Shopify customers and paid orders to HubSpot: contact upsert, deal upsert with association, segmentation read from Shopify’s GraphQL Admin API, and an email when one of them fails. No Code node, no secret in the files.

This site is the developer reference: how each workflow is wired, what to replace before the first run, and how to replay signed webhooks against your own instance. The reasoning behind the choices, the FAQ and the longer discussion of limits are in the full guide on cinfolog.com (in French).

Quick start

Create the five credentials first, with exactly the names and types listed on the setup page. On import, n8n links each node to the credential of the same name and type. If you import first, select the credential in every node, or delete the imported copies and import again, before publishing; otherwise every request, signed or not, gets a 400.

Then import. Self-hosted n8n, from a clone of the repository:

git clone https://github.com/cinfolog/n8n-shopify-hubspot-kit.git
cd n8n-shopify-hubspot-kit
n8n import:workflow --input=workflows/04-alerte-echec-workflow.json
n8n import:workflow --input=workflows/00-proprietes-hubspot.json
n8n import:workflow --input=workflows/01-client-shopify-vers-contact-hubspot.json
n8n import:workflow --input=workflows/02-commande-payee-vers-transaction-hubspot.json
n8n import:workflow --input=workflows/03-segmentation-client-shopify-hubspot.json

With Docker, copy the files into the container and run the CLI as the node user, as n8n’s documentation does:

docker cp workflows <container>:/tmp/kit-workflows
docker exec -u node <container> n8n import:workflow --input=/tmp/kit-workflows/01-client-shopify-vers-contact-hubspot.json

On n8n Cloud, use Import from File in the workflow menu, one file at a time. Imported workflows are deactivated. Import 03b instead of 03 only if you still have a fixed Admin API token: both listen on the same path.

The whole order: create credentials, import, replace the placeholders, run workflow 00 once, publish 04, set 04 as the Error workflow of 01, 02 and 03 (or 03b), publish those, create the Shopify webhooks, replay. The setup page has the detail; the testing page has the replay script.

What is in the repository

FileTriggerNodesCredentials
00-proprietes-hubspot.jsonManual, once3HubSpot App Token
01-client-shopify-vers-contact-hubspot.jsonWebhook customers/create and customers/update, path shopify-client11Crypto, HubSpot App Token
02-commande-payee-vers-transaction-hubspot.jsonWebhook orders/paid, path shopify-commande-payee16Crypto, HubSpot App Token
03-segmentation-client-shopify-hubspot.jsonWebhook orders/paid, path shopify-segmentation; token requested on every run16Crypto, HubSpot App Token, Custom Auth
03b-segmentation-client-jeton-fixe.jsonSame webhook path as 03; fixed Admin API token. Use 03 or 03b15Crypto, HubSpot App Token, Header Auth
04-alerte-echec-workflow.jsonError Trigger (set as the Error workflow of 01, 02 and 03 or 03b)2SMTP

Node counts exclude sticky notes. Each workflow carries a “read first” sticky note in French then English.

What the workflows do that a bare template does not

The architecture page walks through each of these, node by node, with the endpoints called.

Tested with, and not tested with

Last checked: November 2026.

A note on language

Node names inside the JSON files are in French (“Calculer la signature HMAC”). Sticky notes are French then English. The architecture page gives the English name of every node, so you can read the French canvas with this page open next to it.

Who maintains this

Thomas Cadalen, based in the Bordeaux area, France. Adapting these workflows to other fields, pipelines or volumes is the kind of work he does as a freelance n8n integrator (page in French). Bug reports and fixes go through GitHub issues.