How to Set Up Notification Handlers in Klik VIP

Created on 15 September, 2026User Guide • 13 views • 4 minutes read

Learn how to create reusable Notification Handlers in Klik VIP for Email, Webhook, Slack, Discord, Telegram, Microsoft Teams and Google Chat, then test each integration before live use.

Quick summary Notification Handlers let you save reusable notification destinations in Klik VIP. Create a handler, choose the destination type, complete the required details, then use Test integration before using it in a live workflow.

What are Notification Handlers?

Notification Handlers are reusable notification destinations inside Klik VIP. Instead of entering the same destination details repeatedly, you can create a handler once and reuse it wherever Klik VIP supports Notification Handlers.

Email

Send notifications to a verified email address.

Webhook-based services

Connect services such as Webhook, Slack, Discord, Microsoft Teams and Google Chat using the required webhook URL.

Telegram

Use a Telegram bot API Token together with the destination Chat ID.

Other supported types

The current interface also shows X tweet, Internal notification and Push notification.

1. Open Notification Handlers

Open Notification handlers from the Klik VIP dashboard. This page shows your existing handlers. Click Create notification handler to add a new one.

Klik VIP Notification Handlers page
Open the Notification Handlers page and start a new handler.
Click or tap the image to view full size.

2. Name It and Choose a Type

Enter a clear internal name for the handler, then choose the notification destination you want to use. The selected type controls which setup field appears below.

Example names: Sales Webhook, Support Telegram, Team Slack or Operations Google Chat.
Klik VIP Notification Handler name and type selection
Give the handler a recognizable name and select its notification type.
Click or tap the image to view full size.

3. Configure the Integration

After choosing a notification type, complete the field shown by Klik VIP. For Webhook, paste the destination Webhook URL. Slack and Discord follow the same pattern with their own service-specific webhook URL.

  • Webhook — paste the endpoint URL that should receive the POST notification.
  • Slack — paste the Slack webhook URL for the destination channel.
  • Discord — paste the Discord webhook URL for the destination channel.

Click Create to save the handler, then use Test integration to verify the connection.

Configure a Webhook notification handler in Klik VIP
Paste the required webhook URL, create the handler and test the integration.
Click or tap the image to view full size.

4. Configure Telegram

Telegram requires two values:

  • Telegram API Token — the token received after creating your Telegram bot.
  • Telegram Chat ID — the destination chat where the bot should send messages.

Enter both values, click Create, then run Test integration.

Configure Telegram Notification Handler in Klik VIP
Telegram needs both the bot API Token and the destination Chat ID.
Click or tap the image to view full size.

5. Configure Microsoft Teams or Google Chat

Microsoft Teams and Google Chat both use service-specific webhook URLs. Select the correct type, paste the URL supplied by that service, click Create, then verify it with Test integration.

Configure Microsoft Teams or Google Chat Notification Handler in Klik VIP
Teams and Google Chat each use their own webhook URL.
Click or tap the image to view full size.

6. Tips & troubleshooting

Best practices

  • Use clear names so you can immediately recognize each handler later.
  • Always run Test integration before relying on the handler in a live workflow.
  • Check that webhook URLs are complete and still active if a test fails.
  • For Telegram, verify both the API Token and Chat ID.
  • Treat webhook URLs and API tokens as credentials and avoid exposing real values publicly.
Quick reminder: Email uses an email address, Telegram uses an API Token plus Chat ID, while Webhook, Slack, Discord, Microsoft Teams and Google Chat use destination URLs.