Actions9
- Account Actions
- Token Actions
- Asset Actions
Overview
This node enables interaction with the WAX blockchain, specifically allowing users to transfer digital assets from one account to another. It is useful in scenarios where you need to programmatically move NFTs or other tokenized assets on the WAX blockchain, such as automating asset management, marketplace operations, or game item transfers.
For example, a user can specify a list of asset IDs and transfer them to another WAX account with an optional memo note, all through this node without manual blockchain transactions.
Properties
| Name | Meaning |
|---|---|
| API Endpoint | The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com). |
| To Account | The target WAX account name to which the assets will be transferred. |
| Asset IDs (Comma-Separated) | A comma-separated string listing the IDs of the assets to transfer. |
| Contract | The smart contract managing the assets, defaulting to atomicassets. |
| Memo | An optional text memo to include with the transfer transaction. |
Output
The node outputs JSON data representing the result of the transfer operation. This typically includes confirmation details from the blockchain about the transfer status. If multiple items are processed, the output is an array of such results.
No binary data output is produced by this node.
Dependencies
- Requires access to a WAX blockchain API endpoint.
- Optionally requires an API key or private key credential for signing transactions (configured separately in n8n).
- Network connectivity to the specified WAX API endpoint.
Troubleshooting
- Common issues:
- Invalid or missing "To Account" or "Asset IDs" will cause the transfer to fail.
- Incorrect API endpoint URL or network issues may prevent communication with the blockchain.
- Insufficient permissions or missing authentication credentials can lead to authorization errors.
- Error messages:
- Errors related to invalid asset IDs or accounts usually indicate input mistakes; verify the values.
- Connection timeouts or unreachable endpoint errors suggest network or endpoint configuration problems.
- Authentication failures require checking that the correct API key or private key is configured.