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
Online Notification → Delete
AI-generatedOverview
This node operation deletes an Online Notification in the Zammad system using the REST API. It is useful for automating the management of notifications, such as removing outdated or irrelevant notifications from the system. For example, it can be used in workflows that clean up notifications after they have been processed or acknowledged.
Use Case Examples
- Deleting an online notification by its ID to keep the notification list clean.
- Automating the removal of notifications related to resolved tickets.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use for the API request, such as Basic Authentication, OAuth2, or Token Authentication. |
| API | The API to use for the request, either REST API or CTI API. |
| Online Notification ID | The unique identifier of the online notification to delete. This is a required field when performing the delete operation. |
Output
JSON
id- The ID of the deleted online notification.message- A confirmation message or status returned by the API after deletion.
Dependencies
- Requires authentication credentials for the Zammad API, which can be Basic Auth, OAuth2, or Token Auth.
Troubleshooting
- Common issues include providing an invalid or non-existent Online Notification ID, which will result in an error from the API indicating the notification could not be found.
- Authentication failures due to incorrect or expired credentials will prevent the API request from succeeding.
- Network or connectivity issues can cause the request to fail; ensure the Zammad server is reachable.
Links
- Zammad API Documentation - Online Notifications Delete - Official documentation for deleting online notifications via the Zammad REST API.