Alerts
Overview
The PRIZM platform can automatically send notifications to users or external systems when a predefined alert is triggered.
Supported Alert Methods
- Email: Sends a formatted email to one employee of your company, at the email address on their profile.
- SMS: Sends a text message to one employee of your company, at the phone number on their profile.
- HTTP Webhook: Sends a
POSTrequest to a specified URL, allowing for integration with third-party services like Slack, PagerDuty, or custom applications. - Notification: Sends an in-app notification (shown in the sidebar bell icon) titled “Alert Triggered!”
Email and SMS can’t reach anyone outside your company. To alert several people, add one action per employee. To reach an outside address or number, use an HTTP Webhook.
An SMS action fails silently if its recipient later removes their phone number. The editor only lets you pick employees who have a phone number in their profile settings, but nothing rechecks it afterwards: if the number is removed, the alert sends nothing and nothing tells you so.
Cost
Every action that completes successfully costs 10,000 credits, and every method above costs the same, including HTTP Webhook and Notification. A failed action is not charged.
Before an alert runs, PRIZM checks that your company can afford all of its actions. If it can’t, the whole alert is blocked and nothing is sent, not even the actions it could have afforded. See Billing & Plan.
Configuring HTTP Webhook Alerts
To integrate PRIZM alerts with an external system, you can configure an HTTP webhook. This is done by defining the target endpoint’s url and any necessary headers.
Configuration Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url | String | Yes | The destination URL where the POST request will be sent. |
headers | Object | No | A key-value map of custom HTTP headers to include in the request, such as for authentication (Authorization). |
Payload Specification
When an alert is triggered, PRIZM sends a POST request to the configured url with a Content-Type: application/json header and the following JSON body:
| Field | Type | Description |
|---|---|---|
deviceId | String | The unique identifier of the device that triggered the alert. |
text | String | The descriptive message of the alert. |