ZAMMAD n8n INTEGRATION: AUTOMATE ZAMMAD WITH N8N

The Update User action allows you to modify existing user records in your Zammad instance programmatically. This is essential for keeping customer information synchronized across your systems, whether you're updating contact details, adjusting permissions, or enriching user profiles with data from other applications.

Key parameters: Credential to connect with (required dropdown), Resource (set to "User"), Operation (set to "Update"), User ID (required text field), and Update Fields (optional section for specific properties to modify).

Use cases: Automatically update user phone numbers when they're changed in your CRM, sync user roles or permissions based on subscription changes in your billing system, or enrich customer profiles with data pulled from LinkedIn or other sources.

The Get Self action retrieves information about the currently authenticated user—the account whose credentials are being used for the n8n connection. This is particularly useful for validation, logging, or workflows that need to reference the automation account's details.

Key parameters: Credential to connect with (required dropdown), Resource (set to "User"), and Operation (set to "Get Self").

Use cases: Validate that your automation credentials are working correctly at the start of a workflow, log which account performed automated actions for audit trails, or retrieve the automation user's ID to exclude from certain bulk operations.

The Get Many action retrieves multiple user records from Zammad in a single operation. This is ideal for generating reports, performing bulk operations, or syncing your entire user base with external systems.

Key parameters: Credential to connect with (required), Resource (set to "User"), Operation (set to "Get Many"), Return All toggle, Limit (number field, default 50), and optional Filters section.

Use cases: Export all Zammad users to a spreadsheet for monthly reporting, sync your user base with an email marketing platform, or find users matching specific criteria for targeted communications.

The Get User action retrieves detailed information about a specific user based on their unique ID. Use this when you need complete user data for a particular individual—perhaps to display in a dashboard, validate before an operation, or pass to another system.

Key parameters: Credential to connect with (required), Resource (set to "User"), Operation (set to "Get"), and User ID (required text field).

Use cases: Fetch customer details when a support ticket is escalated, validate user existence before attempting updates from external systems, or retrieve user data to populate personalized email templates.

The Delete User action permanently removes a user from your Zammad instance. This is useful for GDPR compliance workflows, cleaning up test accounts, or deprovisioning users when they leave your organization.

Key parameters: Credential to connect with (required), Resource (set to "User"), Operation (set to "Delete"), and User ID (required text field).

Use cases: Automate GDPR "right to be forgotten" requests, clean up test users created during QA processes, or deprovision support accounts when employees leave.

The Create User action adds new user records to your Zammad instance. This is fundamental for automated onboarding—whether you're creating customer accounts when they sign up, importing users from other systems, or provisioning support agent accounts.

Key parameters: Credential to connect with (required), Resource (set to "User"), Operation (set to "Create"), First Name (required), Last Name (required), and Additional Fields (optional section for email, phone, organization, roles, and custom fields).

Use cases: Automatically create Zammad users when someone registers on your website, import users from a CRM or HR system during initial setup, or create support agent accounts from an IT provisioning workflow.

The Ticket Get Many action retrieves multiple tickets from Zammad, essential for reporting dashboards, bulk processing, or synchronizing ticket data with external systems. You can limit results or fetch everything depending on your needs.

Key parameters: Credential to connect with (required), Resource (set to "Ticket"), Operation (set to "Get Many"), Return All toggle, and Limit (number field, default 50).

Use cases: Generate daily open ticket reports sent to management via Slack, sync tickets with a BI tool for support analytics, or archive old tickets to external storage for compliance.

The Get Ticket action retrieves complete information about a specific ticket using its unique ID. This is your go-to action when you need full ticket details for processing, display, or passing to another system in your workflow.

Key parameters: Credential to connect with (required), Resource (set to "Ticket"), Operation (set to "Get"), and Ticket ID (required text field).

Use cases: Fetch ticket details when a customer replies via email, retrieve ticket information to populate a custom notification, or validate ticket status before performing follow-up actions.

The Delete Ticket action permanently removes a ticket from Zammad. Use this for cleanup operations, removing spam tickets, or implementing data retention policies.

Key parameters: Credential to connect with (required), Resource (set to "Ticket"), Operation (set to "Delete"), and Ticket ID (required text field).

Use cases: Automatically delete spam tickets identified by your filtering rules, clean up test tickets from development environments, or implement data retention policies that remove resolved tickets after a set period.

The Create Ticket action opens new support tickets in Zammad programmatically. This is one of the most powerful actions—enabling you to turn any event in your tech stack into a trackable support request.

