Skip to Workflow Atlas
ETL PipelineAI systemIntermediate

Automated Sales Persona & Email Drafting

Automated Sales Persona & Email Drafting is a 11-node automation blueprint connecting Google Gemini, Gmail, HubSpot. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

11

Nodes

11

Links

1

Run groups

Connected tools

3 integrations

  • Google AI
  • Gmail
  • HubSpot

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Sales Persona & Email Drafting execution lanes1 run groups containing 11 workflow nodes and 11 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 clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTGet Contacts. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 02Get ContactsHUBSPOTHUBSPOT1 IN / 1 OUTFor Each Contact. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 03For Each ContactINTEGRATIONSPLITINBATCHES2 IN / 1 OUTContact Ref. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 04Contact RefINTEGRATIONNOOP1 IN / 1 OUTVariables. transform node, set. 1 incoming and 1 outgoing connections.STEP 05VariablesTRANSFORMSET1 IN / 1 OUTGet All Customer's Correspondence. Gmail node, gmail. 1 incoming and 1 outgoing connections.STEP 06Get All Customer's Corres…GMAILGMAIL1 IN / 1 OUTAnalyse and Build Persona. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 07Analyse and Build PersonaAIINFORMATIONEXTRACTOR2 IN / 1 OUTGenerate Sales Email. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 08Generate Sales EmailAIINFORMATIONEXTRACTOR2 IN / 1 OUTCreate Draft Email For Review. Gmail node, gmail. 1 incoming and 1 outgoing connections.OUTCOMECreate Draft Email For Re…GMAILGMAIL1 IN / 1 OUTGoogle Gemini Chat Model. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat ModelGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 OUTGoogle Gemini Chat Model1. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat Model1GOOGLE AILMCHATGOOGLEGEMINI0 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.11 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 clicking ‘Test workflow’

9 Execution Links2 Support Dependencies
  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Get Contacts

    Integration

  3. Step 3

    For Each Contact

    Integration

  4. Step 4

    Contact Ref

    Integration

  5. Step 5

    Variables

    Transform

  6. Step 6

    Get All Customer's Correspondence

    Integration

  7. Step 7

    Analyse and Build Persona

    AI reasoning

  8. Step 8

    Generate Sales Email

    AI reasoning

  9. Outcome

    Create Draft Email For Review

    Integration

Attached dependencies

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

2 nodes
  • Google Gemini Chat Model

    AI reasoning dependency

  • Google Gemini Chat Model1

    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.