Overview
Integrations and webhooks allow your applications to receive real-time notifications about events in your Scalelite cluster. When servers go offline, meetings start, or alerts trigger, Scalelite sends HTTP POST requests to your configured endpoints.
- Real-time HTTP event notifications
- HMAC signature verification for security
- Automatic retries with exponential backoff
- Detailed delivery logs and success tracking
Webhooks Dashboard
Access webhooks from the sidebar under Settings → Integrations. View all configured webhooks, their delivery success rates, and manage endpoints.
🔌 Your Webhooks
| Name | URL | Events | Success Rate | Status | Actions |
|---|---|---|---|---|---|
| Slack Alerts | https://hooks.slack.com/services/... |
alerts | 98% (245/250) | Active | |
| Analytics Webhook | https://api.myapp.com/webhook |
meetings, recordings | 100% (89/89) | Active |
Event Types
1Server Events
Triggered when server status changes:
server.online- Server came onlineserver.offline- Server went offlineserver.health_changed- Health status changed
2Meeting Events
Triggered during meeting lifecycle:
meeting.created- New meeting startedmeeting.ended- Meeting endedmeeting.recording_started- Recording beganmeeting.recording_ended- Recording finished
3Alert Events
Triggered when alerts fire:
alert.created- New alert triggeredalert.resolved- Alert was resolvedalert.escalated- Alert escalated to next level
Creating a Webhook
- Click Create Webhook button
- Configure settings:
- Name: Descriptive name (e.g., "Slack Alerts")
- URL: Your HTTP endpoint URL
- Events: Select event types to receive
- Secret: Optional HMAC signing secret
- Click Save to create the webhook
- Use Test button to send a test payload
Webhook Payload Format
All webhooks receive JSON payloads with this structure:
Security: HMAC Signatures
Verify webhook authenticity using HMAC-SHA256 signatures sent in the X-Webhook-Signature header:
Retry Behavior
Failed webhook deliveries are automatically retried with exponential backoff:
- Attempt 1: Immediate
- Attempt 2: After 1 minute
- Attempt 3: After 5 minutes
- Attempt 4: After 30 minutes
- Attempt 5: After 2 hours (final)
Deliveries are considered failed when:
- HTTP status code is not 2xx
- Connection timeout (30 seconds)
- SSL/TLS errors
Popular Integrations
Slack
Send alerts to Slack channels using incoming webhooks:
- Create Slack incoming webhook at
api.slack.com - Add webhook URL to Scalelite
- Select "alerts" event type
Microsoft Teams
Configure Teams connector for notifications:
- Add "Incoming Webhook" connector to your Teams channel
- Copy the webhook URL
- Create webhook in Scalelite with that URL
PagerDuty
Route alerts through PagerDuty for on-call management:
- Create PagerDuty service integration
- Use Events API v2 endpoint
- Configure alert event routing