WAX KitInstall

Summary

Sends multiple token transfers on the WAX blockchain from a configured list of transfer entries. The node's own source is obfuscated and the resource implementation isn't included, so exact on-chain behavior (single batched transaction vs. separate ones) and return fields aren't confirmed.

Inputs

• endpoint (required) — WAX API endpoint: Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
• customEndpoint — Custom API URL; shown only when endpoint is Custom.
• transferList — Repeatable list of transfers. Each has To Account (required), Amount (required, default 1), Symbol (required, default WAX), Precision (required, default 8), Token Contract (required, default eosio.token), and optional Memo.
• authorization — Repeatable list of authorizations. Each has Actor (account name) and Permission (Active, Owner, or Custom with a Custom Permission name). Defaults to active.

Output shape

One output item per input item, containing the result of the transfer execution. The exact fields aren't visible in the provided source.

The node requires WAX Kit private key credentials (waxKitPrivateKeyApi) and checks a license key via Lemon Squeezy before running. If 'Continue on Fail' is enabled, a failed item returns json with success: false, error, and details. Otherwise the error is thrown.

Examples

Example 1: Airdrop WAX to several accounts

Endpoint Greymass; add a Transfer entry per recipient with Symbol WAX, Precision 8, Contract eosio.token, and an Amount and Memo; Authorization actor = sender account, permission active.

Example 2: Pay out a custom token to multiple holders

Add Transfer entries with the token's Symbol, its Precision, and its Token Contract; set Authorization to the sending account's active permission.

Links

• n8n community nodes installation guide