Voltage icon

Voltage

Interact with Voltage API
Join our community

Actions18

Overview

This node interacts with the Voltage API to retrieve wallet-related data within an organization. Specifically, the "Wallet - Get All" operation fetches all wallets associated with a given organization, optionally applying filters such as pagination (limit and offset).

Common scenarios where this node is beneficial include:

  • Retrieving a list of all wallets for financial reporting or auditing.
  • Integrating wallet data into workflows that require wallet details for further processing.
  • Monitoring wallet statuses or balances by fetching comprehensive wallet lists.

Practical example:

  • A user wants to synchronize all wallets from their Voltage account into another system daily. They can use this node to get all wallets and then process each wallet's data accordingly.

Properties

Name Meaning
Organization ID The unique identifier of the organization whose wallets you want to retrieve.
Filters Optional parameters to refine the results:
- Limit Maximum number of wallet results to return (pagination).
- Offset Number of wallet results to skip before starting to collect the output (pagination).
- Wallet ID Filter (not applicable here) (Present in filters but not used for wallet getAll operation)
- Payment Statuses (not applicable here) Only relevant for payment resource filters, ignored here.
- Payment Kind (not applicable here) Only relevant for payment resource filters, ignored here.
- Payment Direction (not applicable here) Only relevant for payment resource filters, ignored here.
- Start Date (not applicable here) Only relevant for other operations, ignored here.
- End Date (not applicable here) Only relevant for other operations, ignored here.
- Sort Key (not applicable here) Only relevant for other operations, ignored here.
- Sort Order (not applicable here) Only relevant for other operations, ignored here.

Note: For the "Wallet - Get All" operation, only limit and offset filters are applied.

Output

The node outputs an array of wallet objects in the json field, each representing a wallet retrieved from the Voltage API. Each wallet object contains detailed information about a wallet within the specified organization.

Output structure example (simplified):

{
  "id": "string",
  "name": "string",
  "balance": {
    "btc": "number",
    "usd": "number"
  },
  "created_at": "ISO8601 timestamp",
  "updated_at": "ISO8601 timestamp",
  // ... other wallet-specific fields
}

If multiple wallets are returned, each wallet is output as a separate item in the node's output array.

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 communicate with the Voltage service.
  • Requires proper configuration of the API base URL and timeout settings via credentials.
  • The user must provide a valid Organization ID to scope the wallet retrieval.

Troubleshooting

Common Issues

  • Authentication errors: If the API key is invalid or missing, the node will fail to authenticate.
  • Invalid Organization ID: Providing a wrong or non-existent organization ID will result in "Not Found" errors.
  • API rate limits or server errors: The Voltage API may return server errors or rate limit responses, causing failures.
  • Incorrect filter values: Using invalid types or out-of-range values for limit or offset may cause validation errors.

Error Messages and Resolutions

  • Validation Error (422): Indicates invalid request data. Check that the Organization ID and filters are correctly formatted.
  • Authentication Error (401): Invalid API key or credentials. Verify the API key and credential setup.
  • Permission Error (403): Access denied due to insufficient permissions. Ensure the API key has rights to access wallet data.
  • Not Found (404): Organization or resource not found. Confirm the Organization ID exists and is correct.
  • Server Error (5xx): Voltage API is experiencing issues. Retry after some time or contact support.
  • Failed to parse response as JSON: Usually indicates authentication issues or incorrect Organization ID. Double-check credentials and input parameters.

The node supports "Continue on Fail" mode, which allows workflow execution to continue even if some items fail, returning error details in the output.

Links and References

Discussion