Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Sync Entra Contacts to Zammad

Sync Entra Contacts to Zammad is a 13-node automation blueprint connecting Microsoft Entra, Zammad. Inspect its trigger, execution graph, branches, and implementation requirements.

Microsoft EntraZammad

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.

13

Nodes

15

Links

1

Run groups

Connected tools

2 integrations

  • Microsoft Entra
  • Zammad

Canvas controls

Fit wide systems, then zoom into any run group.

Sync Entra Contacts to Zammad execution lanes1 run groups containing 13 workflow nodes and 15 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.When clicking ‘Test workflow’. trigger node, manualTrigger. 0 incoming and 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTGet Zammad Users. integration node, zammad. 1 incoming and 1 outgoing connections.STEP 02Get Zammad UsersINTEGRATIONZAMMAD1 IN / 1 OUTGet Contacts from Entra. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Get Contacts from EntraINTEGRATIONHTTPREQUEST1 IN / 1 OUTFilter if needed. decision node, if. 1 incoming and 3 outgoing connections.STEP 03Filter if neededDECISIONIF1 IN / 3 OUTEntra Contacts. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Entra ContactsTRANSFORMSPLITOUT1 IN / 1 OUTFilter contacts if needed. decision node, if. 1 incoming and 1 outgoing connections.STEP 04Filter contacts if neededDECISIONIF1 IN / 1 OUTZammad Univeral User Object. transform node, set. 1 incoming and 3 outgoing connections.STEP 05Zammad Univeral User ObjectTRANSFORMSET1 IN / 3 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 06MergeDECISIONMERGE2 IN / 1 OUTFind new Zammad Users. decision node, compareDatasets. 2 incoming and 1 outgoing connections.STEP 06Find new Zammad UsersDECISIONCOMPAREDATASETS2 IN / 1 OUTFind removed Users. decision node, compareDatasets. 2 incoming and 1 outgoing connections.STEP 06Find removed UsersDECISIONCOMPAREDATASETS2 IN / 1 OUTUpdate Zammad User. integration node, zammad. 1 incoming and 0 outgoing connections.OUTCOMEUpdate Zammad UserINTEGRATIONZAMMAD1 IN / 0 OUTCreate Zammad User. integration node, zammad. 1 incoming and 0 outgoing connections.OUTCOMECreate Zammad UserINTEGRATIONZAMMAD1 IN / 0 OUTDeactivate Zammad User. integration node, zammad. 1 incoming and 0 outgoing connections.OUTCOMEDeactivate Zammad UserINTEGRATIONZAMMAD1 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.13 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

When clicking ‘Test workflow’

15 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Get Zammad Users

    Integration

    Get Contacts from Entra

    Integration

  3. Step 3

    Filter if needed

    Decision

    Entra Contacts

    Transform

  4. Step 4

    Filter contacts if needed

    Decision

  5. Step 5

    Zammad Univeral User Object

    Transform

  6. Step 6

    Merge

    Decision

    Find new Zammad Users

    Decision

    Find removed Users

    Decision

  7. Outcome

    Update Zammad User

    Integration

    Create Zammad User

    Integration

    Deactivate Zammad User

    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