Ikoula API CS icon

Ikoula API CS

Interact with Ikoula CloudStack API for billing and consumption. Developed by Ascenzia - www.ascenzia.fr

Overview

This node interacts with the Ikoula CloudStack API to retrieve billing and consumption information related to a user's subscription. Specifically, the "Get Current Consumption" operation fetches the current resource usage data for a given subscription ID.

Common scenarios where this node is beneficial include:

  • Monitoring real-time cloud resource consumption to manage costs.
  • Integrating current usage data into dashboards or reports.
  • Automating alerts or workflows based on consumption thresholds.

For example, a user can configure this node to periodically pull the current consumption of their cloud resources and trigger notifications if usage exceeds a budget limit.

Properties

Name Meaning
Subscription ID The unique numeric identifier of the subscription whose current consumption is retrieved.
Response Format The format in which the API response is returned. Options: JSON, XML

Output

The node outputs an array of items, each containing a json field with the API response data:

  • If the response format is JSON, the json field contains the parsed JSON object representing the current consumption details.
  • If the response format is XML, the json field contains the raw XML string under a data property.

The output structure corresponds directly to the API's response for current consumption, including usage metrics and related billing information.

Dependencies

  • Requires valid credentials for the Ikoula CloudStack 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 GET requests to the Ikoula API endpoint.
  • The user must configure the node with appropriate API authentication credentials.

Troubleshooting

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

  • HTTP request failures
    Network issues, incorrect subscription IDs, or invalid API URLs may cause request errors. Verify the subscription ID is correct and the API endpoint is reachable.

  • Response format issues
    If the selected response format does not match the expected content type, parsing errors may occur. Choose JSON for easier integration unless XML is specifically needed.

  • Continue On Fail behavior
    If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.

Links and References

Discussion