MultiversX icon

MultiversX

MultiversX blockchain operations: Execute smart contracts, check balances, transfer tokens, query accounts, get transactions, and access network data. Can inspect ABI functions and contract details. ALWAYS validate ABI functions before execution. Automatically provides contract context to AI including address and available functions.
Join our community

Actions3

Overview

This node enables interaction with the MultiversX blockchain, focusing on executing and querying smart contract functions. It supports calling state-modifying contract functions (which require gas) as well as querying read-only view functions without gas costs. The node also allows inspecting contract details and ABI functions.

Common scenarios include:

  • Executing token transfers, staking, minting, or other blockchain state changes via smart contracts.
  • Querying contract state or blockchain data without modifying it.
  • Inspecting smart contract ABI to understand available functions and their parameters before execution.

Practical examples:

  • Calling a transfer function on a token contract to send tokens.
  • Querying a balanceOf view function to get an account's token balance.
  • Inspecting a contract’s ABI to list all available functions and their input/output types.

Properties

Name Meaning
Contract Action Choose between:
• Call Function — execute a smart contract function that modifies blockchain state (requires gas).
• Query Function — query a smart contract view function without modifying state (no gas).
Contract Address The address of the smart contract to interact with (e.g., erd1qqqqqqqqqqqqqpgq...).
Contract ABI JSON representation of the contract's ABI, required for validating functions and parameter types.
Function Input Method How to specify the function name and arguments:
• Manual Selection (Dropdown) — select function from dropdown generated from ABI.
• AI Specification (Direct Input) — allow AI to specify function name and args directly.
Function Name (Manual method) Select the function to call/query from the list of available functions parsed from the ABI.
Function Name (AI method) Directly input the smart contract function name to execute (e.g., transfer, mint).
Function Arguments (Manual method) Provide multiple arguments with name, value, and type (Address, BigNumber, Boolean, Number, String).
Function Arguments (AI method) Provide multiple arguments with name, value, and type specified as free text.
Gas Limit (For Call Function only) Gas limit for the transaction (default 5,000,000).
Value (EGLD) (For Call Function only) Amount of EGLD cryptocurrency to send with the transaction (default "0").

Output

The node outputs JSON objects containing the results of the executed operation:

  • For Call Function:

    • success: boolean indicating if the transaction was successful.
    • transactionHash: hash of the submitted transaction.
    • sender: sender address.
    • receiver: contract address.
    • function: name of the called function.
    • arguments: array of parsed function arguments.
    • gasLimit: gas limit used.
    • value: EGLD value sent.

  • For Query Function:

    • success: boolean indicating success.
    • function: queried function name.
    • result: returned data from the contract query.
    • gasUsed: gas consumed by the query.
    • contractAddress: address of the queried contract.

  • For Inspect Contract:

    • Depending on inspection type, returns contract details, list of functions, or detailed info about a specific function.

The node does not output binary data.

Dependencies

  • Requires an API key credential for MultiversX wallet access, including private key for signing transactions.
  • Uses MultiversX SDK libraries for blockchain interaction and transaction creation.
  • Network environment configuration (mainnet, testnet, devnet) determines API endpoints.
  • Requires valid contract ABI JSON for smart contract operations.

Troubleshooting

  • Invalid ABI format: If the provided ABI JSON is malformed or missing required fields, the node will throw an error. Ensure the ABI is correctly formatted JSON matching the contract.
  • Function not found in ABI: When specifying a function name, it must exist in the ABI. Use the "Inspect Contract" operation to list available functions.
  • Missing or invalid private key: For call functions, a valid private key must be provided in credentials. The key can be PEM format or a 64-character hex string. Errors occur if the key is missing or incorrectly formatted.
  • Gas limit too low: Transactions may fail if the gas limit is insufficient. Adjust the gas limit property accordingly.
  • Network environment mismatch: Ensure the selected network environment matches the contract deployment (mainnet/testnet/devnet).
  • Unsupported contract action or operation: Only supported actions are "callFunction" and "queryFunction" under the "smartContract" operation.

Links and References

Discussion