Automatisation HubSpot avec n8n : gestion des clients Stripe
Ce workflow n8n a pour objectif d'automatiser la gestion des clients dans HubSpot à partir des données de Stripe. Dans un contexte où les entreprises cherchent à optimiser leur relation client et à réduire les tâches manuelles, ce workflow permet de synchroniser efficacement les informations des clients, d'éliminer les doublons et d'agréger les montants capturés. En utilisant des déclencheurs programmés, ce processus s'exécute automatiquement, garantissant que les données de vos clients sont toujours à jour. Étape 1 : Le workflow commence par un déclencheur programmé qui active le processus à intervalles réguliers. Étape 2 : Il récupère ensuite tous les frais associés aux clients via l'API Stripe, ce qui permet d'obtenir des informations détaillées sur chaque transaction. Étape 3 : Une fois les données récupérées, le workflow vérifie si le client existe déjà dans HubSpot. Si c'est le cas, il passe à l'étape suivante ; sinon, il crée ou met à jour le client dans HubSpot. Étape 4 : Les doublons sont ensuite supprimés grâce à un traitement spécifique, et les montants capturés sont agrégés pour une analyse plus facile. Les bénéfices de cette automatisation n8n sont multiples : elle réduit le risque d'erreurs humaines, améliore la qualité des données clients et permet aux équipes de se concentrer sur des tâches à plus forte valeur ajoutée. En intégrant Stripe et HubSpot, ce workflow facilite la gestion des relations clients et optimise les processus commerciaux. Tags clés : automatisation, HubSpot, Stripe.
Vue d'ensemble du workflow n8n
Schéma des nœuds et connexions de ce workflow n8n, généré à partir du JSON n8n.
Détail des nœuds du workflow n8n
Inscris-toi pour voir l'intégralité du workflow
Inscription gratuite
S'inscrire gratuitementBesoin d'aide ?{
"meta": {
"instanceId": "a2434c94d549548a685cca39cc4614698e94f527bcea84eefa363f1037ae14cd"
},
"nodes": [
{
"id": "9be821db-fbc7-4168-962f-26c8382cefbf",
"name": "If charge has customer",
"type": "n8n-nodes-base.if",
"position": [
1560,
880
],
"parameters": {
"conditions": {
"string": [
{
"value1": "={{ $json[\"customer\"] }}",
"operation": "isNotEmpty"
}
]
}
},
"typeVersion": 1
},
{
"id": "d06bae31-6856-4941-b86c-c611fc9d3da6",
"name": "Get customer",
"type": "n8n-nodes-base.stripe",
"position": [
2160,
920
],
"parameters": {
"resource": "customer",
"customerId": "={{ $json[\"customer\"] }}"
},
"credentials": {
"stripeApi": {
"id": "22",
"name": "[UPDATE ME]"
}
},
"typeVersion": 1
},
{
"id": "4e0d87bf-084f-4958-b2d3-cf7985f8c901",
"name": "On schedule",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
-400,
1400
],
"parameters": {
"rule": {
"interval": [
{}
]
}
},
"typeVersion": 1
},
{
"id": "fb620c92-5e22-4a9c-9320-847442b5e955",
"name": "Remove duplicate customers",
"type": "n8n-nodes-base.itemLists",
"position": [
1880,
920
],
"parameters": {
"compare": "selectedFields",
"options": {
"removeOtherFields": true
},
"operation": "removeDuplicates",
"fieldsToCompare": {
"fields": [
{
"fieldName": "customer"
}
]
}
},
"typeVersion": 1
},
{
"id": "3ad7554d-24b3-4ee2-8136-6a151bf06c71",
"name": "Aggregate `amount_captured`",
"type": "n8n-nodes-base.itemLists",
"position": [
1880,
540
],
"parameters": {
"options": {},
"operation": "aggregateItems",
"fieldsToAggregate": {
"fieldToAggregate": [
{
"fieldToAggregate": "amount_captured"
}
]
}
},
"typeVersion": 1
},
{
"id": "c8448580-40f2-4cf6-87ba-80903555d5a5",
"name": "Aggregate totals",
"type": "n8n-nodes-base.code",
"position": [
2820,
1360
],
"parameters": {
"jsCode": "// aggregate `amounts_captured` with the customer, taking note \n// that `aggregateAmountsPerContact` is the value in cents\nconst aggregateAmountsPerContact = new Object();\nfor (const item of $input.all()) {\n if (aggregateAmountsPerContact[item.json.email] == null) {\n aggregateAmountsPerContact[item.json.email] = 0;\n }\n aggregateAmountsPerContact[item.json.email] += item.json.amount_captured;\n}\n\n// parse the data in a way that is usable in future nodes, and\n// converts amounts from cents to dollars\nconst parsed = [];\nfor (const contact of Object.keys(aggregateAmountsPerContact)) {\n parsed.push({\n email: contact,\n amount_captured: aggregateAmountsPerContact[contact] / 100\n });\n}\n\nreturn parsed;"
},
"typeVersion": 1
},
{
"id": "dedaf89e-84d1-4964-9c87-94beea4adf26",
"name": "Create or update customer",
"type": "n8n-nodes-base.hubspot",
"position": [
3140,
1360
],
"parameters": {
"email": "={{$node[\"Aggregate totals\"].json[\"email\"]}}",
"resource": "contact",
"authentication": "oAuth2",
"additionalFields": {
"customPropertiesUi": {
"customPropertiesValues": [
{
"value": "={{$node[\"Aggregate totals\"].json[\"amount_captured\"]}}",
"property": "={{$(\"Configure\").first().json[\"contactPropertyId\"]}}"
}
]
}
}
},
"credentials": {
"hubspotOAuth2Api": {
"id": "11",
"name": "[UPDATE ME]"
}
},
"notesInFlow": false,
"typeVersion": 1
},
{
"id": "4c419e90-facc-4a64-83f2-d349264338c6",
"name": "Merge data",
"type": "n8n-nodes-base.merge",
"position": [
2520,
1360
],
"parameters": {
"mode": "combine",
"options": {},
"mergeByFields": {
"values": [
{
"field1": "id",
"field2": "customer"
}
]
}
},
"typeVersion": 2
},
{
"id": "6a21495f-e567-4b0f-b584-34306bf7fa18",
"name": "Note",
"type": "n8n-nodes-base.stickyNote",
"position": [
2460,
1160
],
"parameters": {
"width": 219.61431588546765,
"height": 378.32426823578305,
"content": "### `Merge data`\nMore specifically, we merge the Stripe data from `Get charges` and `Get customer` nodes. Only the charges with customers on them will continue."
},
"typeVersion": 1
},
{
"id": "7319c8fe-9e55-43d9-a634-3a7884268016",
"name": "Note1",
"type": "n8n-nodes-base.stickyNote",
"position": [
2760,
1160
],
"parameters": {
"width": 218.46574043407196,
"height": 379.1631729345614,
"content": "### `Aggregate totals`\nGiven the merged data, we now aggregate the amounts from charges to the customers/contacts."
},
"typeVersion": 1
},
{
"id": "c24d972b-270d-4467-9352-4ced18e377c0",
"name": "Note2",
"type": "n8n-nodes-base.stickyNote",
"position": [
1780,
400
],
"parameters": {
"width": 297.57428772569784,
"height": 325.06310253513686,
"content": "### ``Aggregate `amount_captured` ``\nThis does nothing. It is an alternative way to find the totals of every charge in existence in Stripe. Potentially useful for debugging purposes."
},
"typeVersion": 1
},
{
"id": "43da8885-fac3-4cb7-9f01-c4770cd0b030",
"name": "Get all charges",
"type": "n8n-nodes-base.stripe",
"position": [
1300,
1380
],
"parameters": {
"resource": "charge",
"operation": "getAll",
"returnAll": true
},
"credentials": {
"stripeApi": {
"id": "22",
"name": "[UPDATE ME]"
}
},
"typeVersion": 1
},
{
"id": "abfe75f5-c36f-4904-a703-cb8d1d83b686",
"name": "Note3",
"type": "n8n-nodes-base.stickyNote",
"position": [
-960,
1220
],
"parameters": {
"width": 504,
"height": 510.0404950205649,
"content": "## Sync Stripe charges to HubSpot contacts\nThis workflow pushes Stripe charges to HubSpot contacts. It uses the Stripe API to get all charges and the HubSpot API to update the contacts. The workflow will create a new HubSpot property to store the total amount charged. If the property already exists, it will update the property.\n\n### How it works\n1. On a schedule, the first Stripe node gets all charges. The default schedule is once a day at midnight.\n2. Once the charges are returned, the second Stripe node gets extra customer information.\n3. Once the customer information is returned, `Merge data` node will merge the customer information with the charges so that the next node `Aggregate totals` can calculate the total amount charged per contact.\n4. Once we have the total amount charged per contact, the `Create or update customer` node will create a new HubSpot property to store the total amount charged. If the property already exists, it will update the property.\n\n\n\nWorkflow written by [David Sha](https://davidsha.me)."
},
"typeVersion": 1
},
{
"id": "67e44a47-18db-48a3-a08e-c4f2afb13a30",
"name": "Note4",
"type": "n8n-nodes-base.stickyNote",
"position": [
1780,
760
],
"parameters": {
"width": 298.2919335506821,
"height": 339.6783118583311,
"content": "### `Remove duplicate customers`\nEnsures that we do not poll Stripe too many times unnecessarily. If multiple charges have the same customer, we ensure that we do not ask for the same information again."
},
"typeVersion": 1
},
{
"id": "02d46492-f3ba-47fe-ba88-f2baad30fc73",
"name": "Get HubSpot field",
"type": "n8n-nodes-base.httpRequest",
"position": [
580,
1540
],
"parameters": {
"url": "=https://api.hubapi.com/crm/v3/properties/contact/{{$(\"Configure\").first().json[\"contactPropertyId\"]}}",
"options": {},
"authentication": "predefinedCredentialType",
"nodeCredentialType": "hubspotOAuth2Api"
},
"credentials": {
"hubspotOAuth2Api": {
"id": "11",
"name": "[UPDATE ME]"
}
},
"typeVersion": 3,
"continueOnFail": true
},
{
"id": "827882c4-5d3f-4cc6-b876-ae575a9a1b36",
"name": "Create field in HubSpot",
"type": "n8n-nodes-base.httpRequest",
"position": [
980,
1660
],
"parameters": {
"url": "https://api.hubapi.com/crm/v3/properties/contact",
"method": "POST",
"options": {
"response": {
"response": {
"neverError": true
}
}
},
"sendBody": true,
"authentication": "predefinedCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "name",
"value": "={{$(\"Configure\").first().json[\"contactPropertyId\"]}}"
},
{
"name": "label",
"value": "={{$(\"Configure\").first().json[\"contactPropertyLabelName\"]}}"
},
{
"name": "type",
"value": "number"
},
{
"name": "fieldType",
"value": "number"
},
{
"name": "groupName",
"value": "contactinformation"
},
{
"name": "formField",
"value": "false"
},
{
"name": "description",
"value": "=The total spend determined by the charges in Stripe. This is a field required for \"{{$workflow.name}}\" n8n workflow."
}
]
},
"nodeCredentialType": "hubspotOAuth2Api"
},
"credentials": {
"hubspotOAuth2Api": {
"id": "11",
"name": "[UPDATE ME]"
}
},
"typeVersion": 3
},
{
"id": "b4092718-bf35-49b5-aefa-b9900596fcb5",
"name": "Note5",
"type": "n8n-nodes-base.stickyNote",
"position": [
500,
1480
],
"parameters": {
"width": 656.5118956254801,
"height": 367.20468504951214,
"content": "### Create HubSpot field if required\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n_These nodes create a HubSpot field if required.\nIt makes the contact field that this workflow uses \nto store the Stripe information. To disable this \nsection, in `Configure` node change `checkFields`\nto false._"
},
"typeVersion": 1
},
{
"id": "6d74e2e3-bd95-4ccb-89c0-3d6f8f1e01f9",
"name": "Configure",
"type": "n8n-nodes-base.set",
"position": [
-80,
1400
],
"parameters": {
"values": {
"string": [
{
"name": "contactPropertyId",
"value": "stripe___total_spend"
},
{
"name": "contactPropertyLabelName",
"value": "Stripe - Total Spend"
}
],
"boolean": [
{
"name": "checkFields",
"value": true
}
]
},
"options": {}
},
"typeVersion": 1
},
{
"id": "8a8262bc-0742-4529-9f10-328c338854fe",
"name": "Note6",
"type": "n8n-nodes-base.stickyNote",
"position": [
-200,
1340
],
"parameters": {
"width": 338.8262165118159,
"height": 505.43603897947025,
"content": "### Configuration\n\n\n\n\n\n\n\n\n\n\n\n\nBy default, this does not need to be updated. \n\n__`contactPropertyId` (required)__: Only change if the specific HubSpot field ID has been taken.\n\n__`contactPropertyLabelName` (required)__: Change if you would like a different display name.\n\n__`checkFields` (required)__: Turn to false if you would like to optimise this workflow, provided this workflow has run once before with this configurable enabled. This will disable the section of this workflow which deals with creating a HubSpot field."
},
"typeVersion": 1
},
{
"id": "fc640a31-2050-4276-a1f7-8154f61d2729",
"name": "Note7",
"type": "n8n-nodes-base.stickyNote",
"position": [
3080,
1160
],
"parameters": {
"width": 219.86482940052417,
"height": 377.58888520886353,
"content": "### `Create or update customer`\nBy default, the only field updated is \"Stripe - Total Spend\". The contact is identified by its email."
},
"typeVersion": 1
},
{
"id": "c91295e6-0306-4f3d-adcf-923fbef1c173",
"name": "Skip field checking",
"type": "n8n-nodes-base.if",
"position": [
240,
1400
],
"parameters": {
"conditions": {
"boolean": [
{
"value1": "={{$node[\"Configure\"].json[\"checkFields\"]}}",
"value2": "={{false}}"
}
]
}
},
"typeVersion": 1
},
{
"id": "8f8b5a15-4895-4c5a-b8ba-8592dd754aca",
"name": "Do nothing",
"type": "n8n-nodes-base.noOp",
"position": [
1880,
1240
],
"parameters": {},
"typeVersion": 1
},
{
"id": "b953e439-955c-4046-9000-32cbb3577c27",
"name": "Note8",
"type": "n8n-nodes-base.stickyNote",
"position": [
1780,
1140
],
"parameters": {
"width": 298.2919335506821,
"height": 247.94509463108915,
"content": "### `Do nothing`\nThis is useful to know what Stripe charges had no customer assigned."
},
"typeVersion": 1
},
{
"id": "ec2116e5-2a4a-4edf-a816-b15c349f23e0",
"name": "If field exists",
"type": "n8n-nodes-base.if",
"position": [
780,
1540
],
"parameters": {
"conditions": {
"number": [
{
"value1": "={{ $json[\"error\"][\"httpCode\"] }}",
"value2": "404",
"operation": "notEqual"
}
]
}
},
"typeVersion": 1
}
],
"connections": {
"Configure": {
"main": [
[
{
"node": "Skip field checking",
"type": "main",
"index": 0
}
]
]
},
"Merge data": {
"main": [
[
{
"node": "Aggregate totals",
"type": "main",
"index": 0
}
]
]
},
"On schedule": {
"main": [
[
{
"node": "Configure",
"type": "main",
"index": 0
}
]
]
},
"Get customer": {
"main": [
[
{
"node": "Merge data",
"type": "main",
"index": 0
}
]
]
},
"Get all charges": {
"main": [
[
{
"node": "If charge has customer",
"type": "main",
"index": 0
},
{
"node": "Merge data",
"type": "main",
"index": 1
}
]
]
},
"If field exists": {
"main": [
[
{
"node": "Get all charges",
"type": "main",
"index": 0
}
],
[
{
"node": "Create field in HubSpot",
"type": "main",
"index": 0
}
]
]
},
"Aggregate totals": {
"main": [
[
{
"node": "Create or update customer",
"type": "main",
"index": 0
}
]
]
},
"Get HubSpot field": {
"main": [
[
{
"node": "If field exists",
"type": "main",
"index": 0
}
]
]
},
"Skip field checking": {
"main": [
[
{
"node": "Get all charges",
"type": "main",
"index": 0
}
],
[
{
"node": "Get HubSpot field",
"type": "main",
"index": 0
}
]
]
},
"If charge has customer": {
"main": [
[
{
"node": "Remove duplicate customers",
"type": "main",
"index": 0
},
{
"node": "Aggregate `amount_captured`",
"type": "main",
"index": 0
}
],
[
{
"node": "Do nothing",
"type": "main",
"index": 0
}
]
]
},
"Create field in HubSpot": {
"main": [
[
{
"node": "Get all charges",
"type": "main",
"index": 0
}
]
]
},
"Remove duplicate customers": {
"main": [
[
{
"node": "Get customer",
"type": "main",
"index": 0
}
]
]
}
}
}Pour qui est ce workflow ?
Ce workflow s'adresse aux entreprises de taille moyenne à grande qui utilisent Stripe pour le traitement des paiements et HubSpot pour la gestion de la relation client. Les équipes marketing et commerciales, ainsi que les responsables de la gestion des données, trouveront cet outil particulièrement utile pour automatiser leurs processus et améliorer l'efficacité opérationnelle.
Problème résolu
Ce workflow résout le problème de la gestion manuelle des clients entre Stripe et HubSpot, qui peut être source d'erreurs et de pertes de temps. En automatisant la synchronisation des données, il élimine les doublons et garantit que les informations clients sont toujours à jour. Les utilisateurs bénéficient ainsi d'une vue d'ensemble précise de leur base de clients, ce qui facilite la prise de décision et améliore l'engagement client.
Étapes du workflow
Étape 1 : Le workflow est déclenché selon un calendrier prédéfini. Étape 2 : Il récupère tous les frais associés aux clients via Stripe. Étape 3 : Une vérification est effectuée pour déterminer si le client existe déjà dans HubSpot. Étape 4 : Si le client existe, il est mis à jour ; sinon, il est créé. Étape 5 : Les doublons sont supprimés pour assurer l'intégrité des données. Étape 6 : Les montants capturés sont agrégés pour une analyse approfondie. Étape 7 : Les champs nécessaires dans HubSpot sont créés ou mis à jour en fonction des données récupérées.
Guide de personnalisation du workflow n8n
Pour personnaliser ce workflow, commencez par ajuster le déclencheur programmé selon vos besoins spécifiques, en modifiant la fréquence d'exécution. Ensuite, vous pouvez adapter les paramètres de l'API Stripe pour cibler des informations spécifiques sur les frais. Pour HubSpot, assurez-vous que les champs créés correspondent à votre structure de données. Vous pouvez également intégrer d'autres outils ou services en ajoutant des noeuds supplémentaires selon vos besoins. Enfin, il est conseillé de sécuriser le flux en vérifiant les permissions d'accès aux API utilisées.