Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Email-Driven HubSpot Contact Management

Email-Driven HubSpot Contact Management is a 9-node automation blueprint connecting HubSpot, OpenAI, Email. Inspect its trigger, execution graph, branches, and implementation requirements.

HubSpotOpenAIEmail

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.

9

Nodes

9

Links

1

Run groups

Connected tools

3 integrations

  • HubSpot
  • OpenAI
  • Email

Canvas controls

Fit wide systems, then zoom into any run group.

Email-Driven HubSpot Contact Management execution lanes1 run groups containing 9 workflow nodes and 9 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.When an email is received. integration node, emailReadImap. 0 incoming and 1 outgoing connections.STARTWhen an email is receivedINTEGRATIONEMAILREADIMAP0 IN / 1 OUTParse the mail with AI. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 02Parse the mail with AIAICHAINLLM3 IN / 1 OUTSearch for the contact via email. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 03Search for the contact vi…HUBSPOTHUBSPOT1 IN / 1 OUTcontact exists?. decision node, if. 1 incoming and 2 outgoing connections.STEP 04contact exists?DECISIONIF1 IN / 2 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Edit FieldsTRANSFORMSET1 IN / 1 OUTCreates contact. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 05Creates contactHUBSPOTHUBSPOT1 IN / 1 OUTCreates an email engagement. HubSpot node, hubspot. 2 incoming and 0 outgoing connections.OUTCOMECreates an email engagementHUBSPOTHUBSPOT2 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTSet the output Json. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Set the output JsonAIOUTPUTPARSERSTRUCTURED0 IN / 1 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.9 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

When an email is received

7 Execution Links2 Support Dependencies

  1. Start

    When an email is received

    Integration

  2. Step 2

    Parse the mail with AI

    AI reasoning

  3. Step 3

    Search for the contact via email

    Integration

  4. Step 4

    contact exists?

    Decision

  5. Step 5

    Edit Fields

    Transform

    Creates contact

    Integration

  6. Outcome

    Creates an email engagement

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

2 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Set the output Json

    AI reasoning dependency

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