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

Mautic CRM User Management Automation

Mautic CRM User Management Automation is a 17-node automation blueprint connecting Mautic. Inspect its trigger, execution graph, branches, and implementation requirements.

Mautic

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.

17

Nodes

19

Links

1

Run groups

Connected tools

1 integrations

  • Mautic

Canvas controls

Fit wide systems, then zoom into any run group.

Mautic CRM User Management Automation execution lanes1 run groups containing 17 workflow nodes and 19 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 OUTSet Webhook Request. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set Webhook RequestTRANSFORMSET1 IN / 1 OUTSwitch Webhook Types. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03Switch Webhook TypesDECISIONSWITCH1 IN / 3 OUTFind User. integration node, mautic. 1 incoming and 1 outgoing connections.STEP 04Find UserINTEGRATIONMAUTIC1 IN / 1 OUTSplit Full Name. transform node, function. 1 incoming and 1 outgoing connections.STEP 04Split Full NameTRANSFORMFUNCTION1 IN / 1 OUTFind User To Tag Sale. integration node, mautic. 1 incoming and 1 outgoing connections.STEP 04Find User To Tag SaleINTEGRATIONMAUTIC1 IN / 1 OUTIf not found return -1. transform node, function. 1 incoming and 1 outgoing connections.STEP 05If not found return -1TRANSFORMFUNCTION1 IN / 1 OUTTag User. integration node, mautic. 1 incoming and 0 outgoing connections.STEP 05Tag UserINTEGRATIONMAUTIC1 IN / 0 OUTSet userFound. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Set userFoundTRANSFORMSET1 IN / 1 OUT@MAIN STUDENT DATA. decision node, merge. 2 incoming and 1 outgoing connections.STEP 07@MAIN STUDENT DATADECISIONMERGE2 IN / 1 OUTIF NOT userFound. decision node, if. 1 incoming and 2 outgoing connections.STEP 08IF NOT userFoundDECISIONIF1 IN / 2 OUTMautic. integration node, mautic. 1 incoming and 0 outgoing connections.STEP 09MauticINTEGRATIONMAUTIC1 IN / 0 OUTSwitch User.type. decision node, switch. 1 incoming and 3 outgoing connections.STEP 09Switch User.typeDECISIONSWITCH1 IN / 3 OUTUpdate User. integration node, mautic. 1 incoming and 1 outgoing connections.STEP 10Update UserINTEGRATIONMAUTIC1 IN / 1 OUTIF unsubscribe_from_marketing_emails. decision node, if. 1 incoming and 2 outgoing connections.STEP 11IF unsubscribe_from_marke…DECISIONIF1 IN / 2 OUTUnsubscribe User. integration node, mautic. 2 incoming and 0 outgoing connections.OUTCOMEUnsubscribe UserINTEGRATIONMAUTIC2 IN / 0 OUTRemove unsubscribe. integration node, mautic. 2 incoming and 0 outgoing connections.OUTCOMERemove unsubscribeINTEGRATIONMAUTIC2 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.17 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

19 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Set Webhook Request

    Transform

  3. Step 3

    Switch Webhook Types

    Decision

  4. Step 4

    Find User

    Integration

    Split Full Name

    Transform

    Find User To Tag Sale

    Integration

  5. Step 5

    If not found return -1

    Transform

    Tag User

    Integration

  6. Step 6

    Set userFound

    Transform

  7. Step 7

    @MAIN STUDENT DATA

    Decision

  8. Step 8

    IF NOT userFound

    Decision

  9. Step 9

    Mautic

    Integration

    Switch User.type

    Decision

  10. Step 10

    Update User

    Integration

  11. Step 11

    IF unsubscribe_from_marketing_emails

    Decision

  12. Outcome

    Unsubscribe User

    Integration

    Remove unsubscribe

    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