Actions11
Overview
This node interacts with the Solana blockchain network to perform various operations. Specifically, the Get Transaction Details operation fetches and returns detailed information about a Solana transaction given its signature. This is useful for verifying transaction status, inspecting transaction contents, or auditing blockchain activity.
Common scenarios include:
- Tracking the status and details of a submitted transaction.
- Retrieving metadata such as instructions, signatures, and confirmations related to a specific transaction.
- Debugging or logging blockchain transactions in workflows.
Example: Given a transaction signature, the node will return the full parsed transaction details from the Solana network, enabling further processing or decision-making based on the transaction content.
Properties
| Name | Meaning |
|---|---|
| Transaction Signature | Signature (unique identifier) of the transaction to look up on the Solana blockchain. |
Output
The output JSON contains:
success: Boolean indicating if the operation succeeded.txDetails: The detailed transaction object returned by the Solana RPC API. This includes all parsed transaction data such as signatures, message instructions, account keys, block time, and confirmation status.operation: The name of the operation performed (getTxDetails).
No binary data is output by this operation.
Example output snippet:
{
"success": true,
"txDetails": {
// Full transaction details object as returned by Solana RPC
},
"operation": "getTxDetails"
}
Dependencies
- Requires an active connection to a Solana RPC endpoint, configured via credentials that provide:
- A private key for signing transactions (not used in this operation but required by the node).
- The RPC URL to connect to the Solana network.
- Uses the official Solana Web3.js library to interact with the blockchain.
- Requires an API authentication token or key configured in n8n credentials for accessing the Solana RPC.
Troubleshooting
Error: No transaction details found for signature:
This means the provided transaction signature does not exist or is not yet confirmed on the network. Verify the signature is correct and that the transaction has been processed.Error: No credentials returned!
Indicates missing or misconfigured Solana API credentials. Ensure the API key and RPC URL are properly set in the node's credential configuration.Network or RPC errors:
Could be caused by connectivity issues or invalid RPC URLs. Confirm the RPC endpoint is reachable and valid.Invalid transaction signature format:
The signature must be a valid base58 encoded string. Invalid formats will cause lookup failures.