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

Zammad Role Update Automation

Zammad Role Update Automation is a 10-node automation blueprint connecting Zammad, Custom API. Inspect its trigger, execution graph, branches, and implementation requirements.

ZammadCustom 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

9

Links

1

Run groups

Connected tools

2 integrations

  • Zammad
  • Custom API

Canvas controls

Fit wide systems, then zoom into any run group.

Zammad Role Update Automation execution lanes1 run groups containing 10 workflow nodes and 9 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 1 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTBasic Variables. transform node, set. 1 incoming and 2 outgoing connections.STEP 02Basic VariablesTRANSFORMSET1 IN / 2 OUTGet all Roles. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get all RolesINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet all Users. integration node, zammad. 1 incoming and 1 outgoing connections.STEP 03Get all UsersINTEGRATIONZAMMAD1 IN / 1 OUTZammad Univeral Role Object. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Zammad Univeral Role ObjectTRANSFORMSET1 IN / 1 OUTZammad Univeral User Object. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Zammad Univeral User ObjectTRANSFORMSET1 IN / 1 OUTFilter Roles if needed. decision node, if. 1 incoming and 1 outgoing connections.STEP 05Filter Roles if neededDECISIONIF1 IN / 1 OUTIf. decision node, if. 1 incoming and 1 outgoing connections.STEP 05IfDECISIONIF1 IN / 1 OUTConvert to Excel Roles. integration node, convertToFile. 1 incoming and 0 outgoing connections.OUTCOMEConvert to Excel RolesINTEGRATIONCONVERTTOFILE1 IN / 0 OUTUpdate Users to default Role(s). integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEUpdate Users to default R…INTEGRATIONHTTPREQUEST1 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

When clicking ‘Test workflow’

9 Execution Links

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Basic Variables

    Transform

  3. Step 3

    Get all Roles

    Integration

    Get all Users

    Integration

  4. Step 4

    Zammad Univeral Role Object

    Transform

    Zammad Univeral User Object

    Transform

  5. Step 5

    Filter Roles if needed

    Decision

    If

    Decision

  6. Outcome

    Convert to Excel Roles

    Integration

    Update Users to default Role(s)

    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