Actions25
- Account Actions
- Token/Asset Actions
- Transaction Actions
- Utility Actions
Overview
This node interacts with the DecentralChain (DCC) blockchain to perform various operations related to tokens/assets, accounts, transactions, and utility functions. Specifically for the Token/Asset resource with the Get NFTs operation, it retrieves a list of NFTs owned by a specified address.
Use cases include:
- Querying which NFTs are owned by a particular blockchain address.
- Integrating NFT ownership data into workflows for asset management, verification, or display.
- Automating NFT-related processes such as monitoring holdings or triggering actions based on NFT possession.
Example: Given a wallet address, this node can fetch all NFTs owned by that address from the DCC blockchain, enabling further processing or reporting in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the DecentralChain node API endpoint to use if no credential is supplied. Defaults to https://nodes.decentralchain.io. |
For the Get NFTs operation specifically, the following input parameters are used internally (not listed in your provided properties but visible in code):
address(string): The blockchain address whose NFTs you want to retrieve.limit(number, default 100): Maximum number of NFTs to return.
These parameters are required to specify the target address and limit the number of results.
Output
The output JSON contains the response from the DecentralChain API endpoint /assets/nft/{address}/limit/{limit}. This typically includes:
- A list of NFT assets owned by the specified address.
- Each NFT entry may contain details such as token ID, metadata, owner information, and other blockchain-specific attributes.
The exact structure depends on the DecentralChain API response but generally represents the NFTs held by the queried address.
No binary data output is produced by this operation.
Dependencies
Requires access to the DecentralChain blockchain API, either via:
- An API key credential configured in n8n (optional).
- Or fallback to the provided Base URL parameter (
https://nodes.decentralchain.ioby default).
Uses HTTP requests to communicate with the blockchain node endpoints.
Optionally uses the
@decentralchain/waves-transactionslibrary for transaction-related operations (not directly relevant for Get NFTs).
Troubleshooting
Common issues:
- Network connectivity problems to the specified Base URL or API endpoint.
- Invalid or missing blockchain address parameter.
- Rate limiting or API quota exceeded on the DecentralChain node.
- Unexpected API response format changes.
Error messages:
"Library loading failed": Indicates failure to load the blockchain transaction library; however, this does not affect read-only operations like Get NFTs.- HTTP request errors will be surfaced with error messages from the underlying API call.
- If the node fails to create or broadcast transactions (not applicable for Get NFTs), detailed debug info is included.
Resolutions:
- Verify the Base URL and network connectivity.
- Ensure the address parameter is correctly formatted.
- Check API credentials if used.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.
Links and References
- DecentralChain official node API documentation (if available) — check the provider's website or developer portal.
- General blockchain and NFT concepts: https://en.wikipedia.org/wiki/Non-fungible_token
- n8n documentation on creating custom nodes and using HTTP Request helper: https://docs.n8n.io/
This summary focuses on the Token/Asset resource and the Get NFTs operation as requested.