Zammad ExtendedInstall

Summary

Execute a custom HTTP API call to a selected Zammad API endpoint using the specified method, with optional query parameters and request body.

Inputs

• HTTP-Methode (required) — HTTP method to use for the API call: GET, POST, PUT, PATCH, or DELETE.
• Endpunkt (required) — Zammad API endpoint to call, selectable from predefined endpoints or customizable via expression for dynamic IDs.
• Query-Parameter — Optional URL query parameters to include in the API call, provided as key-value pairs.
• Body (JSON) — Request body as a JSON object for POST, PUT, or PATCH requests.
• Suchanfrage (required) — Elasticsearch query string for the endpoint "/api/v1/tickets/search" (only when selected endpoint is this).
• Limit — Maximum number of results to return for ticket search endpoint (default 25).
• Sortieren nach — Field to sort ticket search results by (e.g. created_at, updated_at).
• Sortierreihenfolge — Order of sorting for ticket search results, ascending or descending.

Output shape

a list of JSON objects representing the API response items or a single JSON object if the response is not an array

If the API response is an array, each element results in a separate output item; otherwise, the entire response is output as a single item. For POST, PUT, PATCH methods, the request body must be valid JSON. Query parameters and endpoint selection control the request specifics.

Examples

Example 1: Perform a GET request to retrieve all users

Set HTTP-Methode to GET, Endpunkt to /api/v1/users, optionally add query parameters for filtering.

Example 2: Search tickets using Elasticsearch query

Set HTTP-Methode to GET, Endpunkt to /api/v1/tickets/search, configure Suchanfrage, Limit, Sortieren nach, and Sortierreihenfolge accordingly.

Links

• n8n community nodes installation guide