Hedera

Interact with Hedera network for NFT operations
Join our community

Overview

This node interacts with the Hedera network to perform NFT-related operations. Specifically, it supports minting a new NFT token on Hedera. This is useful for users who want to create unique digital assets represented as NFTs on the Hedera blockchain.

A practical example would be an artist or content creator automating the creation of NFTs representing their digital artwork or collectibles. By providing the token name, symbol, and metadata, they can mint NFTs programmatically within an n8n workflow.

Properties

Name Meaning
Token Name The name of the NFT token to be minted (e.g., "My NFT").
Token Symbol The symbol representing the NFT token (e.g., "NFT").
Metadata A JSON string containing metadata for the NFT, such as attributes or descriptions.

Output

The node outputs a JSON array where each item corresponds to one input item processed. For the "Mint NFT" operation, each output item contains:

  • success: Boolean indicating if the minting was successful.
  • tokenId: The identifier of the minted token on Hedera (mocked as "0.0.1234567").
  • serialNumber: The serial number of the minted NFT (mocked as 1).
  • tokenName: The name of the token as provided in input.
  • tokenSymbol: The symbol of the token as provided in input.
  • metadata: The metadata JSON string as provided in input.
  • message: A success message confirming the NFT was minted (mock response).

Note: The current implementation returns a mock response and does not perform real network calls.

Dependencies

  • Requires access to the Hedera network API or SDK for actual minting (not implemented in this code).
  • Needs configuration of appropriate API credentials or authentication tokens to interact with Hedera services (not shown here).
  • No external dependencies are explicitly imported in the provided code snippet.

Troubleshooting

  • Common issues:
    • Invalid JSON in the Metadata property could cause errors when parsing or sending data to Hedera.
    • Missing or incorrect API credentials will prevent actual minting (once implemented).
  • Error messages:
    • If an error occurs during execution, the node either throws the error or, if configured to continue on fail, outputs an error object with the message.
  • Since the current code uses a mock response, no real network errors will occur until integration is added.

Links and References

Discussion