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 → Get Netboot Status
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage network boot (netboot) operations among other server management tasks. Specifically, for the Network Boot resource and the Get Netboot Status operation, it retrieves the current status of a specific netboot request on a dedicated server identified by its IP address.
Typical use cases include:
- Monitoring the progress or result of a netboot request initiated on a dedicated server.
- Automating workflows that depend on the netboot status, such as triggering subsequent configuration steps once a netboot completes.
- Integrating server provisioning or recovery processes where network boot status is critical.
Example: After requesting a netboot on a server, you can use this node to periodically check the status of that netboot by providing the server IP and netboot ID, receiving detailed status information in response.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which the netboot status is queried. |
| Netboot ID | The unique identifier of the netboot request whose status you want to retrieve. |
| Response Format | The format of the API response; options are JSON or XML. |
Output
The node outputs the API response under the json field. This response contains the details about the netboot status for the specified netboot ID on the given server. The exact structure depends on the API but typically includes fields such as status codes, timestamps, and descriptive messages about the netboot process.
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 an API key credential for authenticating with the Ikoula Dedicated Server API.
- The node uses HTTPS requests to the Ikoula API endpoint (
https://api.ikoula.comby default). - The password used for authentication is encrypted using RSA public key encryption before sending.
- No additional external dependencies beyond standard n8n HTTP request helpers.
Troubleshooting
No credentials provided!
This error occurs if the required API authentication credentials are missing. Ensure you have configured valid API credentials in n8n before running the node.Invalid Server IP or Netboot ID
If the server IP or netboot ID is incorrect or does not exist, the API may return an error or empty response. Verify these inputs carefully.API Response Errors
Network issues, invalid credentials, or API rate limits may cause errors. Check your network connectivity and API usage limits.Response Format Issues
If you select XML format but downstream nodes expect JSON, parsing errors may occur. Choose the response format according to your workflow needs.
Links and References
- Ikoula Dedicated Server API Documentation (general reference for API endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n)