Zammad icon

Zammad

Consume Zammad REST API

Priority → Create

AI-generated

Overview

This node integrates with the Zammad REST API to manage ticket priorities. Specifically, the 'Priority Create' operation allows users to create a new ticket priority by specifying its name and optional additional fields such as UI icon, UI color, active status, default creation flag, and notes. This is useful in scenarios where a support or ticketing system needs customized priority levels to categorize and escalate tickets effectively.

Use Case Examples

  1. Creating a new priority named 'High' with a red UI color and setting it as active.
  2. Adding a priority with a specific icon and a note explaining its usage.

Properties

Name Meaning
Authentication The authentication method to use for API requests.
API The API type to use for the request.
Name The name of the priority to create.
Additional Fields Optional additional fields for the priority such as UI icon, UI color, active status, default create flag, and note.

Output

JSON

  • id - The unique identifier of the created priority.
  • name - The name of the created priority.
  • ui_icon - The UI icon associated with the priority.
  • ui_color - The UI color associated with the priority.
  • active - Indicates if the priority is active.
  • default_create - Indicates if the priority is the default for ticket creation.
  • note - Additional notes about the priority.

Dependencies

  • Zammad REST API

Troubleshooting

  • Ensure the authentication credentials are correctly configured and valid for the chosen authentication method.
  • Verify that the API endpoint is accessible and the base URL is correctly set in the node credentials.
  • Check that the 'name' property is provided and not empty, as it is required for creating a priority.
  • If optional fields are used, ensure their values conform to expected formats (e.g., color codes, boolean values).
  • Common error messages include authentication failures (401 Unauthorized), missing required fields (400 Bad Request), and permission issues (403 Forbidden). Resolving these typically involves checking credentials, input parameters, and user permissions in Zammad.

Links

Discussion