Integrations
An integration is a stored credential or webhook URL connecting SiteQwality to an external service. Once an integration exists, you can create notification channels that deliver to it.
The split exists because:
- One integration → many channels. One Slack workspace integration can fan into 20 different channels (
#ops,#deploys,#alerts-billing, …). - Credentials are reusable. You connect Slack once via OAuth; you don’t re-enter the workspace every time you want a new channel.
Chat and messaging
Section titled “Chat and messaging” Slack OAuth-installed app. Posts rich blocks to any channel; supports interactive Acknowledge and Resolve buttons.
Microsoft Teams Incoming webhook URL from a Teams channel connector. Posts Adaptive Cards.
Discord Incoming webhook URL from a Discord channel. Posts embeds.
Telegram Bot-based via setup-code flow. Direct messages or group chats.
Google Chat Incoming webhook URL for a space. Posts card messages.
Mattermost Incoming webhook URL, self-hosted or Cloud. Posts Slack-style attachments.
On-call and paging
Section titled “On-call and paging” PagerDuty Events API v2. Outages trigger an incident; recoveries resolve the same incident automatically.
OpsGenie Alerts API. Outages create an alert; recoveries close it automatically by alias.
Push to your devices
Section titled “Push to your devices” Pushover User key plus an application token. Outages arrive at high priority.
Pushbullet Account access token. Note pushes to every signed-in device.
Anything else
Section titled “Anything else” Webhooks Generic outbound webhook URL. POSTs incident JSON to your endpoint.
How integrations and channels relate
Section titled “How integrations and channels relate”Integrations Notification channels Notification group(account-level) (group-level) (monitor-level)
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐│ Slack workspace │ ←── │ Channel: #ops │ ─┐ │ ││ (one OAuth) │ └──────────────────┘ │ │ "Default group" ││ │ ┌──────────────────┐ ├──→ attached →│ ││ │ ←── │ Channel: #alerts │ ─┤ │ │└──────────────────┘ └──────────────────┘ │ │ │ ┌──────────────────┐ │ │ │ │ Channel: webhook │ ─┘ │ │ └──────────────────┘ └──────────────────┘So the typical setup flow is:
- Connect the integration (one-time OAuth or webhook URL).
- Create a notification channel referencing that integration with the per-channel detail (the Slack channel name, the Telegram chat ID).
- Add the channel to a notification group.
- Attach the group to your monitors.
Pricing
Section titled “Pricing”Integrations themselves are free. Delivery costs (SMS, phone calls) are extra and per-message; see Notifications.
See also
Section titled “See also” Notification channels The next step after connecting an integration.
Notifications overview Channels, groups, contact methods, rules.