Actions57
- User Actions
- Organization Actions
- Group Actions
- Ticket Actions
- Article Actions
- Priority Actions
- State Actions
- Tag Actions
- Mention Actions
- Online Notification Actions
- Object Actions
- User Access Token Actions
Priority → Update
AI-generatedOverview
This node operation updates an existing priority in the Zammad system using the REST API. It allows users to modify the priority's name and other optional fields such as UI icon, UI color, active status, default creation status, and notes. This operation is useful for managing ticket priorities dynamically within a workflow, ensuring that priority settings are kept up to date according to business needs.
Use Case Examples
- Updating the name and UI color of a priority to reflect a change in ticket handling urgency.
- Activating or deactivating a priority based on current operational requirements.
- Adding notes to a priority to provide additional context for support agents.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use for API requests (Basic, OAuth2, or Token Authentication). |
| API | The API to use for the operation, either REST API or CTI API. |
| Name | The name of the priority to update. This is a required field when using the REST API. |
| Priority ID | The unique identifier of the priority to update. This is required to specify which priority to modify. |
| Additional Fields | Optional additional fields for the priority such as UI icon, UI color, active status, default creation status, and notes. |
Output
JSON
id- The unique identifier of the updated priority.name- The updated name of the 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
- Requires authentication credentials for the Zammad API (Basic Auth, OAuth2, or Token Auth).
Troubleshooting
- Ensure the Priority ID is correct and exists in the Zammad system to avoid 'not found' errors.
- Verify that the authentication credentials are valid and have sufficient permissions to update priorities.
- Check that required fields like 'Name' are provided when using the REST API to prevent validation errors.
- If the API returns an error, review the error message for details on missing or invalid parameters.
Links
- Zammad API Documentation - Update Priority - Official documentation for updating ticket priorities via the Zammad REST API.
