FAQ: Alerts

Try opening the verification link in a new browser tab where you’re already logged into the Dashboard. If this doesn’t work, please contact our support team via the in-app chat or support@tenderly.co.

Alerts and Web3 Actions have a retry mechanism in place and will retry five times.

Learn more about using webhooks as an Alert destination here.

Setting up an Even Emitted Alert type is possible only for contracts that are verified through ABI verification or source code verification.

Learn more about contract verification on Tenderly here.

If you want to create an event or function alert type on a proxy contract, both the proxy and its implementation have to be added to your project in order for all events to be visible.

Will an alert be triggered if an account has 0.51 Ether and it sends a transaction to a smart contract, paying a transaction fee of 0.02 to the validators (the new balance is 0.49 ETH)?

Yes, the alert will be triggered when the balance drops below 0.5 ETH.

Will an alert be triggered if an account already has less than 0.5 Ether? For example, if an account has 0.1 Ether and receives an additional 0.1 from another account (the new balance is 0.2 ETH)?

No, the alert won’t get triggered if the balance continues to decrease. However, if the balance goes above 0.5 Ether and then drops below this threshold, the alert will be triggered.

Tenderly Alerts notify you of on-chain events, such as successful or failed transactions, contract function calls, and token transfers, through various destinations like email, Slack, or webhooks.

To set up an Alert, define the alert type (e.g., transaction), the target address or contract, and the notification destination (e.g., email, webhook).

Alerts can be triggered by successful or failed transactions, function calls, state changes, ERC20 token transfers, balance changes, and more.

Alerts can be sent to email, Slack, Telegram, Discord, PagerDuty, Sentry, or webhooks.

This Alert triggers when a specified transaction is successfully executed, notifying you of wallet, dapp, or contract activity.

Webhooks can be set as destinations to send real-time notifications of on-chain events to external services or applications.

This Alert triggers when a specified contract emits a particular event, such as token approvals or transfers.

Project-scoped Alerts notify you of events within a specific project, while account-scoped Alerts monitor events across all projects in an account.

This Alert notifies you when a transaction fails, which can help detect issues in a dapp or smart contract.

This Alert triggers when an address from a blocklist interacts with your contract, helping to monitor unauthorized access attempts.

Yes, Alerts can help detect suspicious behavior like unauthorized access or unusual token transfers, aiding in early threat detection.

This Alert notifies you when a wallet’s balance changes according to specified conditions, useful for monitoring DAOs or key wallets.

The ERC20 Token Transfer Alert triggers when tokens are transferred, helping track fund movements or suspicious wallet activities.

This Alert triggers when a specific function in a smart contract is called, helping to monitor contract interactions.

This Alert monitors when a view function’s return value meets specified conditions, such as checking token balances.

The Transaction Value Alert notifies you when a transaction’s value exceeds a certain amount, ideal for monitoring high-value transfers.

The State Change Alert triggers when a state variable in a contract changes, such as monitoring the number of confirmations in a multisig.

Alerts can trigger Web3 Actions, enabling automated responses to on-chain events, such as executing custom code when a transaction fails.

This Alert notifies you when an address not on the allowlist interacts with your contract, useful for monitoring restricted access.

Alerts can be sent to multiple destinations, including email, Slack, Telegram, Discord, PagerDuty, and webhooks.