Entra contacts to Zammad user sync

by Sirhexalot ✓ · 442 views · created 2024-12-01 · CRM

What this workflow does

This workflow has 13 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”.

1. Get Zammad Users (Zammad): get many
2. Get Contacts from Entra (HTTP Request): calls graph.microsoft.com
3. Filter if needed (If): checks a condition and branches into true / false
4. Entra Contacts (Split Out): splits a list into separate items
5. Merge: merges the data from its input branches
6. Find new Zammad Users (Compare Datasets): uses Compare Datasets
7. Find removed Users (Compare Datasets): uses Compare Datasets
8. Filter contacts if needed (If): checks a condition and branches into true / false
9. Update Zammad User (Zammad): update
10. Create Zammad User (Zammad): uses Zammad

…plus 2 more steps. See the full node list below.

Services it uses

Zammad

HTTP calls to: graph.microsoft.com

Before you upgrade to n8n 3.0

Nodes used (8)

• Manual Triggern8n-nodes-base.manualTrigger
• Edit Fields (Set)n8n-nodes-base.set
• Zammadn8n-nodes-base.zammad
• Mergen8n-nodes-base.merge
• Compare Datasetsn8n-nodes-base.compareDatasets
• HTTP Requestn8n-nodes-base.httpRequest
• Split Outn8n-nodes-base.splitOut
• Ifn8n-nodes-base.if

From the author

This workflow facilitates seamless synchronization between Entra (Microsoft Azure AD) and Zammad. It automates the following processes: 1. Fetch Entra Contacts: 2. Create Universal User Object: Extracts key user information, such as email, phone, and name,…

View the original on n8n.io → Check your own copy