Notification channels, credentials & operator access
Open Agent → Channels in the App. Each channel has different credentials; configure only the channels you actually use. Tokens, passwords, and webhook URLs are stored only on this Sentinel computer and are never returned to the UI. After configuration, validate with a safe test event or command—do not wait for a real critical incident.
Choose the right channel first
| Channel | Use | What to enter | Two-way? |
|---|---|---|---|
| Telegram | Best for small venues and operators; snapshots, queries, and commands. | Bot Token, Chat ID | Yes |
| Slack Commands | Queries and commands inside company Slack. | Bot Token, App Token, allowed User IDs | Yes |
| Slack Alerts / Google Chat | Send alerts to a channel or space. | Incoming Webhook URL | No |
| LINE / Email / Discord / Teams | Receive alerts through an existing work habit. | Channel-specific values below | No |
| Webhook | n8n, Make, Zapier, WhatsApp, SMS, PagerDuty, or your backend. | Receiver URL and optional HMAC secret | Through your workflow |
Telegram: complete this one first
- Find @BotFather in Telegram, send
/newbot, then copy the Bot Token. - Find the new bot and send one ordinary message such as
hi. - Open
https://api.telegram.org/bot<yourToken>/getUpdatesin a browser and find the numericchat.idin the response. - Enter Bot Token and Chat ID in the Telegram card, then save.
- Send
/statusto the bot. A camera summary confirms the two-way connection.
Useful commands: /status, /recent 10, /snapshot 1, and /watch 1 Watch the rear door for loitering. The first Chat ID receives critical alerts by default; separate multiple recipients with commas.
Slack: decide alerts-only or commands
Slack Alerts is simplest: create an Incoming Webhook in a Slack App, choose the destination channel, and paste the URL into the Slack alerts card. It delivers alerts only.
Slack Commands uses Socket Mode and does not require a public Sentinel computer. Create a Slack App, enable Socket Mode, create an App-Level Token with connections:write (xapp-…), install the App for a Bot Token (xoxb-…), and enter allowed Slack User IDs. Test by DMing /status to the bot. Only listed users with the right role can operate it.
Other alert-only channels: where credentials come from
- Google Chat: create an Incoming Webhook in the Workspace space and paste its URL.
- LINE: create a Messaging API channel in LINE Developers and enter its Channel Access Token plus destination user/group ID. This version sends text alerts; use Telegram, email, Discord, or a webhook for photos.
- Email: enter SMTP Host, Port (usually 587), account, App Password, From, and one or more To addresses. Use an App Password for Gmail/Microsoft where available. A successful alert contains text and a JPEG attachment.
- Discord: create a Webhook in the target channel’s Integrations settings and paste its URL; critical snapshots are attached.
- Microsoft Teams: create a Workflows/Power Automate flow that posts when a webhook request arrives, then paste the Workflow Webhook URL. This version sends a text card.
Webhook: use this for your own system or WhatsApp
Enter your workflow receiver URL and an HMAC secret. Sentinel posts signed JSON to that URL; the receiver must verify X-Sentinel-Signature against the raw request body before parsing it. This is the right way to reach WhatsApp, SMS, PagerDuty, Trainge, or your backend—never give a third-party workflow your RTSP URL or Sentinel token.
Permissions: who can reply or command?
viewer can query status and snapshots; operator can use /watch; admin can manage long-term notes. A single trusted operator can begin without roles; multi-person venues should define roles and make the default viewer.
SENTINEL_CLAW_ROLES={"8765432":"admin","U0456WXYZ":"operator"}
SENTINEL_CLAW_DEFAULT_ROLE=viewer