Zammad ExtendedInstall

Summary

Retrieve multiple Zammad tickets using various client-side filters without requiring Elasticsearch. Supports pagination to fetch up to a specified limit, sorts the tickets, and filters them by status, priority, group, owner, customer, organization, and creation or update date.

Inputs

• Limit — Maximum number of tickets to return (1 to 500, default 25).
• Sortieren nach (Sort By) — Field to sort tickets by: created_at, updated_at, id, title, or priority (default: created_at).
• Reihenfolge (Sort Order) — Sort order: descending (neueste zuerst) or ascending (älteste zuerst), default descending.
• Filter — Collection of filters including status (include), excludeStatus (exclude), priority, group/team name, assigned agent (owner), customer (email or login), organization name, createdAfter date, and updatedAfter date.

Output shape

multiple ticket objects matching the filters, each as an individual item.

Retrieves tickets in batches (pages) of up to 100 from Zammad's API, accumulating until reaching the user-specified limit or no more tickets are available. After fetching, it applies client-side filtering based on the specified filters. Returned tickets include expanded details due to 'expand=true'. If no tickets match, no output items are returned.

Examples

Example 1: Get up to 50 tickets created after 2024-01-01 with status 'open' or '02 in Bearbeitung', sorted by priority ascending.

Limit=50, sortBy=priority, sortOrder=asc, filters.status=['open','02 in Bearbeitung'], filters.createdAfter=2024-01-01T00:00:00.000Z

Links

• n8n community nodes installation guide