Actions32
- Automatic Power Control Actions
- Dedicated Server Actions
- DNS Secondary Actions
- Network Boot Actions
- Network Diagnostic Actions
- Remote Access Control Actions
- Reset Actions
- Reverse DN Actions
- Security Scan Actions
Security Scan → List Security Scans
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage security scans on dedicated servers. Specifically, the "List Security Scans" operation retrieves a list of all security scans associated with a given server IP address. This is useful for monitoring and auditing security scan activities on your dedicated servers.
Practical scenarios include:
- Automatically fetching recent or historical security scan data for compliance reporting.
- Integrating security scan status checks into automated workflows to trigger alerts or remediation steps.
- Aggregating security scan results from multiple servers for centralized security management.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server for which to list security scans (required). |
| Response Format | The format in which the API response should be returned. Options: JSON, XML. |
Output
The output contains a JSON object representing the list of security scans retrieved from the Ikoula API for the specified server IP. The structure depends on the API response but generally includes details such as scan IDs, dates, statuses, and other metadata related to each security scan.
If the response format is set to XML, the raw XML string is returned inside the data field of the JSON output.
Example output snippet (in JSON mode):
{
"json": {
"scans": [
{
"id": 123,
"date": "2024-01-01 12:00:00",
"status": "completed",
...
},
...
]
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Ikoula Dedicated Server API.
- The node uses HTTPS requests to the Ikoula API endpoint (default:
https://api.ikoula.com). - The password is encrypted using RSA public key encryption before transmission.
- No additional external dependencies beyond standard n8n HTTP request helpers.
Troubleshooting
No credentials provided!
This error occurs if the required API authentication credentials are not configured. Ensure you have set up the necessary API key credential in n8n.Invalid Server IP or missing parameter
TheServer IPproperty is mandatory. Make sure it is correctly set and corresponds to a valid dedicated server managed by your Ikoula account.API response errors
If the API returns an error (e.g., unauthorized, not found), verify that your credentials are correct and that the server IP exists and is accessible.Response format issues
If you select XML format, ensure your downstream nodes can handle XML strings appropriately.
Links and References
- Ikoula Dedicated Server API Documentation (general reference for API endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)