Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Daily HubSpot Outreach Email Automation

Daily HubSpot Outreach Email Automation is a 5-node automation blueprint connecting HubSpot, Gmail. Inspect its trigger, execution graph, branches, and implementation requirements.

HubSpotGmail

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.

5

Nodes

4

Links

1

Run groups

Connected tools

2 integrations

  • HubSpot
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Daily HubSpot Outreach Email Automation execution lanes1 run groups containing 5 workflow nodes and 4 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.Every day at 9 am. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTEvery day at 9 amTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet uncontacted HubSpot contacts. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 02Get uncontacted HubSpot c…HUBSPOTHUBSPOT1 IN / 1 OUTSet keys. transform node, set. 1 incoming and 2 outgoing connections.STEP 03Set keysTRANSFORMSET1 IN / 2 OUTSend outreach email. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend outreach emailGMAILGMAIL1 IN / 0 OUTRecord engagement in HubSpot. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.OUTCOMERecord engagement in HubS…HUBSPOTHUBSPOT1 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.5 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

Every day at 9 am

4 Execution Links

  1. Start

    Every day at 9 am

    Trigger

  2. Step 2

    Get uncontacted HubSpot contacts

    Integration

  3. Step 3

    Set keys

    Transform

  4. Outcome

    Send outreach email

    Integration

    Record engagement in HubSpot

    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