Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Lead Capture to Email Subscription

Lead Capture to Email Subscription is a 2-node automation blueprint connecting Facebook Lead Ads, KlickTipp. 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.

2

Nodes

1

Links

1

Run groups

Connected tools

2 integrations

  • Facebook Lead Ads
  • KlickTipp

Canvas controls

Fit wide systems, then zoom into any run group.

Lead Capture to Email Subscription execution lanes1 run groups containing 2 workflow nodes and 1 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.Facebook Lead Ads Trigger. trigger node, facebookLeadAdsTrigger. 0 incoming and 1 outgoing connections.STARTFacebook Lead Ads TriggerTRIGGERFACEBOOKLEADADSTRIGGER0 IN / 1 OUTSubscribe lead in KlickTipp. integration node, klicktipp. 1 incoming and 0 outgoing connections.OUTCOMESubscribe lead in KlickTippINTEGRATIONKLICKTIPP1 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.2 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

Facebook Lead Ads Trigger

1 Execution Link
  1. Start

    Facebook Lead Ads Trigger

    Trigger

  2. Outcome

    Subscribe lead in KlickTipp

    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.