Webhooks

Neverline can broadcast JSON payloads to external services when specific queue events occur.

Configuration

Manage webhooks in Settings → Integrations in the admin dashboard. Each webhook requires:

• URL — the endpoint to receive webhook payloads
• Events — which events to listen for

Events

Event	Description
session.created	Customer joins a queue
session.called	Staff calls a customer
session.completed	Service marked complete
session.no_show	Customer didn't show up
session.requeued	Customer sent back to queue
session.away	Customer entered away mode
session.away_expired	Away timer expired
session.late	Customer marked as running late
session.late_expired	Late grace period expired
session.jumped	Customer accepted a queue jump
chat.message_sent	New chat message in a thread

Payload

All webhooks send POST requests with JSON body:

{
  "event": "session.called",
  "timestamp": "2025-01-15T10:30:00Z",
  "data": {
    "sessionId": "uuid",
    "queueId": "uuid",
    "queueName": "General Services",
    "position": 3,
    "customerName": "John",
    "customerToken": "token"
  }
}

Retry Policy

Failed deliveries (non-2xx response) are retried up to 3 times with exponential backoff.

Security

Webhook payloads include an X-Neverline-Signature header for payload verification. The signature is an HMAC-SHA256 hash of the request body using your webhook secret.