Alert Integrations
Send alert and automation notifications to the tools your team already uses. All notification integrations are free on every plan and configured per-rule, so different rules can go to different channels.
Available Channels
Section titled “Available Channels”| Channel | What You Need | Cost |
|---|---|---|
| Your account email | Free (all plans) | |
| SMS | Verified phone number | Business+ plans |
| Discord | Discord webhook URL | Free (all plans) |
| Slack | Slack webhook URL | Free (all plans) |
| Telegram | Bot token + chat ID | Free (all plans) |
| Custom Webhook | Any HTTP(S) URL | Free (all plans) |
| Send Command | Target device with commands | Free (all plans) |
Discord
Section titled “Discord”Post rich alert messages to a Discord channel.
- In your Discord server, go to Server Settings > Integrations > Webhooks
- Click New Webhook
- Choose the channel where alerts should appear
- Click Copy Webhook URL
- In SiliconWit.IO, create or edit an alert and check Discord
- Paste the webhook URL
What Gets Posted
Section titled “What Gets Posted”Discord receives a rich embed with:
- Alert name and condition details
- Device name with a link to the device page
- Timestamp in UTC
- Red accent color for visibility
Post alert messages to a Slack channel using incoming webhooks.
- Go to api.slack.com/apps and create a new app (or use an existing one)
- Under Features, click Incoming Webhooks and toggle it on
- Click Add New Webhook to Workspace
- Choose the channel and click Allow
- Copy the webhook URL (starts with
https://hooks.slack.com/services/...) - In SiliconWit.IO, create or edit an alert and check Slack
- Paste the webhook URL
What Gets Posted
Section titled “What Gets Posted”Slack receives a formatted message with:
- Alert name as a header
- Device name, condition value, and timestamp
- A “View Device” button linking to the dashboard
Telegram
Section titled “Telegram”Send alert messages to a Telegram group, channel, or direct message.
Step 1: Create a Bot
Section titled “Step 1: Create a Bot”- Open Telegram and search for @BotFather
- Send
/newbotand follow the prompts to name your bot - BotFather will give you a bot token like
123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11 - Save this token
Step 2: Get Your Chat ID
Section titled “Step 2: Get Your Chat ID”For a group or channel:
- Add your bot to the group or channel
- Send a message in the group
- Open
https://api.telegram.org/bot<YOUR_TOKEN>/getUpdatesin a browser - Find the
"chat":{"id": ...}value (it will be negative for groups, e.g.-1001234567890)
For direct messages:
- Send any message to your bot
- Open the
getUpdatesURL above - Find your chat ID in the response
Step 3: Configure in SiliconWit.IO
Section titled “Step 3: Configure in SiliconWit.IO”- Create or edit an alert and check Telegram
- Enter your bot token and chat ID
What Gets Sent
Section titled “What Gets Sent”Telegram receives an HTML-formatted message with:
- Alert name in bold
- Device name, condition value, and timestamp
- A link to the device page
Custom Webhook
Section titled “Custom Webhook”POST a JSON payload to any URL when an alert fires. This is the most flexible option and works with any service that accepts HTTP requests.
- Create or edit an alert and check Webhook
- Enter your endpoint URL (must start with
https://orhttp://)
JSON Payload
Section titled “JSON Payload”Your endpoint receives a POST request with this JSON body:
{ "event": "alert.triggered", "alert": { "id": "alert-uuid-here", "name": "High Temperature", "condition_value": "temperature = 42.5 (threshold: > 40)" }, "device": { "id": "device-uuid-here", "name": "Office Sensor" }, "data": { "temperature": 42.5, "humidity": 35 }, "timestamp": "2026-02-10T14:30:00.000Z"}| Field | Description |
|---|---|
event | Always alert.triggered |
alert.id | The alert’s unique ID |
alert.name | The alert name you configured |
alert.condition_value | Human-readable description of what triggered |
device.id | Device UUID |
device.name | Device name |
data | The full telemetry payload that triggered the alert |
timestamp | ISO 8601 timestamp |
Example: n8n Workflow
Section titled “Example: n8n Workflow”- In n8n, add a Webhook trigger node
- Set method to POST
- Copy the webhook URL from n8n
- Paste it into SiliconWit.IO as the custom webhook URL
- Build your workflow (e.g. filter by severity, send to multiple destinations)
Example: Node-RED
Section titled “Example: Node-RED”- Add an http in node set to POST
- Connect it to your processing flow
- Use the Node-RED endpoint URL as the custom webhook URL
Example: Zapier / Make
Section titled “Example: Zapier / Make”- Create a new Zap/Scenario with a Webhooks trigger
- Copy the webhook URL
- Paste it into SiliconWit.IO
- Map the JSON fields to your downstream actions
Using Multiple Channels
Section titled “Using Multiple Channels”Each alert can have multiple actions enabled simultaneously. For example, a critical temperature alert could:
- Send an email to the on-duty engineer
- Post to the #alerts channel on Slack
- Send a Telegram message to the ops group chat
- Fire a custom webhook to trigger an automated response
Configure this by checking multiple action checkboxes when creating or editing the alert.
Next Steps
Section titled “Next Steps”- Alerts - Alert types, conditions, and configuration
- Automation - Create rules with notification and device actions
- API Overview - Integrate with your systems