Trigger Onchain

Triggers when tokens leave a wallet address. Filter by recipient, specific token, or minimum amount.

At a Glance

FieldValue
Trigger IDerc20-send
CategoryOnchain
Tagserc20, token, transfer, send, withdrawal, blockchain, evm, wallet

Trigger Configuration

FieldTypeRequiredDescription
chainIdintegerYesChain ID to monitor (e.g., 1 for Ethereum, 42161 for Arbitrum, 8453 for Base)
fromAddressstringYesThe address sending tokens (the wallet to monitor)
tokenAddressstringNoOptional: specific token contract address. If omitted, triggers on any ERC-20 token.
toAddressstringNoOptional: filter by recipient address
minAmountstringNoOptional: minimum transfer amount in wei (token's smallest unit)
enrichmentsarrayNoAdditional data to include with each event. Each enrichment adds an RPC call (and sometimes a price lookup) per trigger.
enrichmentFilterobjectNoFilter applied to enrichment results. Only fires when enriched data matches. Same syntax as event filter ($and/$or with $eq, $gt, $gte, $lt, $lte, $in, etc.).

Trigger Result

FieldTypeRequiredDescription
triggeredAtstringYesTimestamp when the transfer was detected (UTC, RFC3339 format)
paramsobjectYesDecoded transfer parameters
rawobjectYesRaw EVM log data including address, topics, data, blockNumber, transactionHash, etc.
enrichmentsobjectNoAdditional data from opt-in enrichments. Only populated when the corresponding enrichment is enabled.

Workflow Root Example

json
{ "nodes": { "root": { "type": "erc20-send", "payload": { "chainId": 8453, "fromAddress": "0x0000000000000000000000000000000000000000" }, "children": [ "log_event" ] }, "log_event": { "type": "log", "payload": { "message": "Triggered at {{$trigger.triggeredAt}}" }, "children": [] } }}

Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.

Ask a question... ⌘I