Tailflow
Skip to article
Browse documentation

Triggers

Transaction in Contract

Watch transactions sent to a contract and inspect their calldata and logs.

Configure it

Choose Transaction in Contract, select chains, and enter one destination contract address. This selects transactions whose recipient is that address, not every transaction that indirectly interacts with it.

Both successful and reverted transactions can appear. Filter Succeeded or the status fields when you only want successful calls.

Contract Transaction Trigger Configuration
1Event source
Transaction in Contract
2Filters
Edit the conditions to explore the controls. Event samples stay fixed.
Inspect Example triggers to check your selection.
3Trigger
Chains
1 selected · 3 of 7 chains shown
Example. Select one destination contract, then filter successful calls. Enter a full contract address in the app.Changes stay in this example. Nothing is saved or sent.

Inspect a transaction

Examples include the sender, recipient, value, function selector, input, and transaction status. Value is also available in human-readable native-currency units. Token transfers inside a transaction are different from its native value.

The logs array contains events from the transaction, including events emitted by other contracts. Named arguments are available where decoding succeeds; other logs keep their raw data.

Transaction Input and Event Logs
Event shape
input
0xa9059cbb…
succeeded
true
from_address
0x1111111111111111111111111111111111111111
Event shape · logs
logs.0.name
Transfer
logs.0.address
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
logs.0.args.value
25000000
Example. Select a transaction example. Input describes the request; Succeeded tells you whether the transaction succeeded.Changes stay in this example. Nothing is saved or sent.

Read a function call

Add Decode with Encoded data set to {{ event.input }} and select the ABI for the called contract. An ABI describes the contract’s functions and events; using the wrong one may prevent decoding.

Use the output picker after a test to insert decoded arguments into a later action. A decoded call describes what was requested; check the transaction status to determine whether it succeeded.

Decode Action Configuration
Path 1
Every event
Decode
Selected action
1Decode
Continue on error
A failure stops later actions on this path.
Example. Encoded data selects the input to interpret. Choose the ABI for that contract, then test to inspect the decoded arguments.Changes stay in this example. Nothing is saved or sent.