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
The node allows managing organizations within the Binalyze AIR platform, specifically enabling or disabling the "shareable deployment" feature for a selected organization. This feature likely controls whether an organization's deployment can be shared externally or across different environments.
A practical use case is when an administrator wants to toggle the shareable deployment status of an organization to control access or distribution of deployment configurations. For example, enabling shareable deployment might allow multiple teams to use the same deployment setup, while disabling it restricts sharing for security or compliance reasons.
Properties
| Name | Meaning |
|---|---|
| Organization | The target organization to update. Can be selected from a list, specified by ID, or by name. |
| Shareable Deployment Status | Boolean flag to enable (true) or disable (false) the shareable deployment feature. |
Output
The node outputs JSON data representing the updated organization resource after changing the shareable deployment status. This output typically includes the organization's details reflecting the new configuration.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR platform.
- The node depends on the Binalyze AIR API endpoints related to organizations.
- Proper network connectivity and permissions to modify organization settings are necessary.
Troubleshooting
- Invalid Organization ID: If specifying the organization by ID, ensure it is a positive number or zero (for the default organization). An invalid ID format will cause validation errors.
- Authentication Errors: Missing or incorrect API credentials will prevent the node from executing successfully.
- Permission Denied: The authenticated user must have sufficient rights to update organization settings; otherwise, the API will reject the request.
- API Connectivity Issues: Network problems or API downtime can cause execution failures.
- Unknown Resource Error: If the resource parameter is incorrectly set, the node throws an error indicating an unknown resource.
To resolve these issues, verify input parameters, check API credentials, confirm user permissions, and ensure stable network connectivity.
Links and References
- Binalyze AIR Official Documentation (for API and organization management)
- n8n Documentation on Creating Custom Nodes