Voltage icon

Voltage

Interact with Voltage API
Join our community

Actions18

Overview

This node interacts with the Voltage API to retrieve information about lines of credit within an organization. Specifically, the "Get All" operation for the "Line of Credit" resource fetches multiple lines of credit associated with a given organization, optionally supporting pagination through limit and offset filters.

Use cases include:

  • Retrieving all lines of credit available in an organization for reporting or monitoring.
  • Integrating line of credit data into workflows that require financial credit information.
  • Automating audits or reconciliations involving credit lines.

Example: A finance team could use this node to pull all active lines of credit from their Voltage account to update internal dashboards or trigger alerts when new credit lines are added.

Properties

Name Meaning
Organization ID The unique identifier of the organization whose lines of credit you want to retrieve.
Filters Optional parameters to refine the results:
- Limit Maximum number of results to return (pagination).
- Offset Number of results to skip before starting to collect the output (pagination).

Output

The node outputs an array of JSON objects, each representing a line of credit retrieved from the Voltage API. Each object contains detailed information about a single line of credit as returned by the API.

The output structure corresponds directly to the Voltage API's line of credit data model, which typically includes fields such as line ID, credit limits, status, and related metadata.

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Voltage API.
  • The node uses the Voltage API SDK internally to perform requests.
  • The user must configure the node with valid credentials and specify the correct organization ID.
  • Network connectivity to the Voltage API endpoint is required.

Troubleshooting

  • Authentication Errors (401): Occur if the API key is invalid or missing. Verify that the API key credential is correctly configured.
  • Permission Errors (403): Indicate insufficient permissions for the API key. Ensure the key has access rights to the organization's data.
  • Not Found Errors (404): May happen if the organization ID does not exist or is incorrect. Double-check the organization ID parameter.
  • Validation Errors (422): Result from invalid request parameters. Review filter values like limit and offset for correctness.
  • Server Errors (5xx): Temporary issues on the Voltage API side. Retry after some time or contact support.
  • Non-JSON Response: If the API returns a non-JSON response, it often signals authentication or configuration problems.

When errors occur, the node can either stop execution or continue on failure depending on the workflow settings, providing error details in the output.

Links and References

Discussion