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 manages security policies within the Binalyze AIR platform, specifically allowing users to update the priorities of multiple policies in bulk. This is useful in scenarios where an organization needs to reorder or reprioritize its security policies to reflect changing risk assessments or operational requirements.
For example, a security administrator might use this node to set the priority of critical policies higher than others so that alerts or actions triggered by those policies are handled first.
Properties
| Name | Meaning |
|---|---|
| Policy Priorities | A JSON string representing an array of policy objects, each containing _id (policy ID) and priority fields. Example: [{"_id": "policy1", "priority": 1}]. This defines the new priorities for the specified policies. |
Output
The node outputs JSON data reflecting the result of the update operation on the policies' priorities. The exact structure depends on the API response from the Binalyze AIR service but typically includes confirmation of updated policies and their new priority values.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Binalyze AIR API.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The node relies on the external Binalyze AIR service to perform policy management operations.
Troubleshooting
- Invalid JSON Format: If the "Policy Priorities" input is not valid JSON or does not conform to the expected array of objects with
_idandpriority, the node will likely throw a parsing or validation error. Ensure the JSON is correctly formatted and includes all required fields. - Authentication Errors: Failure to provide valid API credentials or expired tokens will cause authorization errors. Verify that the API key credential is correctly configured and has sufficient permissions.
- Unknown Resource Error: If the resource parameter is incorrectly set or missing, the node throws an error indicating an unknown resource. Make sure the resource is set to "policies" for this operation.
- API Limitations or Network Issues: Network connectivity problems or API rate limits may cause failures. Check network access and API usage quotas.
Links and References
- Binalyze AIR Official Documentation — For detailed API and policy management information.
- n8n Documentation — For guidance on configuring credentials and using custom nodes.