FleetDeckDocs

Integrations

Webhook events and delivery

What FleetDeck sends to a generic webhook, how it signs each request, and how retries and auto-disable work.

Create a webhook

  1. Open Automations → Alerts as a workspace owner and choose Add alert.
  2. Pick Destination: Webhook (Zapier, Make, n8n…), paste the https URL from your tool and tick the events to send.
  3. Save, then copy the whsec_ signing secret. It is shown once; to rotate it, delete the alert and add it again.
  4. Press Send test. Your tool receives a webhook.test event you can use to map fields.

Each workspace can have up to 10 alerts. Only owners can add, test or delete them.

Events

EventWhen it is sent
run.succeededA scheduled run or a sequence run started through the API completed.
run.failedA run failed, or its worker lease expired (run.status is interrupted).
run.skippedA run could not start: device offline or busy, missed occurrence, model mismatch and similar.
webhook.testYou pressed Send test. schedule, device and run are null.

Runs you cancel yourself send nothing.

Payload

FleetDeck sends POST with a JSON body. id is the delivery id.

run.failed
{
  "id": "clx9delivery0001",
  "event": "run.failed",
  "occurredAt": "2026-10-29T12:00:05.000Z",
  "schedule": { "id": "schedule_123", "name": "Morning routine" },
  "device": { "id": "device_123", "name": "iPhone 15" },
  "run": {
    "id": "run_123",
    "status": "failed",
    "scheduledAt": "2026-10-29T12:00:00.000Z",
    "startedAt": "2026-10-29T12:00:01.000Z",
    "finishedAt": "2026-10-29T12:00:05.000Z",
    "error": "Device is offline"
  }
}

Headers

HeaderValue
Content-Typeapplication/json
User-AgentFleetDeck-Webhooks/1
X-FleetDeck-EventThe event name, for example run.failed
X-FleetDeck-DeliveryUnique per delivery and identical across retries; equals the body id. Use it to drop duplicates.
X-FleetDeck-Signaturet=<unix seconds>,v1=<hex HMAC-SHA256(secret, "<t>.<raw body>")>

Slack, Discord and Telegram destinations receive their own message format and no X-FleetDeck headers.

Delivery and retries

  • Alerts are queued with the run result and usually sent within a minute.
  • Return a 2xx within 10 seconds. The response body is ignored. Redirects are not followed; a 3xx is a failure.
  • Network errors, timeouts, 408, 425, 429 and 5xx are retried with backoff (30 s, 1 min, 2 min …) up to 8 attempts. Other 4xx fail at once.
  • After 3 deliveries in a row fail completely, the alert is turned off and its queued deliveries are discarded. The Alerts tab shows why; turn it back on after fixing the receiver.
  • Targets must be https on port 443 and resolve to public IP addresses. Private, loopback, link-local, CGNAT and metadata ranges are refused on save and on every send.