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 coin transactions on a specified blockchain and network. It is designed to trigger workflows when coins are confirmed as transferred, enabling automation around blockchain events such as wallet monitoring, transaction tracking, or alerting systems.

Common scenarios include:

  • Monitoring incoming confirmed coin transactions to a specific address.
  • Triggering notifications or downstream processes when new confirmed transactions occur.
  • Integrating blockchain event data into broader financial or auditing workflows.

For example, a user could configure this node to watch the Bitcoin mainnet for confirmed transactions to their wallet address and automatically update their accounting system or send alerts.

Properties

Name Meaning
blockchain The blockchain to monitor (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 A collection of optional parameters:
- address Specific wallet address to filter transactions for.
- allowDuplicates Boolean flag to allow duplicate event callbacks.
- callbackSecretKey Secret key used to validate callbacks from the API.
- callbackUrl URL to receive webhook callbacks for new confirmed transactions.
- receiveCallbackOn Numeric value indicating when to receive callbacks (e.g., on confirmation count).

Output

The node outputs an array of JSON objects representing the confirmed coin transactions received from the Crypto APIs service. Each JSON object contains details about a single confirmed transaction event.

If configured with a callback URL, the node can handle webhook callbacks containing transaction data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Crypto APIs REST API.
  • Needs network access 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 the Crypto APIs service and standard n8n environment.

Troubleshooting

  • Operation not found error: If the selected operation is not found in the bundled API spec, ensure the node version and API spec file are up to date.
  • Missing required parameters: The blockchain and network properties are mandatory; missing these will cause errors.
  • API authentication failures: Verify that the API key credential is correctly configured and has necessary permissions.
  • Webhook callback issues: If using callbackUrl, ensure the URL is publicly accessible and properly secured with callbackSecretKey if set.
  • Duplicate events: If duplicates are received, consider setting allowDuplicates appropriately.

Links and References

Discussion