WAX KitInstall

Summary

Transfers a fungible token (WAX by default) from the credentialed account to another WAX account by sending a transfer action to a token contract. The source is obfuscated and the resource handlers are not included, so the exact return shape is not visible.

Inputs

• endpoint (required) — WAX API endpoint. Choose Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
• customEndpoint — Custom API URL. Shown only when Endpoint is Custom.
• contract (required) — Token contract account, default "eosio.token".
• symbol — Token symbol, default "WAX".
• to (required) — Recipient account name.
• amount (required) — Amount of tokens to send, default 1.
• precision — Decimal places for the token, default 8. It should match the token's actual precision.
• memo — Memo text attached to the transfer.
• authorization — Optional list of authorizations. Each has an actor, and a permission of active, owner or custom (with a custom permission name).

Output shape

One output item per input item, containing the result of the transfer as JSON. This is most likely the transaction result, but the handler code is not shown.

The node requires the waxKitPrivateKeyApi credential, which signs the transaction. A WAX Kit license key is validated against Lemon Squeezy before each run. If Continue On Fail is enabled, a failed item returns {success:false, error, details} instead of stopping the workflow.

Examples

Example 1: Send 5 WAX to another account with a memo

Contract eosio.token, Symbol WAX, To = recipient account, Amount 5, Precision 8, Memo "payment".

Example 2: Transfer a custom token through a custom node

Endpoint Custom with Custom Endpoint URL, Contract = token contract, Symbol = token symbol, Precision matching the token, To and Amount set.

Links

• n8n community nodes installation guide