Skip to main content

Entra contacts to Zammad user sync

Workflow preview

Workflow preview
100%
Entra contacts to Zammad user sync preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 : E...

Best for

  • CRM automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.stickynote, n8n-nodes-base.set, n8n-nodes-base.zammad, n8n-nodes-base.merge, n8n-nodes-base.comparedatasets, n8n-nodes-base.httprequest, n8n-nodes-base.splitout

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Sirhexalot.

Original n8n.io source

1.1 Workflow description

Title
Entra contacts to Zammad user sync
Workflow name
Entra contacts to Zammad user sync

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, and formats it for Zammad compatibility.
  3. Synchronize with Zammad:
    • Identifies users in Zammad who need updates based on Entra data.
    • Adds new users from Entra to Zammad.
    • Deactivates users in Zammad if they are no longer in Entra.

Key Features

  • Dynamic Matching: Compares contacts from Entra with existing Zammad users based on email and updates records accordingly.
  • Efficient Management: Automatically creates, updates, or deactivates Zammad users based on their status in Entra.
  • Custom Fields: Supports custom field mapping, ensuring enriched user profiles in Zammad.

Setup Instructions

  1. Microsoft Entra Integration:

    • Ensure proper API permissions for accessing Entra contacts.
    • Configure Microsoft OAuth2 credentials in n8n.
  2. Zammad Integration:

    • Set up Zammad API credentials with appropriate access rights.
    • Customize the workflow to include additional fields or map existing fields as needed.
  3. Run Workflow:

    • Trigger the workflow manually or set up an automation schedule (e.g., daily sync).
    • Review created/updated/deactivated users in Zammad.

Use Cases

  • IT Administration: Keep your support system in sync with the organization’s Entra data.
  • Customer Management: Ensure accurate and up-to-date user records in Zammad.

Prerequisites

  • Access to an Entra (Azure AD) environment with contacts data.
  • A Zammad instance with API credentials for user management.
  • A custom field in Zammad User Object (entra_key) of type String.

  • A custom field in Zammad User Object (entra_object_type) of type `Single selection field with two key value pairs
    • user = User
    • contact = Contact`


This workflow is fully customizable and can be adapted to your organization’s specific needs. Save time and reduce manual errors by automating your user sync process with this template!

If you have found an error or have any suggestions, please report them here on Github.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Zammad Univeral User Object

Type / Role
n8n-nodes-base.set - set
Config choices
Version 1

Block 4 - Get Zammad Users

Type / Role
n8n-nodes-base.zammad - zammad
Config choices
Version 1

Block 5 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 6 - Find new Zammad Users

Type / Role
n8n-nodes-base.compareDatasets - compareDatasets
Config choices
Version 2.3

Block 7 - Update Zammad User

Type / Role
n8n-nodes-base.zammad - zammad
Config choices
Version 1

Block 8 - Create Zammad User

Type / Role
n8n-nodes-base.zammad - zammad
Config choices
Version 1

Block 9 - Deactivate Zammad User

Type / Role
n8n-nodes-base.zammad - zammad
Config choices
Version 1

Block 10 - Find removed Users

Type / Role
n8n-nodes-base.compareDatasets - compareDatasets
Config choices
Version 2.3

Block 11 - Get Contacts from Entra

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Entra Contacts

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 13 - Filter contacts if needed

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 14 - Filter if needed

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

3. Summary Table

Workflow Entra contacts to Zammad user sync
Complexity intermediate
Nodes 14
Categories CRM
Author Sirhexalot
Published 01 Dec 2024

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2599/2599.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Entra contacts to Zammad user sync do?

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 : E...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.