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 various resources, including organizations. Specifically, the "Check Name Exists" operation under the "Organization" resource allows users to verify if an organization with a given name already exists in the system. This is useful for workflows that need to prevent duplicate organization entries or validate organization names before proceeding with further actions.
Practical examples:
- Before creating a new organization record, check if the name is already taken to avoid duplicates.
- Validate user input in automation flows where organization names are provided dynamically.
- Use as a conditional step in workflows to branch logic based on the existence of an organization.
Properties
| Name | Meaning |
|---|---|
| Organization Name to Check | The exact name of the organization to verify for existence. This is a required string input where you enter the organization name you want to check. |
Output
The node outputs JSON data indicating whether the specified organization name exists. The structure typically includes a boolean or status field confirming existence, along with any relevant metadata about the organization if found.
If the node supports binary data output (not indicated here), it would generally relate to associated files or attachments linked to the organization, but this operation focuses on existence checking and thus primarily outputs JSON.
Dependencies
- Requires an active connection to the Binalyze AIR API via an API key credential configured in n8n.
- The node depends on the Binalyze AIR service being accessible and the API credentials having permissions to query organization data.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems can prevent reaching the Binalyze AIR API.
- Providing an empty or malformed organization name may result in errors or false negatives.
Error messages:
"Unknown resource: organizations"— indicates the resource parameter was not set correctly; ensure "Organization" is selected.- Authentication errors suggest checking the API key credential configuration.
- If the node returns no results, verify the organization name spelling and case sensitivity.
Links and References
- Binalyze AIR Official Documentation (for API details and usage)
- n8n Documentation on Creating Custom Nodes