WAX KitInstall

Summary

Sells a specified number of bytes of RAM from a WAX account on the WAX blockchain, signing the transaction with the node's configured private-key credential. The source pack is obfuscated and the resource handlers are not included, so the exact on-chain action (presumably eosio::sellram) is inferred from the operation name.

Inputs

• endpoint (required) — WAX API endpoint to submit the transaction to. Options: Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
• customEndpoint — Custom API URL. Shown only when Endpoint is set to Custom.
• bytes (required) — Number of bytes of RAM to sell (default 1000).
• authorization — One or more authorization entries, each with an Actor (account name) and a Permission (active, owner, or custom with a custom permission name). Defines who signs the action.

Output shape

One output item per input item. The exact fields come from the resource handler, which is not visible in the source pack, so they are likely transaction result details.

The node requires the waxKitPrivateKeyApi credential and checks its license key against Lemon Squeezy before running. If Continue On Fail is enabled, a failed item returns json with success:false, error, and details instead of stopping the workflow.

Examples

Example 1: Sell 5000 bytes of unused RAM from your account to reclaim WAX.

Endpoint: Greymass; RAM Bytes: 5000; Authorization: actor 'myaccount', permission 'active'.

Example 2: Sell RAM through a self-hosted API node.

Endpoint: Custom; Custom Endpoint URL: https://my-wax-node.example.com; RAM Bytes: 1000; Authorization: actor 'myaccount', permission 'active'.

Links

• n8n community nodes installation guide