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

CRM Company and Contact Automation

CRM Company and Contact Automation is a 12-node automation blueprint connecting Clearbit, HubSpot, Calendly. Inspect its trigger, execution graph, branches, and implementation requirements.

ClearbitHubSpotCalendly

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.

12

Nodes

11

Links

1

Run groups

Connected tools

3 integrations

  • Clearbit
  • HubSpot
  • Calendly

Canvas controls

Fit wide systems, then zoom into any run group.

CRM Company and Contact Automation execution lanes1 run groups containing 12 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.Calendly Trigger. trigger node, calendlyTrigger. 0 incoming and 1 outgoing connections.STARTCalendly TriggerTRIGGERCALENDLYTRIGGER0 IN / 1 OUTFilter out personal emails. decision node, filter. 1 incoming and 1 outgoing connections.STEP 02Filter out personal emailsDECISIONFILTER1 IN / 1 OUTEnrich email. integration node, clearbit. 1 incoming and 2 outgoing connections.STEP 03Enrich emailINTEGRATIONCLEARBIT1 IN / 2 OUTIf person has a company. decision node, if. 1 incoming and 2 outgoing connections.STEP 04If person has a companyDECISIONIF1 IN / 2 OUTContact not found, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04Contact not found, do not…INTEGRATIONNOOP1 IN / 0 OUTEnrich company. integration node, clearbit. 1 incoming and 1 outgoing connections.STEP 05Enrich companyINTEGRATIONCLEARBIT1 IN / 1 OUTUpsert lead. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.STEP 05Upsert leadHUBSPOTHUBSPOT1 IN / 0 OUTSearch company. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 06Search companyHUBSPOTHUBSPOT1 IN / 1 OUTif company does not exist on CRM. decision node, if. 1 incoming and 2 outgoing connections.STEP 07if company does not exist…DECISIONIF1 IN / 2 OUTCreate company. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.STEP 08Create companyHUBSPOTHUBSPOT1 IN / 1 OUTUpdate company. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.STEP 08Update companyHUBSPOTHUBSPOT1 IN / 0 OUTUpsert contact. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.OUTCOMEUpsert contactHUBSPOTHUBSPOT1 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.12 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

Calendly Trigger

11 Execution Links

  1. Start

    Calendly Trigger

    Trigger

  2. Step 2

    Filter out personal emails

    Decision

  3. Step 3

    Enrich email

    Integration

  4. Step 4

    If person has a company

    Decision

    Contact not found, do nothing

    Integration

  5. Step 5

    Enrich company

    Integration

    Upsert lead

    Integration

  6. Step 6

    Search company

    Integration

  7. Step 7

    if company does not exist on CRM

    Decision

  8. Step 8

    Create company

    Integration

    Update company

    Integration

  9. Outcome

    Upsert contact

    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