Skip to content

Add NOT operator and event parameter conditions to action triggers#217

Draft
skypper wants to merge 1 commit intomasterfrom
feat/improve-actions
Draft

Add NOT operator and event parameter conditions to action triggers#217
skypper wants to merge 1 commit intomasterfrom
feat/improve-actions

Conversation

@skypper
Copy link

@skypper skypper commented Feb 18, 2026

Summary

  • Add not field to function, eventEmitted, logEmitted, and comparable int/str filters (value,
    gasUsed, gasLimit, fee, from, to), allowing users to negate any filter condition in their
    action trigger YAML.
  • Replace the old unsupported parameter map on eventEmitted with typed parameters array supporting
    string (exact match) and int (eq/gt/gte/lt/lte) comparisons against decoded event arguments.
  • Remove the MsgIdAndParameterForbidden constraint — parameters now work with both id and name
    matching.
  • Update generated Conjure structs (ParameterCondition, Not fields on EventEmittedFilter,
    FunctionFilter, LogEmittedFilter, ComparableInt, ComparableStr).

Example YAML

function:
  - contract:
      address: "0x..."
    name: "transfer"
    not: true

eventEmitted:
  - contract:
      address: "0x..."
    name: "Transfer"
    not: true
    parameters:
      - name: from
        string: "0x0000000000000000000000000000000000000000"
      - name: value
        int:
          gte: 1000

Test plan

  • TestTransactionNot — validates not and parameters round-trip through ToRequest() for all affected
    filter types
  • Manual: publish action with not: true filters via CLI, verify correct behavior in
    actions-trigger-service (requires companion PR in tenderly-core)

Add `not` field to function, eventEmitted, logEmitted, and comparable
int/str filters. Replace the old unsupported `parameter` map on
eventEmitted with typed `parameters` supporting string and int
comparisons. Update generated Conjure structs to match.
@skypper skypper self-assigned this Feb 18, 2026
@skypper skypper marked this pull request as draft February 18, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments