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
Network Boot → List Netboots
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage network boot (netboot) operations for dedicated servers. Specifically, the "List Netboots" operation retrieves a list of netboot requests associated with a given server IP address.
Common scenarios where this node is beneficial include:
- Monitoring all netboot requests made on a specific dedicated server.
- Auditing or tracking netboot activity for troubleshooting or compliance.
- Integrating netboot status checks into automated workflows for server management.
Practical example:
- A user wants to fetch and display all netboot requests for a particular server to verify if a recent netboot request was successfully registered.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server for which to list netboot requests. |
| Response Format | The format in which the API response should be returned. Options: JSON, XML. |
Output
The node outputs an array of items, each containing a json field with the data returned by the Ikoula API for the list of netboots. The structure depends on the API response but typically includes details about each netboot request such as IDs, statuses, timestamps, and related metadata.
If the response format is set to XML, the raw XML string is returned inside the data property of the json output.
No binary data output is produced by this operation.
Dependencies
- Requires valid credentials for the Ikoula API, including email, password, and optionally a custom API URL.
- The password is encrypted using RSA public key encryption before being sent.
- The node makes HTTP requests to the Ikoula API endpoint, defaulting to
https://api.ikoula.com. - Proper configuration of the API credentials within n8n is necessary for successful authentication.
Troubleshooting
No credentials provided!
This error occurs if the node is executed without configured Ikoula API credentials. Ensure that the API credentials are properly set up in n8n.HTTP request failures
Network issues, incorrect server IP, or invalid parameters can cause HTTP errors. Verify the server IP is correct and reachable, and check the API documentation for valid parameter values.Unexpected response format
If the response format is set to XML but downstream nodes expect JSON, parsing errors may occur. Choose the response format according to your workflow needs.Encryption errors
The node encrypts the password using a hardcoded RSA public key. If this key changes or becomes invalid, authentication will fail. Contact the API provider if authentication issues persist.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)