Alerting webhooks

You are here:
Estimated reading time: 3 min


We’re excited to introduce a new feature that leverages the power of webhooks to help you stay on top of important events in your application. Our new webhook alert feature allows you to receive notifications about critical events in real-time as they happen.

Webhooks are a powerful tool for developers that allow real-time communication between applications. They provide a way for your application to automatically receive data from external sources without needing an external source to poll your application for updates. Webhooks work by sending an HTTP POST request to a URL you specify, which contains data relevant to the event that occurred.

It’s important to note that the webhook alert feature is currently limited to three of our modules: the DoS detection module, the WAF 2.0 module, and the Malware Detection module.

If you are using any of these modules, you can set up a webhook to receive real-time notifications about critical events, such as a potential DoS attack, a detected malware threat, or a WAF blocking request. By taking immediate action, you can quickly address these issues and minimize any potential downtime, resulting in a better user experience for your customers.

Setting Up Webhooks in BitNinja

Step 1: Choose which Module You Want to Receive Alerts From:

The first step in setting up webhooks is to choose which BitNinja security module you want to receive alerts from. Currently, the DoS Detection, WAF 2.0 module, and Malware Detection module support webhook integration. Once you’ve decided which module you want to receive alerts from, you can proceed to the next step.

Step 2: Set Up the Webhook Parameters:

To set up webhooks for your BitNinja security modules, you’ll need to configure three parameters:

  • Webhook URL: This is the URL of the third-party or custom webhook service that will receive the alerts from BitNinja.You’ll need to provide this URL in the BitNinja dashboard when setting up webhooks for your module.
  • Threshold: This parameter specifies the number of incidents that must occur before an alert is triggered. For example, if you set the threshold to 5, you’ll receive an alert when the security module detects five incidents that match your criteria.
  • Timeframe: This parameter specifies the amount of time that BitNinja has to reach the threshold. For example, if you set the timeframe to 24 hours and the threshold to 5, BitNinja will trigger an alert if it detects five incidents within
    1-120 minute time period.

Step 3: Test and Monitor Your Webhook Integration:

Once you’ve configured the webhook parameters, you can test your webhook integration by triggering a test alert. You can do this by manually triggering an event that matches your webhook criteria, such as triggering a WAF rule, for example, with Threshold set to 1 and the Timeframe set to 1. (You can learn how to trigger a WAF 2.0 rule manually in this guide: If your webhook integration is working correctly, you should receive an alert at the specified webhook URL.

How can I create a webhook? and offer webhook functionality that allows you to receive notifications when events occur in your account.

Both Zapier and Make offer similar webhook functionality, but some differences between the platforms may make one more suitable for your needs than the other. Here are some factors to consider when choosing between Zapier and Make:

  • Integration options: Both platforms offer various integrations with other apps and services, but Zapier has a more extensive library of pre-built integrations. If you want to connect with a specific app or service, it’s worth checking if it’s available on both platforms.
  • Customization: Make offers more customization options than Zapier, allowing you to create more complex workflows and integrations. Make may be a better choice if you need fine-grained control over how data is processed and transformed.
  • Pricing: Both platforms offer free and paid plans, but the pricing models and feature sets differ. It’s worth comparing each platform’s pricing and features to determine which provides the best value for your needs.
  • User interface: Each platform’s user interface differs, and some users may find one platform more intuitive. It’s worth trying both platforms to see which one you find easier.

Overall, both Zapier and Integromat/ are powerful automation platforms that offer webhook functionality. If you’re looking for a platform with more pre-built integrations and a more straightforward user interface, Zapier may be the better choice. If you need more customization options and control over your workflows, may be a better fit.

Was this article helpful?
It was not helpful
Views: 162