Skip to main content
The Whitelisted Callers trigger alerts you any time a transaction reaches the monitored contract from an address that is not in your approved list. This is the inverse of blacklisting — only known, trusted addresses are allowed to interact silently.

​
Use cases

Confirm that only authorized operators, bots, or contracts interact with privileged functions. Any unexpected caller immediately triggers an alert.
Ensure only whitelisted integrations (e.g., your own frontend router or partner contracts) reach the contract. Catches routing bugs and front-running bots.
After a security incident, lock down interaction to a minimal whitelist while you investigate, and get alerted to any attempt to bypass it.

​
Configuration

1

Trigger Name

Enter a descriptive label, e.g. Unauthorized Caller Detected.
2

Whitelisted Entities

Add one or more wallet addresses that are allowed to interact with the contract. Any transaction from an address not on this list will trigger an alert.You can add multiple addresses — use the multi-select field to build the full list.
3

Severity

Choose the alert severity: Critical, High, Medium, Low, or Info.
4

Notification Channels

Select one or more channels to receive the alert (email, Slack, webhook, PagerDuty, etc.).
An empty whitelist means every caller is unauthorized. Make sure to add all legitimate addresses before enabling this trigger, or you will receive an alert for every transaction.