Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
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

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

12

Nodes

11

Edges

6

Zones

System stack

3 integrations

  • Clearbit
  • HubSpot
  • Calendly
CRM Company and Contact Automation interactive execution graphStructural view of 12 workflow nodes and 11 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Calendly Trigger. trigger node, calendlyTrigger. 0 incoming and 1 outgoing connections.Calendly TriggerTRIGGERCALENDLYTRIGGER0 IN / 1 OUTFilter out personal emails. decision node, filter. 1 incoming and 1 outgoing connections.Filter out personal emailsDECISIONFILTER1 IN / 1 OUTEnrich email. integration node, clearbit. 1 incoming and 2 outgoing connections.Enrich emailINTEGRATIONCLEARBIT1 IN / 2 OUTIf person has a company. decision node, if. 1 incoming and 2 outgoing connections.If person has a companyDECISIONIF1 IN / 2 OUTContact not found, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.Contact not found, do not…INTEGRATIONNOOP1 IN / 0 OUTEnrich company. integration node, clearbit. 1 incoming and 1 outgoing connections.Enrich companyINTEGRATIONCLEARBIT1 IN / 1 OUTUpsert lead. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.Upsert leadHUBSPOTHUBSPOT1 IN / 0 OUTSearch company. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.Search companyHUBSPOTHUBSPOT1 IN / 1 OUTif company does not exist on CRM. decision node, if. 1 incoming and 2 outgoing connections.if company does not exist…DECISIONIF1 IN / 2 OUTCreate company. HubSpot node, hubspot. 1 incoming and 1 outgoing connections.Create companyHUBSPOTHUBSPOT1 IN / 1 OUTUpsert contact. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.Upsert contactHUBSPOTHUBSPOT1 IN / 0 OUTUpdate company. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.Update companyHUBSPOTHUBSPOT1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph a8e731f7b333e9e8Enter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

Calendly Trigger

Trigger

02

Data & operations

4 nodes

Transformations and external-system actions that move the work forward.

Enrich company

Integration

Create company

Integration

Enrich email

Integration

Search company

Integration

03

Intelligence & routing

3 nodes

Model calls and control points that interpret, branch, or govern the run.

if company does not exist on CRM

Decision

Filter out personal emails

Decision

If person has a company

Decision

04

Terminal actions

4 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Upsert contact

Integration

Update company

Integration

Contact not found, do nothing

Integration

Upsert lead

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
11 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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