Actions7
Overview
The node integrates with the Turnkey API to manage cryptocurrency wallets and related operations within an organization. It supports various wallet-related actions such as retrieving wallet details, creating wallets and accounts, signing transactions, and listing wallets.
The Get Wallet operation specifically fetches detailed information about a particular wallet identified by its Wallet ID within a given organization.
Common scenarios:
- Retrieving wallet metadata or status for auditing or display purposes.
- Integrating wallet data into automated workflows for financial or blockchain applications.
- Fetching wallet info before performing further operations like account creation or transaction signing.
Practical example:
A user wants to retrieve the details of a specific wallet in their Turnkey-managed organization to verify its configuration or balance before initiating transfers or other blockchain activities.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Key" |
| Organization ID | The unique identifier of the Turnkey organization under which the wallet exists |
| Wallet ID | The unique identifier of the wallet to retrieve |
Output
The output is a JSON object containing the wallet details as returned by the Turnkey API's getWallet method. This typically includes metadata about the wallet such as its ID, name, associated accounts, creation timestamps, and other relevant properties managed by Turnkey.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Turnkey API.
- Uses the Turnkey client library (
@turnkey/http) to communicate with the Turnkey service. - The node expects the Turnkey API base URL and credentials to be configured properly in n8n.
Troubleshooting
Common issues:
- Missing or invalid API key credential will cause authentication failures.
- Incorrect Organization ID or Wallet ID will result in errors or empty responses.
- Network connectivity issues can prevent communication with the Turnkey API.
Error messages:
"Failed to execute operation: <error message>"indicates an error during the API call or parameter handling."Operation getWallet not supported"would occur if the operation parameter is incorrectly set (not applicable here since "getWallet" is supported).
Resolutions:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Double-check the Organization ID and Wallet ID values for correctness.
- Ensure network access to the Turnkey API endpoint is available from the n8n environment.
Links and References
- Turnkey API Documentation (generic placeholder, replace with actual URL)
- n8n Documentation on Credentials
- Turnkey Client Library on npm