Entra User to Zammad User Sync
Configured with Compare Datasets, HTTP Request, Split Out, Zammad. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
- Routing
- Integration
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Get Groups from Entra | Web / API | HTTP Request | See node parameters |
| Remove outer Array | Transform | Split Out | See node parameters |
| Select Entra Zammad default Group | Routing | If | See node parameters |
| Remove outer Array from Entra User | Transform | Split Out | See node parameters |
| Zammad Univeral User Object | Transform | Edit Fields | See node parameters |
| Get Zammad Users | Integration | Zammad | getAll |
| Merge | Transform | Merge | See node parameters |
| Get Members of the default group | Web / API | HTTP Request | See node parameters |
| Find new Zammad Users | Transform | Compare Datasets | See node parameters |
| Update Zammad User | Integration | Zammad | update |
| Create Zammad User | Integration | Zammad | See node parameters |
| Deactivate Zammad User | Integration | Zammad | update |
| Find removed Users | Transform | Compare Datasets | See node parameters |
| If | Routing | If | See node parameters |
| Select only active Users and entra_obect_type="user" | Routing | If | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
microsoftGraphSecurityOAuth2ApimicrosoftOAuth2ApizammadTokenAuthApi
Workflow notes
Select Entra Zammad default Group
Please enter the Entra group name of users to be synchronized.
Entra User to Zammad User Sync
Entra User to Zammad User Sync
Purpose and structure
This folder contains the Entra User to Zammad User Sync workflow. Its executable nodes use compareDatasets, httpRequest, if, manualTrigger, merge, set, splitOut, zammad. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/1531_Splitout_Comparedatasets_Sync_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Select Entra Users in a named Entra Group that should be synced to Zammad