Configure it

Choose Contract event, select chains, and name up to three emitting contract addresses. This watches emitted logs rather than transactions sent to those contracts.

Inspect examples to find the event you want. Where an ABI is available, the event has a name and decoded args. Otherwise topics and data remain available.

Contract Event Trigger Configuration

1Event source

Contract event

Selection

2Filters

Edit the conditions to explore the controls. Event samples stay fixed.

Inspect Example triggers to check your selection.

3Trigger

Chains

EthereumBaseArbitrum

1 selected · 3 of 7 chains shown

Example. With a decoded example, use its event name to narrow the logs. Enter the full emitting contract address in the app.Changes stay in this example. Nothing is saved or sent.

Filter the event

Use the event name or topic0 to narrow to a particular event. For decoded events, nested fields such as args.value can be filtered directly. Check the example’s units: a decoded integer may still be a raw amount rather than a token amount adjusted for decimals.

If decoded is false, do not assume the event has no arguments. It means the readable interpretation is unavailable. Add Decode with the appropriate ABI when you need to interpret raw data.

Contract Event Filters

Filters

Edit the conditions to explore the controls. Event samples stay fixed.

Event shape

name

Transfer

decoded

true

args.value

25000000

Example. Select Event and a nested argument in Filters. This example compares raw USDC units: 25000000 represents 25 USDC.Changes stay in this example. Nothing is saved or sent.

Event versus transaction

contract_address identifies the emitter. Transaction context such as tx_from helps identify who submitted the transaction. A transaction can emit multiple matching logs and therefore cause multiple runs.

Event Emitter and Transaction Context

Event shape

contract_address

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

tx_from

0x1111111111111111111111111111111111111111

name

Transfer

Example triggers

Transfer · log 0Transaction 0xaaaa…aaaa

Transfer · log 1Transaction 0xaaaa…aaaa

Two events from the same transaction. Hashes are shortened for display.

Example. Inspect an example’s event fields. The emitting contract and transaction sender are different roles; two matching logs in one transaction can produce two runs.Changes stay in this example. Nothing is saved or sent.