Actions99
- InterACT Actions
- Notification Actions
- Organization Actions
- Task Actions
- Policy Actions
- Repository Actions
- Setting Actions
- Triage Rule Actions
- User Actions
- Acquisition Actions
- API Token Actions
- Asset Actions
- Auto Asset Tag Actions
- Baseline Actions
- Case Actions
- Evidence Actions
Overview
This node integrates with the Binalyze AIR platform to manage user notifications. Specifically, the "Mark as Read by ID" operation allows users to mark a particular notification as read by specifying its unique identifier. This is useful in workflows where you want to programmatically acknowledge or clear notifications after processing them, helping maintain an organized notification system.
Practical examples include:
- Automatically marking security alerts as read once they have been reviewed.
- Clearing notifications related to completed tasks or acquisitions.
- Integrating notification management into broader incident response workflows.
Properties
| Name | Meaning |
|---|---|
| Notification | The specific notification to mark as read. Can be selected from a searchable list of existing notifications or provided directly by its ID (must contain only letters, numbers, hyphens, and underscores). |
Output
The node outputs JSON data representing the result of the "mark as read" operation on the specified notification. This typically includes confirmation details such as the notification ID and its updated status. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR platform.
- The node depends on the Binalyze AIR API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Notification ID: If the notification ID contains invalid characters (anything other than letters, numbers, hyphens, or underscores), the node will reject it. Ensure the ID matches the required pattern.
- Notification Not Found: If the specified notification ID does not exist or is inaccessible, the operation may fail. Verify the notification exists and that the API credentials have sufficient permissions.
- Authentication Errors: If the API key is missing, expired, or incorrect, the node will fail to authenticate. Check the API key configuration.
- API Connectivity Issues: Network problems or API downtime can cause failures. Confirm network connectivity and API service status.
Links and References
- Binalyze AIR Official Documentation (for API details and notification management)
- n8n Documentation (for general node usage and credential setup)