Ikoula API Dedicated Server icon

Ikoula API Dedicated Server

Interact with Ikoula Dedicated Server API. Developed by Ascenzia - www.ascenzia.fr

Actions32

Automatic Power Control → Get Reboot Status

AI-generated

Overview

This node interacts with the Ikoula Dedicated Server API to manage Automatic Power Control (APC) reboots. Specifically, the "Get Reboot Status" operation retrieves the current status of a previously requested APC reboot for a dedicated server identified by its IP address and a reboot ID.

Typical use cases include:

  • Monitoring the progress or completion status of an APC reboot request.
  • Integrating server power management status checks into automated workflows.
  • Alerting or logging reboot statuses for audit or operational purposes.

For example, after requesting a reboot on a server, you can use this node operation to periodically check if the reboot has completed successfully or if it is still in progress.

Properties

Name Meaning
Server IP The IP address of the dedicated server on which the APC reboot was requested.
Reboot ID The unique identifier of the APC reboot request whose status you want to retrieve.
Response Format The format of the API response; options are JSON or XML.

Output

The node outputs a JSON object representing the status of the APC reboot request. The exact structure depends on the API response but typically includes details such as:

  • Current state of the reboot (e.g., pending, in progress, completed, aborted).
  • Timestamps related to the reboot request.
  • Any messages or error information returned by the API.

If the response format is set to XML, the raw XML string is returned inside the json.data field as a string.

No binary data output is produced by this operation.

Dependencies

  • Requires valid credentials for the Ikoula API, including an 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, so network connectivity to the API service is required.
  • No additional external dependencies beyond standard n8n helpers and Node.js crypto module.

Troubleshooting

  • No credentials provided!
    This error occurs if the node is executed without proper Ikoula API credentials configured. Ensure that the API authentication details are correctly set up in n8n credentials.

  • Invalid Server IP or Reboot ID
    If the server IP or reboot ID is incorrect or does not exist, the API may return an error or empty result. Verify these inputs carefully.

  • API Response Errors
    The API might return errors due to rate limits, invalid parameters, or server issues. Check the error message returned in the node output for guidance.

  • Network Issues
    Failure to reach the API endpoint could be caused by network problems or incorrect API URL configuration.

To resolve most issues, verify credentials, input parameters, and network connectivity. Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

Discussion