Skip to main content
Web3 Actions automate responses to blockchain events. This guide shows how to set up Alerts as triggers for Web3Actions, so an action runs whenever its alert conditions are met.
This guide assumes you have a Tenderly account and basic familiarity with Web3Actions.

​
Prerequisites

Before you begin, make sure you have:
  • Tenderly CLI installed
  • A Tenderly account with appropriate permissions
  • Basic understanding of Web3Actions

​
Setup Process

You can set up Alert triggers for Web3Actions through either the UI or CLI approach.

​
Understanding the Configuration

Here’s what each configuration element means:
  • account_id and project_slug: Identify your Tenderly account and project
  • runtime: Specifies the runtime version for your action
  • sources: Indicates the directory containing your action code
  • specs: Defines the specifications for your action
  • trigger: Configures how your action is triggered
  • execution_type: Determines how multiple instances are handled

​
Best Practices

  1. Use descriptive names for your actions and alerts
  2. Keep your action code modular and focused
  3. Use environment variables for sensitive information
  4. Test thoroughly before deployment
  5. Monitor your action executions regularly

​
Troubleshooting

If you encounter issues:
  • Verify the Web3 Action is added as a destination on the Alert
  • Check alert conditions are properly configured
  • Review Tenderly dashboard logs for errors
  • Ensure CLI is up to date and properly authenticated
If your action isn’t triggering, first check the alert configuration and action logs in the Tenderly dashboard.