WAX KitInstall

Summary

Mints the same NFT template on the WAX blockchain to a list of recipient accounts in one batch, using the supplied collection, schema, template and data. The resource implementation is obfuscated and not included in the source pack, so runtime details are inferred from the declared properties.

Inputs

• endpoint (required) — WAX API endpoint: Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
• customEndpoint — Endpoint URL, used only when API Endpoint is Custom.
• collectionName (required) — Collection to mint in (12 characters max).
• schemaName (required) — Schema name of the assets being minted.
• templateIdInt (required) — Template ID to mint. Defaults to -1, which typically means no template.
• immutableData — JSON object of immutable attributes for the minted assets. Defaults to {}.
• mutableData — JSON object of mutable attributes for the minted assets. Defaults to {}.
• recipients — Multiple entries, each with an Account (required) that will receive the NFT.
• authorization — One or more actor and permission pairs (active, owner, or custom) used to authorize the transaction.

Output shape

One output item per input item, containing the result of the batch mint action. The exact fields, such as a transaction ID, can't be confirmed from the provided source.

The node requires a WAX Kit private key credential and checks its license key (via Lemon Squeezy) before running. If Continue On Fail is enabled, a failing item returns {success:false, error, details} instead of stopping the workflow.

Examples

Example 1: Airdrop a promotional NFT to several community members.

Set collectionName, schemaName and templateIdInt. Add one recipient per account, set authorization actor to the collection author with active permission, and leave the data fields as {}.

Links

• n8n community nodes installation guide