Actions9
Overview
This node interacts with TON Jetton tokens, a token standard on the TON blockchain. It supports various operations related to managing and using Fun Jettons within the TON ecosystem. The "Get Token Metadata" operation specifically retrieves metadata information about a given token minter contract.
Common scenarios for this node include:
- Querying token details such as name, symbol, or other metadata from a specific token minter contract.
- Managing token lifecycle events like minting, transferring, or burning tokens.
- Accessing pricing information and performing buy/sell operations on tokens.
Practical example:
If you want to fetch metadata of a particular Jetton token deployed on the TON blockchain, you provide the minter contract address and select the "Get Token Metadata" operation. This will return relevant metadata about that token.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform. Options include: Deploy Minter, Get Token Metadata, Update Token Metadata, Mint, Transfer, Burn, Get Prices, Buy Tokens, Sell Tokens. |
| Minter Address | The address of the GovernanceJettonMinter contract (required for some operations). Format examples: EQ... or UQ... |
| Recipient Address | The recipient's address for minting or transferring tokens. Required only for Mint and Transfer operations. Format examples: EQ... or UQ... |
| Amount | The number of tokens involved in minting, transferring, or selling operations. Specified as a string representing whole units without decimals. |
Output
The node outputs an array of JSON objects where each object corresponds to an input item processed. Each output JSON contains the parameters used for the operation:
{
"operation": "getMetadata",
"minterAddress": "string",
// For mint, transfer, sellTokens operations:
"recipient": "string",
"amount": "string"
}
Note: The current implementation returns the input parameters as output JSON; it does not show actual fetched metadata or results from blockchain queries. This suggests the node is structured to pass these parameters downstream or requires further implementation to interact with the blockchain.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for TON blockchain access (referred generically as an API authentication token).
- The node depends on the TON mnemonic credential for signing transactions.
- No external services are explicitly referenced in the provided code snippet, but interaction with the TON blockchain network is implied.
Troubleshooting
- Empty or invalid minter address: Ensure the minter address is correctly formatted (starting with EQ or UQ) and corresponds to a valid GovernanceJettonMinter contract.
- Missing recipient or amount for mint/transfer operations: These fields are mandatory for those operations; missing them will likely cause errors.
- Operation not supported or misspelled: Select a valid operation from the provided options.
- Credential issues: Make sure the required TON mnemonic credential is configured properly in n8n to authorize blockchain interactions.
Common error messages might relate to invalid addresses, missing parameters, or failed authentication. Verifying inputs and credentials usually resolves these.