Nessus

Overview

This node interacts with the Nessus API to manage folders within a Nessus environment. Specifically, the "Folder - Create" operation allows users to create a new folder in their Nessus instance. This is useful for organizing scans, policies, or other resources into logical groups.

Practical scenarios include:

• Automatically creating folders to categorize scans by project or department.
• Structuring scan results and policies for easier management and access control.
• Integrating folder creation into automated workflows that provision Nessus resources dynamically.

Properties

Output

The output JSON contains the response from the Nessus API after attempting to create the folder. Typically, this will include details about the newly created folder such as its ID, name, and possibly metadata returned by the API.

Example output structure (simplified):

{
  "id": 123,
  "name": "My New Folder",
  "type": "user"
}

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the Nessus API via an API key credential configured in n8n.
• The node depends on the NessusApi helper class to communicate with the Nessus service.
• Proper permissions in the Nessus account are necessary to create folders.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Insufficient permissions in Nessus may result in authorization errors when creating folders.
  • Providing an empty or invalid folder name will likely cause the API to reject the request.

• Error messages:

  • Errors thrown by the node will include messages from the Nessus API, such as "Unauthorized", "Forbidden", or validation errors related to the folder name.
  • If the node fails to load folder options or perform the create operation, it will throw a descriptive error indicating the failure reason.

• Resolution tips:

  • Verify that the API key credential is correctly set up and has appropriate permissions.
  • Ensure the folder name is provided and meets any naming requirements imposed by Nessus.
  • Check network connectivity to the Nessus server.

Links and References

• Nessus API Documentation
• n8n Documentation on Credentials
• n8n Expressions Guide