DocsIntegrationsSlack, Teams & webhooks

Slack, Teams & webhooks.

Chat and webhook alerts are free and unlimited. Add the webhook URLs once as account defaults, then switch them on per URL.

On this page

Account defaults

Go to Account → Preferences → Default Webhook URLs and fill in the channels you use. Verify sends a real test message and shows whether it arrived. In a project without alert settings yet, new URLs start with these defaults switched on; in other projects new URLs copy the settings of the project's other URLs. Defaults are also filled in when you switch a channel on in a URL's alert settings, and you can still change them per URL.

ChannelURL must be on
Slackhooks.slack.com
Microsoft Teams*.webhook.office.com, *.logic.azure.com, *.powerplatform.com or outlook.office.com
Google Chatchat.googleapis.com
Custom webhookAny https:// URL

Slack

  1. In Slack, create an app for your workspace, turn on Incoming Webhooks and add a webhook to the channel that should receive alerts.
  2. Copy the webhook URL (https://hooks.slack.com/services/…) into Search Sentinel.

Alerts arrive as a formatted message. To send different URLs to different channels, use a different webhook URL per URL.

Microsoft Teams

  1. In Teams, add a Workflows (Power Automate) flow that posts to a channel when a webhook request is received, or an incoming webhook.
  2. Copy the URL it gives you into Search Sentinel.

Alerts arrive as an Adaptive Card.

Google Chat

  1. In a Google Chat space, open Apps & integrations → Webhooks and add a webhook.
  2. Copy the URL into Search Sentinel.

Google Chat receives URL change alerts and domain health alerts.

Custom webhook

Give the webhook a name (optional, like "n8n production") and an HTTPS URL. Search Sentinel sends a JSON POST with the header User-Agent: SearchSentinel/1.0 for URL change and domain health alerts. Use it with a Zapier, Make or n8n catch hook, or your own endpoint.

Payload

{
  "source": "Search Sentinel",
  "webhook_name": "n8n production",
  "alert_type": "url_change",
  "timestamp": "2026-11-13T09:14:02.000Z",
  "timestamp_formatted": "Nov 13, 2026, 10:14 AM (UTC: Nov 13, 2026, 09:14 AM)",
  "url": "https://www.example-shop.com/products/running-shoes/",
  "monitored_url_id": "8f0c…",
  "changes_count": 1,
  "changes": [
    {
      "type": "canonical_url_1",
      "type_label": "Canonical URL",
      "old_value": "https://www.example-shop.com/products/running-shoes/",
      "new_value": "https://www.example-shop.com/products/"
    }
  ],
  "summary": "Website change detected on https://www.example-shop.com/products/running-shoes/: 1 change found",
  "is_test": false
}

The values above are an example. Field reference:

FieldMeaning
sourceIdentifies Search Sentinel as the sender
webhook_nameThe name you gave the webhook
alert_typeurl_change, domain_health or core_web_vitals
timestampISO 8601 time of detection
timestamp_formattedThe same time, readable, in your timezone
url, monitored_url_idThe URL and its ID in Search Sentinel (URL change alerts)
domain, project_idThe domain and project, instead of url (domain health alerts)
changes_countNumber of changes in this check
changes[]type, type_label, old_value, new_value per change; domain health changes can add expires_at, days_until_expiry and alert_stage (expiring, final_reminder, expired or renewed; renewals use the types ssl_renewed and domain_renewed)
summaryA one-line summary
is_testtrue for Send Test Alert and Verify

Delivery rules

  • HTTPS only. Redirects are not followed. The request times out after 10 seconds.
  • Each alert is sent once. There are no retries, signatures or custom headers, so make your endpoint fast and reliable.
  • The result of every delivery shows in the URL's alert history.