Actions17
- Folder Actions
- Plugin Actions
- Policy Actions
- Scan Actions
Overview
This node integrates with the Nessus API to manage various security scanning resources, including folders. Specifically, the "Folder Delete" operation allows users to delete a folder within their Nessus environment by specifying the folder's name or ID. This is useful for cleaning up unused or obsolete folders that organize scans, policies, or other assets.
Practical scenarios include:
- Automating cleanup of temporary or test folders after scans are completed.
- Managing folder lifecycle as part of a larger security orchestration workflow.
- Ensuring compliance by removing folders that contain outdated or irrelevant scan data.
Properties
| Name | Meaning |
|---|---|
| Folder Name or ID | Select the folder to delete. Choose from a dynamically loaded list of existing folders or specify an ID using an expression. |
Output
The node outputs a JSON object representing the response from the Nessus API after attempting to delete the specified folder. The exact structure depends on the API but typically includes confirmation of deletion or error details.
If an error occurs during deletion and the node is configured to continue on failure, the output will contain an error field with the error message.
No binary data output is involved in this operation.
Example output JSON (success):
{
"message": "Folder deleted successfully",
"id": 12345
}
Example output JSON (failure with continueOnFail enabled):
{
"error": "Folder not found"
}
Dependencies
- Requires an active connection to the Nessus API via an API key credential configured in n8n.
- The node uses internal methods to load available folders dynamically for selection.
- Proper permissions on the Nessus account are necessary to delete folders.
Troubleshooting
Common issues:
- Attempting to delete a folder that does not exist or has already been deleted.
- Insufficient permissions to delete folders in the Nessus account.
- Network or authentication errors connecting to the Nessus API.
Error messages and resolutions:
"Folder not found": Verify the folder ID or name is correct and exists."Unauthorized"or authentication errors: Check that the API key credential is valid and has appropriate permissions."Failed to load folders"when selecting folder: Ensure the API connection is working and the user has permission to list folders.
To handle errors gracefully, enable the node's "Continue On Fail" option to capture error messages in the output without stopping the workflow.