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
Reset → List Resets
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage server reset requests among other server-related operations. Specifically, for the "Reset" resource and the "List Resets" operation, it retrieves a list of reset requests made on a dedicated server identified by its IP address.
Common scenarios where this node is beneficial include:
- Monitoring all reset requests made to a specific dedicated server.
- Automating workflows that need to track or audit server resets.
- Integrating server reset status checks into broader IT infrastructure management processes.
For example, an IT administrator could use this node to automatically fetch and log all reset requests for a server after maintenance windows or before deploying new configurations.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server for which to list reset requests. |
| Response Format | The format in which the API response should be returned. Options: JSON, XML. |
Output
The node outputs the API response under the json field. For the "List Resets" operation, this will typically be a JSON object (or XML if selected) containing the list of reset requests associated with the specified server IP.
The exact structure depends on the Ikoula API but generally includes details such as reset request IDs, timestamps, statuses, and possibly additional metadata about each reset.
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 (
https://api.ikoula.comby default). - 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 set up correctly in n8n before running the node.API request failures
If the API returns errors (e.g., invalid server IP, unauthorized access), verify that the server IP is correct and that the credentials have sufficient permissions.Incorrect response format
Selecting XML format requires handling XML output downstream. If JSON is preferred, ensure the "Response Format" property is set accordingly.Network issues
Connectivity problems to the Ikoula API endpoint can cause timeouts or failed requests. Check network settings and firewall rules.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n Documentation for setting up credentials and HTTP request nodes
If you need details on other operations or resources, feel free to ask!