Overview
The "Eskom" node is designed to interact with the Eskom API, specifically for checking API allowance (i.e., how many requests you have left or your current usage status). This is useful in scenarios where you need to monitor your API quota before making further requests, helping to avoid hitting rate limits and ensuring smooth automation workflows. For example, you might use this node at the start of a workflow to decide whether to proceed with data-intensive operations based on your remaining API allowance.
Properties
| Name | Type | Meaning |
|---|---|---|
| Simplify | Boolean | If enabled, the output will be simplified for easier consumption. Useful for quick checks or when only essential information is needed. |
Output
- The node outputs a
jsonfield containing the result of the "Check allowance" operation from the Eskom API. - The structure typically includes information about your current API usage and remaining allowance.
- If "Simplify" is enabled, the output may be condensed to show only the most relevant fields.
Note: The exact structure of the output depends on the Eskom API's response for the allowance check endpoint.
Dependencies
- External Service: Requires access to the Eskom API.
- Credentials: An API key or credentials named
eskomApimust be configured in n8n for authentication.
Troubleshooting
Missing Credentials:
Error Message: "No credentials found for 'eskomApi'"
Resolution: Ensure that valid Eskom API credentials are set up in n8n under the nameeskomApi.API Limit Exceeded:
Error Message: May receive an error or empty data if the API limit is reached.
Resolution: Check your API usage and wait until your quota resets, or request a higher limit from Eskom.Invalid Response Structure:
Error Message: Unexpected output or missing fields.
Resolution: Verify that the Eskom API is operational and returning expected data. Double-check the "Simplify" option if output seems incomplete.