Sync Entra user to Zammad user
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Zammad. It also calls graph.microsoft.com over HTTP.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Get Zammad Users (Zammad): get many
- Get Groups from Entra (HTTP Request): calls graph.microsoft.com
- Select only active Users and entra_obect_type="user" (If): checks a condition and branches into true / false
- Remove outer Array (Split Out): splits a list into separate items
- Merge: merges the data from its input branches
- Find new Zammad Users (Compare Datasets): uses Compare Datasets
- Find removed Users (Compare Datasets): uses Compare Datasets
- Select Entra Zammad default Group (If): checks a condition and branches into true / false
- Update Zammad User (Zammad): update
- Create Zammad User (Zammad): uses Zammad
…plus 5 more steps. See the full node list below.
Services it uses
HTTP calls to: graph.microsoft.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Zammad
n8n-nodes-base.zammad - Merge
n8n-nodes-base.merge - Compare Datasets
n8n-nodes-base.compareDatasets
From the author
This workflow facilitates seamless synchronization between Entra (Microsoft Azure AD) and Zammad. It automates the following processes: 1. Fetch Entra Group Members: Retrieves users from a designated Entra group. These users are candidates for…