Drop an evmquery node into any n8n flow. Trigger on schedule, read a contract, branch on the result, send alerts. No glue code, no ABI files.
cel.bind(d, token.decimals(), {
"name": token.name(),
"symbol": token.symbol(),
"decimals": string(formatUnits(d, 0)),
"totalSupply": string(formatUnits(token.totalSupply(), d))
})n8n community node · Make and Zapier on the roadmap
You have a workflow engine. You have an idea. What stops you is that every onchain read means commissioning a dev sprint for ABIs, RPCs, and decoders.
n8n and Make have nodes for Slack, Airtable, and 400 other services. For reading an EVM contract? You're building a custom HTTP node and decoding hex by hand.
Provider keys, rate limits, retries, fallback URLs. Stuff that belongs in a platform, not inside a workflow.
Every contract needs its ABI JSON pasted into an HTTP node. Every proxy needs its implementation resolved manually. It rots the moment a contract upgrades.
The "quick" Python script for a one-time alert grows into five cron jobs nobody remembers owning. A visual workflow is where this belongs.
Install the evmquery node in n8n. Point it at any contract. Get typed data back into the workflow, ready for branching, alerts, or storage.
Install from the n8n community marketplace. Authenticate once with an API key. Expressions work the same as in the REST API and MCP.
Ethereum, Base, BNB Smart Chain, and Polygon today. Proxies resolve automatically. Verified contracts work without uploading ABIs.
BigInt, address, and struct decoded into workflow variables. Run IF nodes, Switch nodes, and Merge nodes on real numbers instead of hex strings.
One expression reads Aave health, a Uniswap LP value, and a Chainlink price in a single node run. Auto-batched across contracts.
REST API works in any tool that speaks HTTP today. Native Make and Zapier connectors are coming. Ping us if you want early access.
{
"node": "evmquery",
"chain": "evm_ethereum",
"expression": "aave.getUserAccountData(wallet).healthFactor"
}Read any EVM contract without wiring providers, ABIs, or decoders by hand.
Independent contracts, different protocols. Every read in an expression is batched into a single Multicall3 call per chain.
1 request4 reads1 round trip
Same behavior on every chain we support.
Read state by address. No ABI files, ever.
Solidity structs decode into fields you dot straight into.
EIP-1967, transparent, beacon: resolved automatically.
10 of 44 major contracts we checked resolve through a proxy.
The same expression language on every surface. Learn it once, query from anywhere.
execute_query and describe_schema are the same two tools behind REST and n8n.
Yes. Install the evmquery community node from the n8n marketplace. It authenticates with an API key and exposes the full expression language as a node action.
Not as native apps yet. They're on the roadmap. The REST API works in any tool that can make an HTTPS request, which covers Make's HTTP module and Zapier's Webhooks by Zapier action.
Health-factor alerts when an Aave position approaches liquidation. Slack notifications on large DEX swaps. Airtable rows for every new NFT mint. Treasury snapshots pushed to a Google Sheet. Anything that reacts to onchain state.
Ethereum, Base, BNB Smart Chain, and Polygon today. More EVM chains are added continuously. If a contract is verified on a supported chain, the node can read it.
The node uses an API key you generate in the dashboard. Keys are scoped per workspace and can be rotated at any time. All traffic is over HTTPS.
Free tier included. No credit card. The n8n node installs in under a minute.