Ethereum Trigger
AI-generatedSummary
Listen to specified Ethereum events via polling and emit decoded event data
Inputs
- event (required) — Type of event to trigger on (newBlock, contractEvent, transaction)
- pollTimes — Poll schedule; can be repeated or custom intervals
- addresses — Comma‑separated contract addresses to monitor for contract events
- abiInput — Method of providing contract ABI (abiEvent or topics)
- abi (required) — Contract ABI as a JSON array (required when abiInput is abiEvent)
- eventName (required) — Name of the contract event to filter (required when abiInput is abiEvent)
- eventArgs — Optional JSON filter for indexed arguments of the event
- topics (required) — Event topics array as JSON (required when abiInput is topics)
- fromBlock — Block range filter for contract events (latest, earliest, or custom)
- blockNumber — Specific block number to start scanning from for contract events
- direction — Transaction direction filter (all, from, to, valueTransfer)
- txAddresses (required) — Comma‑separated addresses to monitor for transaction events
- txFromBlock — Block range filter for transaction events (latest, earliest, or custom)
- txFromBlockNumber — Specific block number to start scanning from for transaction events
Output shape
an array of event records (or null if no new events)
State is persisted between runs; each record contains parsed details such as block number, hash, timestamp, and decoded arguments
Examples
Example 1: Listen for new blocks
Select event = newBlock; keep default poll schedule; optionally adjust pollTimes
Example 2: Watch a contract for a specific event
Set event = contractEvent; provide abi, eventName, optionally eventArgs and topics; optionally specify addresses and fromBlock
Example 3: Monitor ETH transfers to an address
Select event = transaction; provide txAddresses, choose direction = to or valueTransfer