WAX KitInstall

Summary

Transfers one or more AtomicAssets NFTs to another WAX account by sending a transfer action on the atomicassets contract (or a custom contract), signed with the credential's private key.

Inputs

• API Endpoint (required) — WAX API node to use. Presets include Greymass (default), EOS Nation, EOSphere, Pink.gg and WAX Sweden, or choose Custom.
• Custom Endpoint URL — Your own WAX API URL. Shown only when the endpoint is Custom.
• To Account (required) — WAX account name that receives the assets.
• Asset IDs — Repeatable list of asset IDs to transfer.
• Or Asset IDs (Comma-Separated) — Comma-separated asset IDs, as an alternative to the list. The source pack doesn't show how the two inputs are combined.
• Contract — NFT contract account. Defaults to atomicassets.
• Memo — Memo text attached to the transfer.
• Authorization — Repeatable actor and permission pairs (active, owner or custom) used to authorize the action.

Output shape

One output item per input item. The execution logic sits in a resources module that isn't in the source pack, so the exact JSON (probably a transaction result) is not confirmed.

The node needs the waxKitPrivateKeyApi credential. Before running, it checks a license key against Lemon Squeezy, and the result is cached. With Continue On Fail enabled, a failed item returns json with success:false, error and details. Otherwise the error stops the workflow.

Examples

Example 1: Send two NFTs to a buyer after a payment is confirmed.

To Account=buyer.wam, Asset IDs list with two IDs, Memo='Order #123', Authorization actor=youraccount with permission active.

Example 2: Transfer many assets from a spreadsheet.

Set 'Or Asset IDs (Comma-Separated)' to an expression such as {{$json.ids}}, set To Account, and leave Contract as atomicassets.

Links

• n8n community nodes installation guide