Skip to main content

Notification Channels

KWatch.io offers multiple ways to receive notifications when your keywords are detected across social media platforms. This guide will help you set up and manage your notification preferences.

Email Notifications​

Email notifications are the simplest way to stay informed about your keyword matches. Here's how to set them up:

  1. Enter your preferred email address in the "Notification Email" field. By default, the email address is the one you used to sign up for KWatch.io, but you can enter another email address if you prefer.
  2. Toggle the checkbox to enable/disable email notifications
  3. Click "Save" to apply your changes

Note: When receiving email notifications, large content is automatically truncated to ensure optimal delivery. If you need the full content, consider using Slack or API webhooks instead.

Slack Notifications​

Slack notifications allow you to receive real-time updates directly in your Slack workspace. Here's how to set them up:

Create a Slack app and get your webhook URL:

  1. Go to https://api.slack.com/apps
  2. Click "Create New App"
  3. Choose "From scratch" and give your app a name
  4. Select your workspace
  5. In the "Add features and functionality" section, click "Incoming Webhooks"
  6. Toggle "Activate Incoming Webhooks" to On
  7. Click "Add New Webhook to Workspace"
  8. Choose the channel where you want to receive notifications
  9. Copy the Webhook URL

In KWatch.io you can either set a global Slack webhook for your account, or set a webhook per alert.

In order to set a global Slack webhook for your account, you can do the following:

  1. Go to the "Notifications" section
  2. Paste your Slack webhook URL in the "Slack Webhook URL" field
  3. Click the "Test Webhook URL" button to ensure you are receiving notifications
  4. Toggle the checkbox to enable the webhook
  5. Click "Save" to apply your changes

In order to set a webhook per alert, you simply need to fill in the "Slack Webhook URL" field when creating or editing an alert.

Please note that if you create both a global and a per-alert webhook, the per-alert webhook will take precedence.

API Webhooks​

API webhooks allow you to integrate KWatch.io notifications with your own systems and applications.

Use API webhooks to:

  • Store mentions in your own database
  • Trigger automated responses
  • Create custom dashboards
  • Interface with other services
  • Integrate with your CRM or marketing tools

API Webhook Setup​

In KWatch.io you can either set a global API webhook for your account, or set a webhook per alert.

In order to set a global API webhook for your account, you can do the following:

  1. Enter your webhook URL in the "API Webhook URL" field
  2. Click the "Test Webhook URL" button to ensure you are receiving notifications
  3. Toggle the checkbox to enable the webhook
  4. Click "Save" to apply your changes

In order to set a webhook per alert, you simply need to fill in the "API Webhook URL" field when creating or editing an alert.

Please note that if you create both a global and a per-alert webhook, the per-alert webhook will take precedence.

API Webhook Payload Format​

When a keyword is detected, KWatch.io will send a POST HTTP request to your webhook URL with a JSON payload.

API Webhook Payload Fields​

The JSON payload contains the following information:

FieldTypeDescription
platformstringThe social media platform where the keyword was detected. Possible values: "reddit", "hacker_news", "twitter", "linkedin", "quora", "youtube", "facebook"
querystringThe keywords that triggered the alert
datetimestringThe date and time when the content was posted
linkstringThe URL to the post or comment containing your keyword
authorstringThe author of the content. For Twitter, includes username, full name, and follower count
contentstringThe full text content. For YouTube, includes video length at the beginning
sentimentstringAI-powered sentiment analysis of the content. Possible values: "positive", "negative", "neutral"

API Webhook Example Payload​

{
    "platform": "reddit",
    "query": "Keywords: vllm",
    "datetime": "19 Jan 24 05:52 UTC",
    "link": "https://www.reddit.com/r/LocalLLaMA/comments/19934kd/sglang_new/kijvtk5/",
    "author": "lmzoo",
    "content": "sglang runtime has a different architecture on the higher-level part with vllm.",
    "sentiment": "neutral"
}