Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
This node interacts with the WAX blockchain to retrieve asset information associated with a specified WAX account. It is particularly useful for users who want to fetch details about digital assets such as NFTs or tokens owned by an account on the WAX blockchain. For example, a user might use this node to list all assets owned by their account or filter assets by specific templates, collections, or schemas.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com). |
| Account Name | The WAX blockchain account name whose assets you want to retrieve. |
| Template ID (Optional) | Comma-separated list of template IDs to filter the assets returned. |
| Collection (Optional) | Comma-separated list of collections to filter the assets returned. |
| Schema (Optional) | Comma-separated list of schemas to filter the assets returned. |
| Code | The smart contract code to query against (default: atomicassets). |
Output
The node outputs JSON data containing the retrieved assets from the WAX blockchain. Each item in the output corresponds to an asset matching the query parameters. The structure typically includes asset metadata such as asset ID, owner, template ID, collection, schema, and other relevant blockchain asset details.
If the node supports binary data output (not explicitly shown in the provided code), it would represent any associated binary content related to the assets, such as images or media files linked to NFTs.
Dependencies
- Requires access to a WAX blockchain API endpoint (default is
https://wax.greymass.com). - May require an API key or authentication token if the endpoint enforces access control (not explicitly detailed in the source).
- No additional external libraries beyond those bundled are indicated.
- No internal credential names are exposed; however, the node optionally supports an API key credential for private key authentication.
Troubleshooting
- Common Issues:
- Incorrect or unreachable API endpoint URL may cause connection failures.
- Invalid or misspelled account names will result in no assets found or errors.
- Filtering by template ID, collection, or schema with incorrect values may return empty results.
- Error Messages:
- Network or timeout errors indicate connectivity issues with the WAX API endpoint.
- Authentication errors may occur if required credentials are missing or invalid.
- Resolutions:
- Verify the API endpoint URL and network connectivity.
- Double-check the account name and filter parameters for correctness.
- Ensure any required API keys or authentication tokens are properly configured in n8n credentials.