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

Automated Mautic Unsubscribe Workflow

Automated Mautic Unsubscribe Workflow is a 11-node automation blueprint connecting Gmail, Mautic. Inspect its trigger, execution graph, branches, and implementation requirements.

GmailMautic

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.

11

Nodes

11

Links

1

Run groups

Connected tools

2 integrations

  • Gmail
  • Mautic

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Mautic Unsubscribe Workflow execution lanes1 run groups containing 11 workflow nodes and 11 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.Gmail Trigger. Gmail node, gmailTrigger. 0 incoming and 1 outgoing connections.STARTGmail TriggerGMAILGMAILTRIGGER0 IN / 1 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit FieldsTRANSFORMSET1 IN / 1 OUTIs automated unsubscribe?. decision node, if. 1 incoming and 1 outgoing connections.STEP 03Is automated unsubscribe?DECISIONIF1 IN / 1 OUTExtract Email from 'From' Field. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Extract Email from 'From'…TRANSFORMCODE1 IN / 1 OUTExtract Unique Email Addresses. transform node, code. 1 incoming and 1 outgoing connections.STEP 05Extract Unique Email Addr…TRANSFORMCODE1 IN / 1 OUTGet Mautic Contact ID from Email Address. integration node, mautic. 1 incoming and 1 outgoing connections.STEP 06Get Mautic Contact ID fro…INTEGRATIONMAUTIC1 IN / 1 OUTIf Contact Exists in Mautic. decision node, if. 1 incoming and 5 outgoing connections.STEP 07If Contact Exists in MauticDECISIONIF1 IN / 5 OUTAdd to Do Not Contact List. integration node, mautic. 1 incoming and 0 outgoing connections.OUTCOMEAdd to Do Not Contact ListINTEGRATIONMAUTIC1 IN / 0 OUTAdd to unsubscribed segment. integration node, mautic. 1 incoming and 0 outgoing connections.OUTCOMEAdd to unsubscribed segmentINTEGRATIONMAUTIC1 IN / 0 OUTRemove newsletter segment. integration node, mautic. 1 incoming and 0 outgoing connections.OUTCOMERemove newsletter segmentINTEGRATIONMAUTIC1 IN / 0 OUTReply Unsubscribe Message. Gmail node, gmail. 2 incoming and 0 outgoing connections.OUTCOMEReply Unsubscribe MessageGMAILGMAIL2 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.11 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

Gmail Trigger

11 Execution Links

  1. Start

    Gmail Trigger

    Trigger

  2. Step 2

    Edit Fields

    Transform

  3. Step 3

    Is automated unsubscribe?

    Decision

  4. Step 4

    Extract Email from 'From' Field

    Transform

  5. Step 5

    Extract Unique Email Addresses

    Transform

  6. Step 6

    Get Mautic Contact ID from Email Address

    Integration

  7. Step 7

    If Contact Exists in Mautic

    Decision

  8. Outcome

    Add to Do Not Contact List

    Integration

    Add to unsubscribed segment

    Integration

    Remove newsletter segment

    Integration

    Reply Unsubscribe Message

    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