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

Intercom User Data Enrichment Workflow

Intercom User Data Enrichment Workflow is a 9-node automation blueprint connecting Intercom, ExactBuyer API. Inspect its trigger, execution graph, branches, and implementation requirements.

IntercomExactBuyer API

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.

9

Nodes

7

Links

2

Run groups

Connected tools

2 integrations

  • Intercom
  • ExactBuyer API

Canvas controls

Fit wide systems, then zoom into any run group.

Intercom User Data Enrichment Workflow execution lanes2 run groups containing 9 workflow nodes and 7 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.Intercom. integration node, intercom. 0 incoming and 0 outgoing connections.CORE RUNTIMEIntercomINTEGRATIONINTERCOM0 IN / 0 OUTOn Webhook event from Intercom. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTOn Webhook event from Int…TRIGGERWEBHOOK0 IN / 1 OUTOn user created. decision node, switch. 1 incoming and 2 outgoing connections.STEP 02On user createdDECISIONSWITCH1 IN / 2 OUTset key fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 03set key fieldsTRANSFORMSET1 IN / 1 OUTOther event. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 03Other eventINTEGRATIONNOOP1 IN / 0 OUTEnrich user from ExactBuyer. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 04Enrich user from ExactBuyerINTEGRATIONHTTPREQUEST1 IN / 2 OUTmassage data. transform node, code. 1 incoming and 1 outgoing connections.STEP 05massage dataTRANSFORMCODE1 IN / 1 OUTCould not find user. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 05Could not find userINTEGRATIONNOOP1 IN / 0 OUTUpdate data in Intercom. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEUpdate data in IntercomINTEGRATIONHTTPREQUEST1 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.9 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

Intercom

0 Execution Links

  1. Core Runtime

    Intercom

    Integration

02

Run Group

On Webhook event from Intercom

7 Execution Links

  1. Start

    On Webhook event from Intercom

    Trigger

  2. Step 2

    On user created

    Decision

  3. Step 3

    set key fields

    Transform

    Other event

    Integration

  4. Step 4

    Enrich user from ExactBuyer

    Integration

  5. Step 5

    massage data

    Transform

    Could not find user

    Integration

  6. Outcome

    Update data in Intercom

    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