Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Masked Email Management Workflow

Masked Email Management Workflow is a 10-node automation blueprint connecting Custom Email API. Inspect its trigger, execution graph, branches, and implementation requirements.

Custom Email 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.

10

Nodes

14

Links

1

Run groups

Connected tools

1 integrations

  • Custom Email API

Canvas controls

Fit wide systems, then zoom into any run group.

Masked Email Management Workflow execution lanes1 run groups containing 10 workflow nodes and 14 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.Webhook. trigger node, webhook. 0 incoming and 2 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 2 OUTSession. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 02SessionINTEGRATIONHTTPREQUEST2 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 5 outgoing connections.STEP 03SwitchDECISIONSWITCH1 IN / 5 OUTcreate random masked email. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 04create random masked emailINTEGRATIONHTTPREQUEST2 IN / 1 OUTdelete. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04deleteINTEGRATIONHTTPREQUEST1 IN / 1 OUTdisabled. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04disabledINTEGRATIONHTTPREQUEST1 IN / 1 OUTget all masked emails. integration node, httpRequest. 4 incoming and 1 outgoing connections.STEP 05get all masked emailsINTEGRATIONHTTPREQUEST4 IN / 1 OUTgather masked email list. transform node, set. 1 incoming and 1 outgoing connections.STEP 06gather masked email listTRANSFORMSET1 IN / 1 OUTcreate html template. integration node, html. 1 incoming and 1 outgoing connections.STEP 07create html templateINTEGRATIONHTML1 IN / 1 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to WebhookTRIGGERRESPONDTOWEBHOOK1 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.10 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

Webhook

14 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Session

    Integration

  3. Step 3

    Switch

    Decision

  4. Step 4

    create random masked email

    Integration

    delete

    Integration

    disabled

    Integration

  5. Step 5

    get all masked emails

    Integration

  6. Step 6

    gather masked email list

    Transform

  7. Step 7

    create html template

    Integration

  8. Outcome

    Respond to Webhook

    Trigger

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