Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node listens for new confirmed internal transactions on a specified blockchain and network, triggering an event each time a transaction is confirmed and for each subsequent confirmation. It is useful for applications that need to track internal movements of funds within smart contracts or wallets, such as monitoring token transfers, auditing contract activity, or triggering workflows based on internal transaction confirmations.

Practical examples include:

  • Notifying users when an internal transaction has been confirmed on Ethereum.
  • Triggering downstream processes after a certain number of confirmations to ensure transaction finality.
  • Auditing internal wallet activity for compliance or analytics.

Properties

Name Meaning
blockchain The blockchain network to monitor (e.g., Ethereum, Bitcoin).
network The specific network environment (e.g., mainnet, testnet) where the blockchain operates.
context Optional string to correlate or identify the callback context.
JSON Body A collection of optional parameters:
- address Specific wallet address to filter internal transactions.
- allowDuplicates Boolean flag to allow duplicate notifications for the same transaction.
- callbackSecretKey Secret key used to secure callbacks from the API service.
- callbackUrl URL to which the API will send webhook notifications about new confirmed internal transactions.
- confirmationsCount Number of confirmations after which the event should be triggered.

Output

The node outputs JSON data representing the details of the confirmed internal transactions received from the blockchain API. Each output item corresponds to one internal transaction event, including all relevant transaction data fields provided by the API.

If binary data were involved (not indicated here), it would typically represent associated files or media related to the transaction, but this node focuses on JSON transaction data only.

Dependencies

  • Requires an API key credential for authenticating with the Crypto APIs REST API service.
  • Needs proper configuration of the API credentials in n8n.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically build requests.
  • Network connectivity to the Crypto APIs service endpoint.

Troubleshooting

  • Common issues:

    • Incorrect blockchain or network values may cause the API to return errors or no data.
    • Missing or invalid API credentials will result in authentication failures.
    • If the callback URL is not reachable or improperly configured, webhook notifications may fail.
    • Setting allowDuplicates incorrectly might lead to repeated events or missed notifications.
  • Error messages:

    • "Operation <operationName> not found": Indicates the requested operation is not defined in the API spec; usually a misconfiguration or typo in the operation parameter.
    • Authentication errors: Check that the API key credential is correctly set up.
    • Network errors: Verify internet connectivity and that the Crypto APIs service is accessible.

Links and References

Discussion