Ir al contenido
Back to Integrations & Webhooks
Integrations & Webhooks

Integrations & Webhooks Overview

Connect with external systems

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.

Key Features:
  • 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 online
  • server.offline - Server went offline
  • server.health_changed - Health status changed

2Meeting Events

Triggered during meeting lifecycle:

  • meeting.created - New meeting started
  • meeting.ended - Meeting ended
  • meeting.recording_started - Recording began
  • meeting.recording_ended - Recording finished

3Alert Events

Triggered when alerts fire:

  • alert.created - New alert triggered
  • alert.resolved - Alert was resolved
  • alert.escalated - Alert escalated to next level

Creating a Webhook

  1. Click Create Webhook button
  2. 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
  3. Click Save to create the webhook
  4. Use Test button to send a test payload

Webhook Payload Format

All webhooks receive JSON payloads with this structure:

{ "event": "alert.created", "timestamp": "2024-12-04T10:30:00Z", "instance_id": 1, "data": { "alert_id": 456, "severity": "critical", "message": "CPU usage exceeded 90%", "server_id": 123 } }

Security: HMAC Signatures

Verify webhook authenticity using HMAC-SHA256 signatures sent in the X-Webhook-Signature header:

# Python example import hmac import hashlib def verify_signature(payload, signature, secret): expected = hmac.new( secret.encode(), payload.encode(), hashlib.sha256 ).hexdigest() return hmac.compare_digest(f"sha256={expected}", signature)
⚠️ Security Tip: Always verify webhook signatures in production to ensure requests are from Scalelite Manager.

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:

  1. Create Slack incoming webhook at api.slack.com
  2. Add webhook URL to Scalelite
  3. Select "alerts" event type

Microsoft Teams

Configure Teams connector for notifications:

  1. Add "Incoming Webhook" connector to your Teams channel
  2. Copy the webhook URL
  3. Create webhook in Scalelite with that URL

PagerDuty

Route alerts through PagerDuty for on-call management:

  1. Create PagerDuty service integration
  2. Use Events API v2 endpoint
  3. Configure alert event routing

Related Articles

Was this article helpful?

¿Aún necesitas ayuda? Contactar con soporte

Buscando...
Buscar en reuniones, grabaciones y participantes
Presione ESC para cerrar