Ikoula Plesk Managed API icon

Ikoula Plesk Managed API

Interact with Ikoula Plesk Managed API for managed Plesk hosting services. Developed by Ascenzia - www.ascenzia.fr

Overview

This node integrates with the Ikoula Plesk Managed API to manage Plesk hosting services. It allows users to list all Plesk managed services or retrieve details of a specific Plesk managed service subscription. This is useful for administrators or developers who want to automate monitoring, management, or reporting tasks related to their Plesk hosting environments.

Practical examples:

  • Automatically fetching a list of all Plesk managed services to display in a dashboard.
  • Retrieving detailed information about a particular Plesk subscription to trigger alerts or update records in other systems.

Properties

Name Meaning
Response Format The format of the API response. Options: JSON (default) or XML.

Output

The node outputs an array of items where each item contains a json field representing the API response:

  • If the response format is JSON, the json field contains the parsed JSON object returned by the API.
  • If the response format is XML, the json field contains the raw XML string under a data property (as a string).
  • In case of errors and if "Continue On Fail" is enabled, the output will contain an error message inside the json.error field.

No binary data is output by this node.

Dependencies

  • Requires an API key credential with email, password, and optionally a custom API URL for authentication.
  • Uses RSA public key encryption to encrypt the password before sending it to the API.
  • Makes HTTP GET requests to the Ikoula API endpoint (https://api.ikoula.com by default).

Troubleshooting

  • No credentials provided!
    This error occurs if the required API credentials are missing. Ensure that valid credentials are configured in n8n before running the node.

  • HTTP request failures:
    Network issues, invalid credentials, or incorrect subscription IDs can cause HTTP errors. Verify API credentials, subscription IDs, and network connectivity.

  • Response format issues:
    If XML is selected as the response format, downstream nodes expecting JSON may fail. Consider converting XML to JSON if needed.

  • Encryption errors:
    The node uses RSA encryption for the password. If the encryption fails due to malformed keys or environment restrictions, the node will throw an error.

Links and References

Discussion