Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node integrates with the Crypto APIs REST API to listen for new confirmed internal transactions on a specified blockchain and network. It is designed to trigger workflows when such internal transactions are detected, enabling automation around blockchain event monitoring.

Common scenarios include:

  • Monitoring internal transactions within smart contracts or wallets on blockchains like Ethereum.
  • Triggering alerts or downstream processes when specific internal transfers occur.
  • Integrating blockchain event data into broader business logic or analytics pipelines.

For example, a user can configure this node to watch for new confirmed internal transactions on the Ethereum mainnet and automatically update a database or notify a team when such events happen.

Properties

Name Meaning
blockchain The blockchain to monitor (e.g., Ethereum, Bitcoin).
network The specific network of the blockchain (e.g., mainnet, testnet).
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 event callbacks.
- callbackSecretKey Secret key used to secure callback requests.
- callbackUrl URL to receive webhook callbacks for new internal transactions.
- receiveCallbackOn Numeric value indicating when to receive callbacks (e.g., on confirmation).

Output

The node outputs an array of JSON objects representing the new confirmed internal transactions received from the Crypto APIs service. Each JSON object contains detailed information about the transaction event as provided by the API.

If configured with a callback URL, the node effectively subscribes to webhook events, and the output corresponds to the payloads received upon those events.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Crypto APIs REST API.
  • Needs network connectivity to the Crypto APIs endpoints.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata.
  • No additional external dependencies beyond standard n8n environment and the Crypto APIs service.

Troubleshooting

  • Operation not found error: If the selected operation is not recognized, ensure the node's bundled OpenAPI spec file is intact and up to date.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid parameters: Double-check required properties like blockchain and network are set correctly.
  • Callback URL issues: If using webhooks, ensure the callback URL is publicly accessible and properly secured if using a secret key.
  • Duplicate events: Use the allowDuplicates property to control whether repeated events are processed multiple times.

Links and References

Discussion