Skip to content


Telegram is a cloud-based instant messaging platform and social media application. You can set up Wallarm to send scheduled reports and instant notifications to Telegram.

Scheduled reports can be sent on a daily, weekly, or monthly basis. Reports include detailed information about vulnerabilities, attacks, and incidents detected in your system over the selected period. Notifications include brief details of triggered events.

Setting up integration

  1. Open the Integrations section.

  2. Click the Telegram block or click the Add integration button and choose Telegram.

  3. Add @WallarmUSBot (if you are using the Wallarm US Cloud) or @WallarmBot (if you are using the Wallarm EU Cloud) to the Telegram group receiving Wallarm notifications and follow the authentication link.

  4. After redirection to Wallarm UI, authenticate the bot.

  5. Enter an integration name.

  6. Choose the frequency of sending security reports. If the frequency is not chosen, then reports will not be sent.

  7. Choose event types to trigger notifications.

    Telegram integration

    Details on available events:

    • System related:
      • User changes (newly created, deleted, role change)
      • Integration changes (disabled, deleted)
      • Application changes (newly created, deleted, name change)
    • Vulnerabilities detected, all by default or only for the selected risk level(s):
      • High risk
      • Medium risk
      • Low risk
    • Rules and triggers changed (creating, updating, or deleting the rule or trigger)
    • Scope (exposed assets) changed: updates in hosts, services, and domains

    The integration with Telegram can be tested only if this integration is already created.

  8. Click Add integration.

  9. Re-open the created integration card.

  10. Click Test integration to check configuration correctness, availability of the Wallarm Cloud, and the notification format.

    This will send the test notifications with the prefix [Test message]:

    [Test message] [Test partner] Network perimeter has changed
    Notification type: new_scope_object_ips
    New IP addresses were discovered in the network perimeter:
    Client: TestCompany
    Cloud: EU

You can also start the chat with @WallarmUSBot or @WallarmBot directly. The bot will send reports and notifications as well.

Setting up additional alerts

Besides the notifications you have already set up through the integration card, Wallarm triggers allow you to select additional events for notifications:

For condition detailing, you can add one or more filters. As soon, as condition and filters are set, select the integration through which the selected alert should be sent. You can select several integrations simultaneously.

Choosing an integration

Disabling and deleting an integration

You can delete or temporarily disable the integration. While deleting stops sending notificatioins and completely deletes all configuration, disabling just stops sending notifications which you can at any moment re-enable with the same settings.

If for the integration the System related events are selected to trigger notifications, Wallarm will notify about both of these actions.

System unavailability and incorrect integration parameters

Notifications to the system are sent via requests. If the system is unavailable or integration parameters are configured incorrectly, the error code is returned in the response to the request.

If the system responds to Wallarm request with any code other than 2xx, Wallarm resends the request with the interval until the 2xx code is received:

  • The first cycle intervals: 1, 3, 5, 10, 10 seconds

  • The second cycle intervals: 0, 1, 3, 5, 30 seconds

  • The third cycle intervals: 1, 1, 3, 5, 10, 30 minutes

If the percentage of unsuccessful requests reaches 60% in 12 hours, the integration is automatically disabled. If you receive system notifications, you will get a message about automatically disabled integration.