Portal Community
What it does: The Ethereum node (ethereum) exposes Ethereum and EVM-compatible chain operations as workflow steps, via Nethereum over JSON-RPC. Unlike most read-only community blockchain nodes, this one already ships real signed writes — token transfers, contract calls, NFT transfers, contract deployment, and off-chain message signing — alongside a large read surface, across 10 resources and 64 defined operations (63 currently reachable through the node; see Roadmap).

Quick Start

  1. Add an Ethereum node to your workflow
  2. Set resource to account and operation to balance
  3. Enter an address (e.g. 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb)
  4. Leave network unset to use the default (ethereum / mainnet), or set it explicitly
  5. Run the workflow — the node returns the address's ETH balance in wei and (optionally) a formatted value
Tip: Every operation on this node shares the same core config keys — resource, operation, network, and (for writes) credentialID — plus a small set of operation-specific fields. Learn the pattern once on Input & Output and every operation below follows it.

Pages in This Guide

Configuration

appsettings.json, default network, wallet credentials, and registration.

Networks

Ethereum mainnet, any EVM-compatible chain, and adding your own.

Account Operations

ETH balances, nonces, EOA/contract detection, transaction history.

Block Operations

Block metadata, chain tip, and ranged block listing.

Transaction Operations

Look up, send, decode, and wait on transactions.

Token Operations (ERC-20)

Balances, transfers, allowances, metadata, mint/burn.

NFT Operations (ERC-721)

Ownership, transfers, approvals, minting, and metadata.

Contract Operations

Arbitrary read/write calls against any ABI, deploy, multicall.

ENS Operations

Name resolution, reverse lookup, avatars, and text records.

Gas Operations

Estimate, price, fee history, and a recommended-fee helper.

Wallet Operations

Off-chain message signing and signature verification.

Utility Operations

ABI encode/decode, unit conversion, address tools.

Input & Output

The shared config-key pattern and how errors surface.

Examples

Worked workflow patterns using this node.

Troubleshooting

Common errors and how to fix them.

Roadmap

The narrow, honestly-documented gaps that remain.

Core Concepts

JSON-RPC via Nethereum

Every operation talks to an EVM-compatible network's JSON-RPC endpoint through Nethereum. That means real gas costs and real signed transactions for writes — this is not a free-Mirror-Node-style read-only integration. A vault CRYPTO_WALLET credential is required for any write. See Input & Output.

Resources

Operations are grouped by resource:

Networks

Every operation runs against whichever EVM-compatible network you've configured, selected per-call via the network config key. See Networks for the built-in examples and how to add your own.

Operation Summary

Resource Operations Guide Page
accountbalance, nonce, history, codeAccount Operations
blockget, number, listBlock Operations
transactionget, send, receipt, pending, decode, waitTransaction Operations
tokenbalance, transfer, approve, transferFrom, allowance, totalSupply, decimals, name, symbol, mint, burnToken Operations
nftbalance, ownerOf, transferFrom, safeTransferFrom, approve, setApprovalForAll, getApproved, isApprovedForAll, tokenUri, mint, listOwnedTokens, getMetadataNFT Operations
contractread, write, simulate, deploy, multicall, detectStandards (logs not yet routed)Contract Operations
ensresolve, reverse, avatar, text, resolverENS Operations
gasestimate, price, feeHistory, priorityFee, optimizeGas Operations
walletsignMessage, signTypedData, verifySignatureWallet Operations
utilityvalidateAddress, convertUnits, chainId, encodeFunctionData, decodeFunctionData, encodeEventTopics, decodeEventLog, contractAddressUtility Operations