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 → Mark All As Read
AI-generatedOverview
This node interacts with the Zammad API to manage online notifications, specifically providing an operation to mark all online notifications as read. It supports multiple authentication methods (Basic, OAuth2, Token) and allows choosing between REST API and CTI API. The 'Mark All As Read' operation sends a POST request to the Zammad API endpoint to mark all online notifications as read for the authenticated user. This node is useful in scenarios where users want to programmatically clear or acknowledge all their unread notifications in Zammad, such as in automated workflows or notification management systems.
Use Case Examples
- Automatically mark all notifications as read after processing them in a workflow.
- Clear all unread notifications for a user at the end of a support shift.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use for connecting to the Zammad API. |
| API | The API to use for the operation, either REST API or CTI API. |
Output
JSON
result- The response from the Zammad API after marking all online notifications as read.
Dependencies
- Zammad API
Troubleshooting
- Ensure the correct authentication method is selected and credentials are valid to avoid authentication errors.
- Verify the API endpoint is accessible and the user has permissions to mark notifications as read.
- Check for network connectivity issues if requests fail to reach the Zammad server.
Links
- Zammad API Documentation - Mark All As Read - Official documentation for the 'Mark All As Read' endpoint in Zammad's online notifications API.