On User created in HubSpot
Configured with HTTP Request, Hubspot, Hubspot Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Web / API
- Transform
- Integration
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Could not find user | Routing | No Op | See node parameters |
| Enrich user from ExactBuyer | Web / API | HTTP Request | See node parameters |
| Set keys | Transform | Edit Fields | See node parameters |
| if found email | Routing | If | See node parameters |
| Update contact from Hubspot | Integration | Hubspot | See node parameters |
| Get HubSpot contact | Integration | Hubspot | get |
| On contact created | Trigger | Hubspot Trigger | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuthhubspotDeveloperApihubspotOAuth2Api
Workflow notes
On User created in HubSpot
On User created in HubSpot
- Setup Oauth2 creds using n8n docs https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger
Be careful with scopes. Scopes must be exactly as defined in the docs
Enrich with data from ExactBuyer
Enrich with data from ExactBuyer
- Add api key from Exact buyer
- Use email as identifier to match user
Use API Guide here https://docs.exactbuyer.com/contact-enrichment/enrichment
Get user in Hubspot
Get user in Hubspot
- Setup Oauth2 creds using n8n docs https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/
Be careful with scopes. Scopes must be exactly as defined in the docs
Will need to be a different cred from the trigger one
On User created in HubSpot
On User created in HubSpot
Purpose and structure
This folder contains the On User created in HubSpot workflow. Its executable nodes use httpRequest, hubspot, hubspotTrigger, if, noOp, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On contact created
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Noop/0416_Noop_HubSpot_Create_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Enrich new Hubspot contacts with contact and company data from ExactBuyer
- Update user in Hubspot