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, "Derive And Sync New Receiving Addresses EVM" under the "HD Wallets" resource, interacts with a Crypto APIs REST API to derive and synchronize new receiving addresses for Ethereum Virtual Machine (EVM) compatible blockchains. It uses an extended public key (xPub) to generate new wallet addresses on a specified blockchain network.
Common scenarios where this node is beneficial include:
- Automatically generating new receiving addresses for wallets in EVM-compatible blockchains like Ethereum, Binance Smart Chain, Polygon, etc.
- Synchronizing wallet addresses derived from an HD wallet to keep track of all generated addresses.
- Integrating address derivation into automated workflows for crypto payment processing or wallet management.
Practical example:
- A user wants to generate new receiving addresses for their Ethereum wallet using an extended public key and keep them synchronized for incoming payments. This node can be used to derive those addresses programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| blockchain | The target blockchain network for which to derive addresses (e.g., Ethereum, BSC). |
| extendedPublicKey | The extended public key (xPub) used to derive new receiving addresses. |
| network | The specific network within the blockchain (e.g., mainnet, testnet) to operate on. |
| context | Optional string to provide additional context or metadata for the request. |
| JSON Body | Additional parameters as a JSON collection to customize the API request body if needed. |
Output
The output is a JSON array containing the results returned by the Crypto APIs endpoint for deriving and syncing new receiving addresses. Each item in the output array corresponds to a derived address or related data returned by the API.
If the API supports binary data output, it would typically represent associated cryptographic material or files, but this node primarily outputs JSON data representing wallet addresses and synchronization status.
Dependencies
- Requires an active connection to the Crypto APIs REST API service.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- Relies on the presence of the extended public key and correct blockchain/network identifiers.
- Uses internal helper functions to make HTTP requests to the Crypto APIs endpoints.
Troubleshooting
Common issues:
- Invalid or malformed extended public key leading to API errors.
- Incorrect blockchain or network names causing the API to reject the request.
- Missing required parameters resulting in validation errors.
- Network connectivity or authentication failures with the Crypto APIs service.
Error messages and resolutions:
"Operation <operationName> not found": Indicates the requested operation is not defined; ensure the operation name matches exactly.- API response errors about invalid keys or parameters: Verify that the extended public key and blockchain/network values are correct and supported.
- Authentication errors: Confirm that the API key credential is properly set up and has necessary permissions.
- If the node returns an error object in the output JSON, check the
errormessage for details and adjust input parameters accordingly.