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

Automated Property Lead Enrichment Workflow

Automated Property Lead Enrichment Workflow is a 11-node automation blueprint connecting Property API, HubSpot, Email. Inspect its trigger, execution graph, branches, and implementation requirements.

Property APIHubSpotEmail

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

  • Property API
  • HubSpot
  • Email

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Property Lead Enrichment Workflow 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.Daily Schedule. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTDaily ScheduleTRIGGERSCHEDULETRIGGER0 IN / 1 OUTWhen clicking "Execute Workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Execute Wo…TRIGGERMANUALTRIGGER0 IN / 1 OUTConfigure Search Parameters. transform node, set. 2 incoming and 1 outgoing connections.STEP 02Configure Search ParametersTRANSFORMSET2 IN / 1 OUTSearch Properties API. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Search Properties APIINTEGRATIONHTTPREQUEST1 IN / 1 OUTFilter Property Results. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Filter Property ResultsTRANSFORMCODE1 IN / 1 OUTGet Owner Contact Info. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Get Owner Contact InfoINTEGRATIONHTTPREQUEST1 IN / 1 OUTFormat Lead Data. transform node, code. 1 incoming and 3 outgoing connections.STEP 06Format Lead DataTRANSFORMCODE1 IN / 3 OUTCreate Excel Spreadsheet. integration node, spreadsheetFile. 1 incoming and 1 outgoing connections.STEP 07Create Excel SpreadsheetINTEGRATIONSPREADSHEETFILE1 IN / 1 OUTSummarize Results. transform node, code. 1 incoming and 1 outgoing connections.STEP 07Summarize ResultsTRANSFORMCODE1 IN / 1 OUTPush to CRM. HubSpot node, hubspot. 1 incoming and 0 outgoing connections.STEP 07Push to CRMHUBSPOTHUBSPOT1 IN / 0 OUTEmail Notification. integration node, emailSend. 2 incoming and 0 outgoing connections.OUTCOMEEmail NotificationINTEGRATIONEMAILSEND2 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.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

Daily Schedule

11 Execution Links

  1. Start

    Daily Schedule

    Trigger

    When clicking "Execute Workflow"

    Trigger

  2. Step 2

    Configure Search Parameters

    Transform

  3. Step 3

    Search Properties API

    Integration

  4. Step 4

    Filter Property Results

    Transform

  5. Step 5

    Get Owner Contact Info

    Integration

  6. Step 6

    Format Lead Data

    Transform

  7. Step 7

    Create Excel Spreadsheet

    Integration

    Summarize Results

    Transform

    Push to CRM

    Integration

  8. Outcome

    Email Notification

    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