Recently, while building automation workflows with n8n, I ran into a problem: although n8n makes it easy to connect various services, interacting with the Ethereum blockchain is surprisingly difficult. Usually, you need to use a Code Node and install external libraries like ethers.js or viem, or manually handle signatures using the Crypto node. This is completely unsuitable for non-developers.

While the community already has n8n-nodes-web3, its functionality is relatively basic, and many common operations aren’t supported. So, I wanted to test Claude Code’s Vibe Coding capabilities while also trying out n8n node development. Since I frequently need these features myself, I decided to create a more comprehensive Ethereum integration package.

n8n-nodes-ethereum

The goal of this project is to provide complete Ethereum blockchain integration, allowing you to handle various blockchain operations directly in n8n’s visual interface without writing code. The project uses viem as the underlying library (more modern, type-safe, and actively maintained compared to traditional web3.js), and adopts a unified Resource/Operation design pattern.

Main Features

The project includes two nodes:

  • Ethereum Node: A regular node for executing various blockchain operations
  • Ethereum Trigger Node: A trigger node that can monitor new blocks, contract events, and transactions to specific addresses

Features cover most common use cases:

  • 10 Resource Types: Accounts, blocks, transactions, contracts, ERC20, ERC721, ERC1155, ENS, Gas, signatures, utility functions, and more
  • Complete Token Standard Support: Built-in support for all standard methods of ERC20, ERC721, and ERC1155, no need to handle ABIs yourself
  • Multi-chain Support: Default support for 18+ EVM-compatible networks (Ethereum, Polygon, BSC, Arbitrum, Optimism, Base, etc.), with custom RPC options
  • Triggers: Monitor new blocks, contract events, and specific address transactions to create real-time reactive workflows
  • Security Design: RPC connections and wallet credentials are managed separately; read-only operations don’t require private keys

In terms of usability, this package allows users to provide an ABI and specify functions or events, with immediate feedback if any inputs are incorrect. While it still requires some technical knowledge, it is significantly simpler than manually constructing calldata and signatures. With the help of LLMs, even non-developers should find complex contract interactions manageable.

For example, you can easily create workflows like:

  • Monitor Transfer events on a specific NFT contract and send notifications for new transactions
  • Periodically check a DAO’s treasury balance and alert when it falls below a threshold
  • Automate token transfers and wait for confirmation
  • Monitor Gas Price and execute transactions when prices are low enough

For a complete feature list, refer to the documentation site.

Current Status and Future

The project has reached version 1.0.1, featuring more complete support and having passed basic testing. While the main features are implemented, I’m continuously building automated tests to ensure all nodes work correctly.

Security Warning: Although it has passed basic testing, I recommend testing on testnets first, and only use it in production after confirming everything works. Be especially careful with operations involving funds, and I recommend only keeping necessary amounts in automation wallets.

Our next step is to improve error handling. Currently, when errors occur, the feedback might not be clear enough to guide users toward a solution. I hope to add more understandable error messages and make it easier for users to provide sufficient context when reporting issues.

I’m also considering integrating popular DeFi protocols like Uniswap. However, this presents a dilemma: adding too many specific nodes could make the interface cluttered and harder to navigate. This is a longer-term goal, and I’m still thinking about how to balance feature richness with usability.

Future plans include continuing to improve test coverage and adding more features based on user feedback. Contributions are welcome!

Want to Learn More?

If you’re using n8n and need to interact with blockchain, feel free to try this package:

The documentation includes installation instructions written by Claude, credential setup tutorials, how to use each resource, and some common workflow examples.


This project was largely developed by directing Claude Code to do the work (even this article was mostly written by Claude, except for this paragraph). This time, I clearly felt the difference compared to a few months ago - it can now handle larger tasks at once, though it still gets stuck in loops sometimes. However, it’s still quite useful for developing small projects like this. Compared to using unfamiliar sources, if the project complexity isn’t too high, it might actually be safer to have an AI write a version directly (although you still have to worry about potential contamination).