Voltage icon

Voltage

Interact with Voltage API
Join our community

Actions18

Overview

This node integrates with the Voltage API to manage cryptocurrency wallets within an organization. Specifically, the Wallet - Get operation retrieves detailed information about a single wallet by its ID and organization ID.

Common scenarios where this node is beneficial include:

  • Fetching wallet details for auditing or reporting purposes.
  • Integrating wallet data into workflows that require wallet metadata.
  • Verifying wallet existence or status before performing transactions.

Example use case:
A finance team wants to automatically retrieve wallet balances and metadata from their Voltage-managed wallets to update internal dashboards or trigger alerts if certain thresholds are met.

Properties

Name Meaning
Organization ID The unique identifier of the organization that owns the wallet.
Wallet ID The specific identifier of the wallet to retrieve information for.

Output

The node outputs a JSON object representing the wallet's details as returned by the Voltage API. This typically includes wallet metadata such as wallet ID, balance, currency, creation date, and other relevant wallet attributes.

The output structure corresponds directly to the Voltage API's wallet object schema.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Voltage API.
  • The node uses the Voltage API SDK client configured with the API key, base URL, and timeout settings.
  • Proper configuration of the API key and access permissions in n8n credentials is necessary.

Troubleshooting

Common Issues

  • Authentication errors: If the API key is invalid or lacks required permissions, the node will fail with authentication errors.
  • Invalid organization or wallet ID: Providing incorrect IDs will result in "Not Found" errors.
  • API response parsing errors: If the API returns non-JSON responses (e.g., due to server issues), the node will report parsing failures.

Error Messages and Resolutions

Error Message Cause Resolution
Authentication Error (401): Invalid API key or credentials. Invalid or missing API key Verify and update the API key credential in n8n.
Permission Error (403): Access denied. Check your API key permissions. Insufficient API key permissions Ensure the API key has rights to access wallet data.
Not Found (404): Organization, environment, or resource not found. Incorrect organization or wallet ID Confirm the organization ID and wallet ID are correct and exist in Voltage.
Validation Error (422): The request data is invalid. Please check your parameters. Malformed or missing required parameters Double-check input parameters for correctness and completeness.
API returned non-JSON response (Status: XXX). Check your API credentials and organization ID. Server error or authentication issue causing bad response Verify API credentials and organization ID; retry later if server issues persist.

Links and References

Discussion