WAX icon

WAX

Interact with the WAX blockchain

Actions9

Overview

This node enables interaction with the WAX blockchain, specifically allowing users to transfer tokens from one account to another. It is useful in scenarios where automated token transfers are needed, such as paying for services, distributing rewards, or managing token balances programmatically on the WAX blockchain.

For example, a user can configure this node to send a specified amount of WAX tokens to another account with an optional memo note, automating payments or transfers within a workflow.

Properties

Name Meaning
API Endpoint The URL of the WAX blockchain API endpoint to connect to (default: https://wax.greymass.com).
Token Contract The smart contract managing the token, e.g., "eosio.token" for standard WAX tokens.
Symbol The symbol of the token to transfer, e.g., "WAX".
To Account The recipient's WAX blockchain account name to which tokens will be transferred.
Amount The number of tokens to transfer (e.g., 1).
Precision Number of decimal places for the token amount (default is 8).
Memo An optional text memo to include with the token transfer transaction.

Output

The node outputs JSON data representing the result of the token transfer operation. This typically includes transaction details such as transaction ID, status, and any relevant blockchain response data confirming the transfer.

If an error occurs during execution, the output JSON will contain an error field with the error message.

No binary data output is produced by this node.

Dependencies

  • Requires access to a WAX blockchain API endpoint (configurable via the "API Endpoint" property).
  • May require an API authentication token or private key credential configured in n8n to authorize transactions on behalf of the user.
  • The node depends on internal resource and operation implementations bundled in the source code (./resources), which handle the actual blockchain communication.

Troubleshooting

  • Common issues:

    • Incorrect or unreachable API endpoint URL may cause connection failures.
    • Invalid or missing recipient account name will cause the transfer to fail.
    • Insufficient token balance or incorrect precision may lead to transaction rejection.
    • Missing or invalid authorization credentials will prevent successful transaction signing.

  • Error messages:

    • Errors returned from the blockchain API will be included in the output under the error field if "Continue On Fail" is enabled.
    • Common errors include "account not found," "insufficient funds," or "invalid token symbol."

  • Resolution tips:

    • Verify the API endpoint URL is correct and accessible.
    • Double-check the recipient account name and token contract details.
    • Ensure the amount and precision match the token's requirements.
    • Confirm that necessary credentials (private keys or API tokens) are properly configured in n8n.

Links and References

Discussion