Notifications
When an incident is created, updated, or resolved, isthisthing.online sends notifications through your configured channels. Here's how the system works end-to-end.
Notification channels
| Channel | Description | Plan |
|---|---|---|
| Default alerts sent to your account email. | All | |
| Slack | Posts to a Slack channel via Incoming Webhooks. | Starter+ |
| Discord | Sends to a Discord channel via Webhooks. | Starter+ |
| Microsoft Teams | Posts to a Teams channel via connectors. | Starter+ |
| Webhook | Generic HTTP POST to any URL with optional signing secret. | Starter+ |
| ClickUp | Sends to ClickUp Chat via webhook. | Starter+ |
| Plan | Max integrations |
|---|---|
| Free | 0 (email only) |
| Starter | 3 |
| Pro | 10 |
| Enterprise | Unlimited |
Free plans receive email notifications only. Starter and above unlock all five integration channels.
How notifications are delivered
- An event occurs — an incident is created, updated, or resolved.
- A notification job is added to the queue.
- Workers pick up the job and deliver it to each enabled integration.
- The delivery status is recorded in the integration's event history.
Event types
Each integration can be configured to fire on specific events:
| Event | When it triggers |
|---|---|
| Incident Created | A new incident is detected or created. |
| Incident Resolved | An incident is marked as resolved. |
| Incident Updated | An incident's details or status changes. |
You can enable or disable each event type per integration in the integration settings.
Notification payload
Each notification includes:
- Incident title and description.
- Current status (Open, Investigating, Monitoring, Resolved).
- Source (Monitor or Manual).
- Monitor details (name, type, URL).
- Workspace name.
- Deep link to the incident in the dashboard.
- Timestamps (created, resolved, updated).
Retry logic
If a notification delivery fails:
- The system retries up to 3 times.
- Retries use exponential backoff: 30 seconds, then 2 minutes, then 10 minutes.
- After 3 failed attempts, the notification is moved to dead letter and will not be retried.
Testing an integration
- Go to Integrations.
- Find the integration you want to test.
- Click the Test button.
- A sample notification is sent to the channel.
If the test fails, check your integration configuration and make sure the webhook URL or token is correct.
Viewing delivery history
- Go to Integrations.
- Select an integration.
- Click Event History.
You'll see each notification delivery with its status:
| Status | Meaning |
|---|---|
| Pending | Queued, waiting to be processed. |
| Processing | Currently being delivered. |
| Delivered | Successfully sent to the channel. |
| Failed | Delivery failed, will be retried. |
| Dead Letter | Failed after all retries, will not retry. |
Configuring per-integration events
- Go to Integrations.
- Open an integration.
- Toggle the event types you want:
- On Incident Created.
- On Incident Resolved.
- On Incident Updated.
- Click Save.
You can have different integrations subscribed to different event types. For example, send all incidents to Slack but only resolved notifications to Discord.