DecentralChain (DCC)Install

Overview

This node interacts with the DecentralChain (DCC) blockchain network to perform various operations related to accounts, tokens, transactions, utilities, and matcher services. Specifically for the Account resource with the Get Account Balance operation, it retrieves the balance information of a specified DCC address by querying the blockchain node's API.

Common scenarios where this node is beneficial include:

• Monitoring the balance of a wallet address in real-time.
• Integrating blockchain account data into workflows for financial or asset management.
• Automating balance checks before performing transactions or other blockchain operations.

Practical example:

• A user wants to check the current DCC token balance of their wallet address before initiating a transfer. This node fetches the balance from the blockchain and outputs it for further processing or notification.

Properties

Output

The output JSON contains the balance information returned by the DecentralChain node API for the specified address. It typically includes fields such as:

• balance: The current balance of the address in the smallest units of DCC.
• Other possible metadata about the account depending on the node's API response.

No binary data output is produced by this operation.

Example output snippet:

{
  "balance": 123456789,
  "additionalInfo": { ... }
}

Dependencies

• Requires access to a DecentralChain node API endpoint, either via the provided Base URL or through configured credentials that supply the API base URL.
• Uses HTTP requests to communicate with the blockchain node.
• Optionally requires an API key credential if authentication is needed by the node API (not explicitly shown but implied by credential usage).
• No external libraries beyond standard n8n workflow helpers and optional blockchain transaction libraries are required for this operation.

Troubleshooting

• Common issues:

  • Incorrect or malformed DCC address input will cause the API request to fail or return errors.
  • Network connectivity issues to the specified Base URL can prevent successful API calls.
  • If the node API requires authentication and credentials are missing or invalid, requests will fail.

• Error messages:

  • HTTP errors from the blockchain node API (e.g., 404 Not Found if address does not exist).
  • JSON parsing errors if the API returns unexpected data.

• Resolutions:

  • Verify the correctness of the DCC address format.
  • Ensure the Base URL is reachable and correct.
  • Provide valid credentials if the node API requires authentication.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

• DecentralChain Official Node API Documentation (Base URL used by default)
• DecentralChain GitHub Repository (for source code and SDKs)
• n8n Documentation (for general node usage and configuration)