OpenRuna
Sign in
← Workflows

Entra User to Zammad User Sync

17 nodes · manual, httpRequest, splitOut, zammad, compareDatasets

Engine
n8n
Nodes
17
Trigger
scheduled/triggered
Source file
1531_Splitout_Comparedatasets_Sync_Webhook.json

Workflow flow

IntegrationsManualHTTPSplit OutZammadCompareDatasetsIFSetMerge
100%
TRIGGER

When clicking ‘Test workflow’

Manual

Get Groups from Entra

HTTP

Get Zammad Users

Zammad

Remove outer Array

Split Out

Select only active Users and entra_obect_type="user"

IF

Select Entra Zammad default Group

IF

Get Members of the default group

HTTP

Remove outer Array from Entra User

Split Out

If

IF

Zammad Univeral User Object

Set

Merge

Merge

Find new Zammad Users

CompareDatasets

Find removed Users

CompareDatasets

Update Zammad User

Zammad

Create Zammad User

Zammad

Deactivate Zammad User

Zammad

16 steps · flows top to bottom, branches left to right

Browse by integration

manualhttpRequestsplitOutzammadcompareDatasets
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Entra User to Zammad User Sync is a free n8n workflow on OpenRuna — 17 nodes connecting manual, httpRequest, splitOut, zammad, compareDatasets. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"Entra User to Zammad User Sync" is an n8n automation built from 17 nodes spanning manual, httpRequest, splitOut, zammad, compareDatasets. 17 nodes · manual, httpRequest, splitOut, zammad, compareDatasets It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current manual integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 17-node flow from scratch.
  • Use it as a starting template when wiring manual, httpRequest, splitOut, zammad, compareDatasets — adjust node parameters to your accounts and record IDs.
  • Import "Entra User to Zammad User Sync" into n8n, reconnect credentials for manual, httpRequest, splitOut, zammad, compareDatasets, and run the same automation in your own workspace.

Example output

Imported into n8n, "Entra User to Zammad User Sync" exposes 17 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, httpRequest, splitOut, zammad, compareDatasets. Reconnect the manual credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Entra User to Zammad User Sync" into Claude and ask it to explain each of the 17 nodes. Claude is good at suggesting credential mappings for manual, httpRequest, splitOut, zammad, compareDatasets, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Entra User to Zammad User Sync" to your accounts — which manual, httpRequest, splitOut, zammad, compareDatasets credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 17 nodes.

Frequently asked questions

How do I import "Entra User to Zammad User Sync" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Entra User to Zammad User Sync" use?
It uses: manual, httpRequest, splitOut, zammad, compareDatasets. The flow diagram above shows how each service connects across the 17 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and httpRequest credentials in n8n after import.
What trigger type does "Entra User to Zammad User Sync" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Entra User to Zammad User Sync" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, httpRequest, splitOut, zammad, compareDatasets.

Related resources