Actions36
- Array Actions
- Disk Actions
- Docker Actions
- Notification Actions
- System Actions
- VM Actions
Notification → Archive
AI-generatedSummary
Archives a single Unraid notification by ID, moving it from unread to the archive via the Unraid GraphQL API, and returns the archived notification's id, title and type.
Inputs
- Notification ID (required) — Prefixed ID of the notification to archive (e.g. notification:abc123). Use the Notification Get Many operation to find IDs.
- Maximum Control Level — Optional cap on what this node may do: Use Credential Default (default), Read, Control or Full. It can only narrow the credential's limit, never raise it. Archive needs at least Control, so Read blocks the operation with an error before any request is sent.
Output shape
One item per input item, with the archived notification's JSON: id, title and type (the type should reflect its new archived state).
The result is an empty object if the API returns nothing. If the API returns GraphQL errors and no data, the node throws. With Continue On Fail enabled, the item instead contains an error message. Each output item is paired to its input item.
Examples
Example 1: Archive a notification after a workflow has handled it, using an ID from a previous Get Many step.
Resource: Notification; Operation: Archive; Notification ID: {{ $json.id }}; Maximum Control Level: Use Credential Default (the credential must be set to Control or Full).