Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

HubSpot Contact Enrichment Workflow

HubSpot Contact Enrichment Workflow is a 7-node automation blueprint connecting HubSpot, ExactBuyer. Inspect its trigger, execution graph, branches, and implementation requirements.

HubSpotExactBuyer

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

7

Nodes

6

Links

1

Run groups

Connected tools

2 integrations

  • HubSpot
  • ExactBuyer

Canvas controls

Fit wide systems, then zoom into any run group.

HubSpot Contact Enrichment Workflow execution lanes1 run groups containing 7 workflow nodes and 6 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.On contact created. HubSpot node, hubspotTrigger. 0 incoming and 1 outgoing connections.STARTOn contact createdHUBSPOTHUBSPOTTRIGGER0 IN / 1 OUTGet HubSpot contact. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 02Get HubSpot contactHUBSPOTHUBSPOT1 IN / 1 OUTSet keys. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set keysTRANSFORMSET1 IN / 1 OUTif found email. decision node, if. 1 incoming and 1 outgoing connections.STEP 04if found emailDECISIONIF1 IN / 1 OUTEnrich user from ExactBuyer. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 05Enrich user from ExactBuyerINTEGRATIONHTTPREQUEST1 IN / 2 OUTUpdate contact from Hubspot. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.OUTCOMEUpdate contact from HubspotHUBSPOTHUBSPOT1 IN / 0 OUTCould not find user. integration node, noOp. 1 incoming and 0 outgoing connections.OUTCOMECould not find userINTEGRATIONNOOP1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.7 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

On contact created

6 Execution Links

  1. Start

    On contact created

    Trigger

  2. Step 2

    Get HubSpot contact

    Integration

  3. Step 3

    Set keys

    Transform

  4. Step 4

    if found email

    Decision

  5. Step 5

    Enrich user from ExactBuyer

    Integration

  6. Outcome

    Update contact from Hubspot

    Integration

    Could not find user

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas