Actions17
- Folder Actions
- Plugin Actions
- Policy Actions
- Scan Actions
Overview
This node interacts with the Nessus vulnerability scanning API, specifically enabling operations on scans such as copying an existing scan. The "Copy" operation duplicates a selected scan, optionally renaming it and placing it into a specified destination folder.
Common scenarios for this node include:
- Quickly duplicating a configured scan to run similar scans with minor adjustments.
- Organizing scans by copying them into different folders for better management.
- Automating scan duplication as part of a larger security workflow.
For example, a user might copy a baseline network scan, rename it to reflect a new target environment, and place it in a dedicated folder for that environment, all within an automated workflow.
Properties
| Name | Meaning |
|---|---|
Scan Name or ID (scanId) |
Selects the scan to copy. You can choose from a list of existing scans or specify an ID using an expression. |
New Name (newName) |
Optional new name for the copied scan. If left empty, the original scan's name is used with a "Copy" suffix. |
Destination Folder Name or ID (destinationFolderId) |
Optional destination folder where the copied scan will be placed. Choose from a list or specify an ID using an expression. |
Output
The node outputs JSON data representing the result of the copy operation. This typically includes details about the newly created scan object returned by the Nessus API, such as its ID, name, status, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Nessus API via an API key credential configured in n8n.
- The node depends on the
NessusApihelper class to communicate with the Nessus service. - Proper permissions on the Nessus server are needed to perform scan copy operations.
- Network connectivity to the Nessus instance must be established.
Troubleshooting
Common issues:
- Invalid or missing scan ID: Ensure the scan to copy exists and the ID is correct.
- Insufficient permissions: The API key used must have rights to read and create scans.
- Destination folder ID invalid or inaccessible: Verify the folder exists and is accessible.
- Network or authentication errors connecting to Nessus API.
Error messages:
"Failed to load scans": Indicates inability to retrieve scans list; check API credentials and connectivity.- Errors during copy operation may include messages from the Nessus API indicating invalid parameters or permission issues.
Resolutions:
- Double-check input parameters, especially IDs.
- Confirm API credentials and permissions.
- Test connectivity to the Nessus server outside n8n if needed.
- Use expressions carefully to ensure valid values.