Key parameters: Credential to connect with (required), Resource (set to "Ticket"), Operation (set to "Create"), Title (required), Group Name or ID (required), Customer Email Name or ID (required), Article (optional section), and Additional Fields (optional).

Use cases: Create tickets automatically from website contact form submissions, generate support tickets when monitoring alerts fire, or open tickets from customer messages in Slack or Microsoft Teams.

The Update Organization action modifies existing organization records in Zammad. Organizations typically represent companies or entities that group multiple users together—keeping this data current ensures accurate reporting and proper ticket routing.

Key parameters: Credential to connect with (required), Resource (set to "Organization"), Operation (set to "Update"), Organization ID (required), and Update Fields (optional section).

Use cases: Sync organization data when company information changes in your CRM, update organization tier/status based on subscription changes, or bulk-update organization metadata during data cleanup projects.

The Get Many Organizations action retrieves multiple organization records from Zammad. This is useful for reporting, synchronization with external systems, or building organization-aware workflows.

Key parameters: Credential to connect with (required), Resource (set to "Organization"), Operation (set to "Get Many"), Return All toggle, and Limit (number field, default 50).

Use cases: Export organization data for business intelligence reporting, sync organizations with your CRM or accounting system, or generate organization lists for targeted communications.

The Get Organization action retrieves detailed information about a specific organization using its unique ID. Use this when you need complete organization data for display, validation, or processing.

Key parameters: Credential to connect with (required), Resource (set to "Organization"), Operation (set to "Get"), and Organization ID (required text field accepting Fixed value or Expression).

Use cases: Fetch organization details when processing a VIP ticket, validate organization existence before assigning users, or retrieve organization data for personalized communications.

The Delete Organization action permanently removes an organization from Zammad. This is useful for cleaning up merged or defunct organizations and maintaining data hygiene.

Key parameters: Credential to connect with (required), Resource (set to "Organization"), Operation (set to "Delete"), and Organization ID (required text field).

Use cases: Clean up organizations after company mergers, remove test organizations from production environments, or implement data retention policies for inactive organizations.

The Create Organization action adds new organization records to Zammad. This enables automated onboarding of company customers and structured grouping of related users.

Key parameters: Credential to connect with (required), Resource (set to "Organization"), Operation (set to "Create"), Organization Name (required), and Additional Fields (optional section).

Use cases: Automatically create organizations when companies sign up for your service, import organizations from your CRM during initial setup, or create organizations as part of partner onboarding workflows.

The Update Group action modifies existing support groups in Zammad. Groups are used to organize agents and route tickets—keeping group settings current ensures proper ticket assignment and team structure.

Key parameters: Credential to connect with (required), Resource (set to "Group"), Operation (set to "Update"), Group ID (required), and Update Fields (optional section).

Use cases: Update group email addresses when team configurations change, modify group settings as part of organizational restructuring, or sync group properties with an HR or team management system.

The Get Many Groups action retrieves multiple group records from Zammad. This is useful for building dynamic routing rules, generating team reports, or syncing group data with external systems.

Key parameters: Credential to connect with (required), Resource (set to "Group"), Operation (set to "Get Many"), Return All toggle, and Limit (number field, default 50).

Use cases: Generate reports on group workloads and ticket distribution, build dynamic dropdowns in custom interfaces pulling live group data, or audit group configurations across your Zammad instance.

The Get Group action retrieves detailed information about a specific support group using its unique ID. Use this when you need complete group data for display, validation, or conditional routing logic.

Key parameters: Credential to connect with (required), Resource (set to "Group"), Operation (set to "Get"), and Group ID (required field accepting Fixed value or Expression).

Use cases: Fetch group details to validate before ticket assignment, retrieve group information for display in custom dashboards, or check group settings as part of audit workflows.

The Delete Group action permanently removes a support group from Zammad. Use this for cleanup operations when teams are dissolved or restructured.

Key parameters: Credential to connect with (required), Resource (set to "Group"), Operation (set to "Delete"), and Group ID (required text field).

Use cases: Clean up deprecated groups after organizational changes, remove test groups from production environments, or implement group lifecycle management automation.

The Create Group action adds new support groups to your Zammad instance. Groups are essential for organizing your support team and routing tickets to the right people.

Key parameters: Credential to connect with (required), Resource (set to "Group"), Operation (set to "Create"), Group Name (required), and Additional Fields (optional section).

Use cases: Automatically create support groups when new departments are added, provision groups as part of multi-tenant onboarding, or create temporary groups for special projects or campaigns.