Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Discourse User Enrichment and Notification

Discourse User Enrichment and Notification is a 7-node automation blueprint connecting Clearbit, Slack, Discourse. 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.

7

Nodes

6

Links

1

Run groups

Connected tools

3 integrations

  • Clearbit
  • Slack
  • Discourse

Canvas controls

Fit wide systems, then zoom into any run group.

Discourse User Enrichment and Notification execution lanes1 run groups containing 7 workflow nodes and 6 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.On new Discourse user. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTOn new Discourse userTRIGGERWEBHOOK0 IN / 1 OUTFilter out common personal emails. decision node, filter. 1 incoming and 1 outgoing connections.STEP 02Filter out common persona…DECISIONFILTER1 IN / 1 OUTEnrich user with Clearbit. integration node, clearbit. 1 incoming and 2 outgoing connections.STEP 03Enrich user with ClearbitINTEGRATIONCLEARBIT1 IN / 2 OUTGet company info. integration node, clearbit. 1 incoming and 1 outgoing connections.STEP 04Get company infoINTEGRATIONCLEARBIT1 IN / 1 OUTNo clearbit enrichment available. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 04No clearbit enrichment av…INTEGRATIONNOOP1 IN / 0 OUTFilter for high value leads. decision node, filter. 1 incoming and 1 outgoing connections.STEP 05Filter for high value leadsDECISIONFILTER1 IN / 1 OUTPost message in Channel. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMEPost message in ChannelSLACKSLACK1 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.7 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

On new Discourse user

6 Execution Links
  1. Start

    On new Discourse user

    Trigger

  2. Step 2

    Filter out common personal emails

    Decision

  3. Step 3

    Enrich user with Clearbit

    Integration

  4. Step 4

    Get company info

    Integration

    No clearbit enrichment available

    Integration

  5. Step 5

    Filter for high value leads

    Decision

  6. Outcome

    Post message in Channel

    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.