Actions113
- blocks Actions
- Get Block Details By Block Hash UTXOs
- List Transactions by Block Hash EVM
- List Transactions by Block Hash UTXOs
- List Transactions By Block Hash XRP
- List Transactions By Block Height XRP
- List Transactions by Block Height EVM
- List Transactions by Block Height UTXOs
- Get Block Details By Block Height UTXOs
- Get Block Details By Block Height EVM
- Get Block Details By Block Height XRP
- Get Block Details By Block Hash EVM
- Get Block Details By Block Hash XRP
- Get Last Mined Block EVM
- Get Last Mined Block UTXOs
- Get Latest Mined Block XRP
- List Latest Mined Blocks UTXOs
- List Latest Mined Blocks EVM
- List Latest Mined Blocks XRP
- HD Wallets Actions
- Sync HD Wallet (xPub, yPub, zPub)
- Derive And Sync New Receiving Addresses UTXO
- Derive And Sync New Change Addresses UTXO
- Derive And Sync New Receiving Addresses EVM
- Derive And Sync New Receiving Addresses XRP
- List Synced Addresses UTXO
- List Synced Addresses EVM
- List Synced Addresses XRP
- List HD Wallet (xPub, yPub, zPub) Transactions UTXO
- List HD Wallet (xPub, yPub, zPub) Transactions EVM
- List HD Wallet (xPub, yPub, zPub) Transactions XRP
- List HD Wallet (xPub, yPub, zPub) UTXOs
- Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub)
- Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM
- Get HD Wallet (xPub, yPub, zPub) Assets UTXO
- Get HD Wallet (xPub, yPub, zPub) Assets EVM
- Get HD Wallet (xPub, yPub, zPub) Assets XRP
- Get HD Wallet (xPub, yPub, zPub) Details UTXO
- Get HD Wallet (xPub, yPub, zPub) Details EVM
- Get HD Wallet (xPub, yPub, zPub) Details XRP
- List Synced HD Wallets (xPub, yPub, zPub)
- Activate HD Wallet (xPub, yPub, zPub)
- Delete Synced HD Wallet (xPub, yPub, zPub)
- address-latest Actions
- Utilities Actions
- simulate-transactions Actions
- addresses-latest Actions
- Get Address Balance Solana
- List Transactions By Address Solana
- Get Address Balance EVM
- Get Address Balance XRP
- Get Address Balance Kaspa
- List Confirmed Transactions By Address EVM
- List Transactions by Address XRP
- List Confirmed Transactions By Address UTXOs
- List Confirmed Transactions By Address Kaspa
- List Unconfirmed Transactions by Address UTXOs
- List Internal Transactions By Address EVM
- Get Next Available Nonce EVM
- List Confirmed Tokens Transfers By Address EVM
- addresses-historical Actions
- Get Address Balance UTXOs
- List Confirmed Transactions By Address EVM history
- List Confirmed Transactions By Address UTXO Historical
- List Unspent Transaction Outputs By Address UTXOs
- Sync Address
- List Synced Addresses
- Get Synced Address Tokens Transfer EVM
- Activate Synced Address
- Delete Synced Address
- List Synced Address Internal Transactions EVM
- List Tokens By Address Synced EVM
- blockchain-events Actions
- New Confirmed Coins Transactions
- New Unconfirmed Coins Transactions
- New Confirmed Tokens Transactions
- New Confirmed Coins Transactions And Each Confirmation
- New Confirmed Tokens Transactions And Each Confirmation
- Mined Transaction
- New Block
- List Blockchain Events Subscriptions
- Get Blockchain Event Subscription Details By Reference ID
- Delete Blockchain Event Subscription
- Activate Blockchain Event Subscription
- New Confirmed Internal Transactions
- New Confirmed Internal Transactions And Each Confirmation
- Crypto Transactions Actions
- Get Transaction Details By Transaction Hash Solana
- Get Transaction Details By Transaction Id Kaspa
- Get Transaction Details By Transaction Hash EVM
- Get Transaction Details By Transaction Hash UTXOs
- Get Transaction Details By Transaction Hash XRP
- List Internal Transaction Details by Transaction Hash EVM
- List Tokens Transfers By Transaction Hash EVM
- List Logs By Transaction Hash EVM
- Get Raw Transaction Data UTXOs
- contracts Actions
- blockchain-fees Actions
- broadcast-transactions Actions
- prepare-transactions Actions
- Market Data & Prices Actions
Overview
This node operation prepares a transaction from an address in an HD Wallet (using extended public keys like xPub, yPub, zPub) on EVM-compatible blockchains. It allows users to construct the necessary transaction data without exposing private keys, enabling secure transaction preparation for Ethereum and similar networks.
Common scenarios include:
- Preparing unsigned transactions for hardware wallets or external signing.
- Constructing transactions programmatically for smart contract interactions or token transfers.
- Integrating with wallet management systems that use extended public keys to derive addresses and prepare transactions.
Practical example:
A user wants to send tokens from an Ethereum address derived from their HD wallet's xPub key. They specify the blockchain (Ethereum), network (e.g., mainnet), recipient address, amount, and optionally fee parameters. The node returns the prepared transaction data ready for signing and broadcasting.
Properties
| Name | Meaning |
|---|---|
| blockchain | The target blockchain network (e.g., Ethereum, Binance Smart Chain). |
| network | Specific network within the blockchain (e.g., mainnet, testnet). |
| extendedPublicKey | The HD wallet extended public key (xPub, yPub, zPub) used to derive addresses. |
| type | The type of transaction or asset involved (specific meaning depends on API context). |
| context | Optional context string for correlating requests or tracking. |
| JSON Body (bodyParameters) | Collection of additional transaction details: |
| - additionalData | Extra data to include in the transaction (e.g., calldata for contracts). |
| - amount | Amount of cryptocurrency or tokens to send. |
| - nonce | Transaction nonce to ensure uniqueness. |
| - recipient | Address receiving the funds. |
| - sender | Address sending the funds (derived from extended public key). |
| - fee | Fee parameters collection (structure depends on blockchain specifics). |
| - transactionType | Type of transaction; options are: legacy-transaction, access-list-transaction, gas-fee-market-transaction. |
Output
The node outputs a JSON array where each item contains the prepared transaction data as returned by the Crypto APIs service. This typically includes all necessary fields to sign and broadcast the transaction externally, such as raw transaction hex, gas limits, fees, nonce, and other blockchain-specific details.
If binary data were involved (not indicated here), it would represent encoded transaction payloads or signatures, but this node focuses on JSON transaction preparation output.
Dependencies
- Requires an active connection to the Crypto APIs REST API service.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- No additional environment variables are explicitly required beyond standard API credential setup.
Troubleshooting
- Operation not found error: Occurs if the specified operation is incorrect or missing. Ensure the operation name matches exactly "Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM".
- Invalid or missing parameters: The node requires certain mandatory inputs like blockchain, network, and extended public key. Missing these will cause errors.
- API request failures: Network issues or invalid API credentials can cause request errors. Verify API key validity and network connectivity.
- Incorrect fee or transaction type: Providing unsupported fee structures or transaction types may result in API rejections. Use only supported options listed in properties.
- To resolve errors, check input parameters carefully, confirm API credentials, and consult Crypto APIs documentation for valid values.