Most-used Zammad workflows
- Export Zammad Objects Users, Roles, Groups and Organizations to Excel (18 nodes)
- Export Zammad Objects (users, Roles, Groups, Organizations) to Excel — n8n Zammad workflow (18 nodes)
- Entra User to Zammad User Sync (17 nodes)
- Sync Entra User to Zammad User — n8n Zammad workflow (17 nodes)
- Entra Contacts to Zammad User Sync (14 nodes)
- Entra Contacts to Zammad User Sync (zammad) — n8n Zammad workflow (14 nodes)
- Update All Zammad Roles to Default Values (10 nodes)
- Update All Zammad Roles to Default Values (zammad) — n8n Zammad workflow (10 nodes)
- Assign Zammad Users to Organizations Based on Email Domain (8 nodes)
- Zammad Open Tickets — n8n Zammad workflow (5 nodes)
Export Zammad Objects Users, Roles, Groups and Organizations to Excel. Uses manualTrigger, zammad, httpRequest, convertToFile. Event-driven trigger; 18 nodes.
This n8n workflow enables you to export data from Zammad, including Users, Roles, Groups, and Organizations, into individual Excel files. It simplifies data handling and reporting by creating structur
Entra User to Zammad User Sync. Uses manualTrigger, stickyNote, httpRequest, splitOut. Event-driven trigger; 17 nodes.
This workflow facilitates seamless synchronization between Entra (Microsoft Azure AD) and Zammad. It automates the following processes: Fetch Entra Group Members: Retrieves users from a designated Ent
Entra Contacts to Zammad User Sync. Uses manualTrigger, stickyNote, zammad, compareDatasets. Event-driven trigger; 14 nodes.
This workflow facilitates seamless synchronization between Entra (Microsoft Azure AD) and Zammad. It automates the following processes: Fetch Entra Contacts: Create Universal User Object: Extracts key
Update all Zammad Roles to default values. Uses manualTrigger, zammad, httpRequest, convertToFile. Event-driven trigger; 10 nodes.
This n8n workflow allows you to reset all user roles in Zammad to specified default roles. It ensures consistency in role management across your Zammad instance. Retrieve all active users from Zammad.
This n8n workflow automates the assignment of existing users to organizations in Zammad based on their email domains, utilizing Zammad’s "domain-based assignment" feature.
Zammad Open Tickets. Uses manualTrigger, zammad, zulip. Event-driven trigger; 5 nodes.
Fetches Zammad tickets at daily basis at 08:30 then sends them to #customer support>ticket on zulip for daily standups.
Update people through Zulip about open tickets in Zammad. Uses zammad, zulip. Event-driven trigger; 5 nodes.
12 of 12 workflows in this view · Browse all →
FAQ
How many n8n Zammad workflows are in the catalog?
12 n8n workflows in AutomationFlows currently use the Zammad integration — triggers, actions, or both.
How do I connect Zammad in n8n?
After importing the workflow JSON, n8n will prompt for Zammad credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Zammad workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.