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 allows users to broadcast locally signed cryptocurrency transactions to a specified blockchain network via the Crypto APIs service. It is useful when you have already created and signed a transaction offline or in another system, and now want to submit it to the blockchain for confirmation.
Common scenarios include:
- Sending a pre-signed Bitcoin or Ethereum transaction from an external wallet or hardware device.
- Broadcasting transactions generated by custom scripts or third-party services.
- Integrating with blockchain applications that separate signing and broadcasting steps.
For example, after signing a Bitcoin transaction hex string offline, you can use this node to push that transaction onto the Bitcoin network without exposing private keys to the node environment.
Properties
| Name | Meaning |
|---|---|
| blockchain | The target blockchain where the transaction will be broadcast (e.g., Bitcoin, Ethereum). |
| network | The specific network of the blockchain (e.g., mainnet, testnet). |
| context | Optional context string to correlate requests and responses. |
| JSON Body: | Collection of optional parameters related to the transaction broadcast: |
| - callbackSecretKey | Secret key used to secure callback notifications (optional). |
| - callbackUrl | URL to receive asynchronous callback notifications about the transaction status (optional). |
| - signedTransactionHex | The hexadecimal string of the locally signed transaction to be broadcasted. |
Output
The node outputs a JSON array containing the response from the Crypto APIs service after attempting to broadcast the transaction. This typically includes details such as transaction ID, status, and any relevant metadata returned by the API.
If the broadcast fails, the output may contain an error message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Crypto APIs REST API service.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node reads a local OpenAPI specification file (
2024-12-12-final.json) bundled with the node for operation definitions but this is internal and transparent to the user.
Troubleshooting
Common issues:
- Invalid or malformed signed transaction hex string will cause the broadcast to fail.
- Incorrect blockchain or network selection may result in errors or rejected transactions.
- Missing or invalid API credentials will prevent successful communication with the Crypto APIs service.
- Network connectivity problems can cause request timeouts or failures.
Error messages:
"Operation <name> not found": Indicates an internal misconfiguration or unsupported operation; usually not encountered by end users.- API errors returned from Crypto APIs will be passed through, e.g., "Invalid transaction hex" or "Transaction already exists".
Resolutions:
- Verify the signed transaction hex is correctly formatted and valid for the selected blockchain.
- Double-check blockchain and network parameters.
- Ensure API credentials are properly set up and have necessary permissions.
- Check internet connectivity and firewall settings.