1Shot icon

1Shot

Interact with the blockchain and web3 via 1Shot API

Actions5

Overview

This node integrates with the 1Shot API to interact with blockchain transactions, specifically allowing users to read details of a blockchain transaction by its ID. It is useful in scenarios where you need to fetch and verify transaction data from the blockchain via the 1Shot service, such as auditing transactions, monitoring transaction status, or retrieving transaction metadata for further processing.

For example, you might use this node to:

  • Retrieve detailed information about a specific blockchain transaction by providing its ID.
  • Use the returned transaction data to trigger downstream workflows based on transaction status or content.

Properties

Name Meaning
Endpoint Name or ID Select a transaction from a list or specify a Transaction ID directly (supports expressions). This identifies which transaction to read.
Parameters JSON object containing additional parameters to pass to the transaction read function. For example: {"to": "0x3e6a2f0CBA03d293B54c9fCF354948903007a798", "amount": "10000"}

Output

The node outputs an array of JSON objects representing the response from the 1Shot API's transaction read endpoint. The structure of each JSON object corresponds to the transaction details retrieved, which may include fields such as transaction status, sender, receiver, amount, timestamps, and other blockchain-specific metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the 1Shot API using OAuth2 authentication with a valid API key credential.
  • The node uses the base URL https://api.1shotapi.com/v0 for all API requests.
  • Proper configuration of the OAuth2 credentials within n8n is necessary to authenticate requests.

Troubleshooting

  • Common Issues:

    • Invalid or expired OAuth2 token leading to authentication failures.
    • Incorrect or non-existent Transaction ID causing the API to return errors or empty results.
    • Malformed JSON in the Parameters field causing request parsing errors.

  • Error Messages:

    • Unsupported operation: read — indicates that the operation parameter was set incorrectly; ensure "Read" is selected.
    • HTTP 403 errors typically indicate authentication issues; verify your API credentials and token validity.
    • JSON parsing errors when entering Parameters — ensure the JSON syntax is correct.

  • Resolutions:

    • Refresh or reconfigure the OAuth2 credentials if authentication fails.
    • Double-check the Transaction ID and ensure it exists on the blockchain accessible by 1Shot.
    • Validate JSON input in the Parameters field before execution.

Links and References

Discussion