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

Email Masking Workflow

Email Masking Workflow is a 6-node automation blueprint connecting Masked email API. Inspect its trigger, execution graph, branches, and implementation requirements.

Masked 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.

6

Nodes

5

Links

1

Run groups

Connected tools

1 integrations

  • Masked email API

Canvas controls

Fit wide systems, then zoom into any run group.

Email Masking Workflow execution lanes1 run groups containing 6 workflow nodes and 5 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 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTSession. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02SessionINTEGRATIONHTTPREQUEST1 IN / 1 OUTget fields for creation. transform node, set. 1 incoming and 1 outgoing connections.STEP 03get fields for creationTRANSFORMSET1 IN / 1 OUTcreate random masked email. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04create random masked emailINTEGRATIONHTTPREQUEST1 IN / 1 OUTprepare output. transform node, set. 1 incoming and 1 outgoing connections.STEP 05prepare outputTRANSFORMSET1 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.6 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

5 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Session

    Integration

  3. Step 3

    get fields for creation

    Transform

  4. Step 4

    create random masked email

    Integration

  5. Step 5

    prepare output

    Transform

  6. 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