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 integrates with Crypto APIs to prepare a blockchain transaction specifically for EVM-compatible blockchains (Ethereum Virtual Machine). The "Prepare Transaction From Address EVM" operation allows users to construct a transaction payload from a given sender address, specifying details such as recipient, amount, fee, nonce, and transaction type. This is useful in scenarios where you want to programmatically create unsigned transactions that can later be signed and broadcasted on an EVM blockchain network.
Practical examples include:
- Preparing a transaction to send tokens or Ether from one wallet to another.
- Creating custom transactions with specific gas fee strategies (legacy, access list, or gas fee market).
- Automating transaction creation workflows in DeFi applications or wallet services.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to use (e.g., Ethereum, Binance Smart Chain). |
| network | The specific network within the blockchain (e.g., mainnet, testnet). |
| type | The type of transaction to prepare. |
| context | Optional context string for additional metadata or tracking. |
| JSON Body: | Collection of parameters defining the transaction details: |
| - additionalData | Extra data to include in the transaction (optional). |
| - amount | Amount of cryptocurrency to send (as a string). |
| - nonce | Nonce value for the transaction (optional). |
| - recipient | Address of the transaction recipient. |
| - sender | Address of the transaction sender. |
| - fee | Fee details as a collection (structure not fully detailed here). |
| - type | Type of the transaction fee model; options are: |
| • legacy-transaction | |
| • access-list-transaction | |
| • gas-fee-market-transaction (default) |
Output
The node outputs a JSON array where each item represents the prepared transaction data returned by the Crypto APIs service. This typically includes all necessary fields to sign and broadcast the transaction on the specified EVM blockchain network.
If binary data were involved (not indicated here), it would represent raw transaction bytes or signatures, but this node focuses on JSON transaction preparation.
Dependencies
- Requires an API key credential for Crypto APIs REST API.
- The node reads a local OpenAPI specification file (
2024-12-12-final.json) bundled with the node to dynamically resolve API paths and operations. - No other external dependencies beyond standard Node.js modules and n8n workflow helpers.
Troubleshooting
- Operation Not Found Error: If the specified operation cannot be found in the API spec, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and up-to-date.
- Missing Required Parameters: The node requires certain parameters like
blockchain,network, andtype. Omitting these will cause errors. - API Request Failures: Network issues or invalid API credentials will cause request failures. Verify your API key and network connectivity.
- Invalid Parameter Values: Providing incorrect blockchain names, network identifiers, or malformed addresses may result in API errors. Double-check input values.
- To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error messages in output JSON.