Integrations
Integrations
Connect FleetDeck run results and saved sequences to Zapier, Make, n8n, chat apps, calendars and spreadsheets.
Two directions
Outgoing: FleetDeck posts scheduled-run results to a signed webhook, Slack, Discord or Telegram. Set this up once in Automations → Alerts; there is no polling.
Incoming: your automation tool calls the REST API with a scoped key to check the connection, list saved sequences, run one now, manage touch schedules or export run history.
Endpoints used by these guides
| Method and path | Scope | Use |
|---|---|---|
GET /api/v1/me | Any valid key | Connection test: account, key scopes, expiry and assigned device IDs. |
GET /api/v1/devices/{deviceId}/sequences | devices:read | Find the sequenceId to run. |
POST /api/v1/devices/{deviceId}/sequence-runs | devices:control | Run a saved sequence now (requestId required). |
GET|POST /api/v1/devices/{deviceId}/touch-schedules | devices:read / jobs:write + devices:control | List or create schedules. |
POST|DELETE /api/v1/devices/{deviceId}/touch-schedules/{scheduleId} | jobs:write | Pause, resume, move or delete a schedule. |
GET /api/v1/devices/{deviceId}/touch-runs?format=csv | devices:read | Run history as JSON or CSV. |
Every call sends Authorization: Bearer fd_…. Full request and response schemas are in the REST reference.
Run a saved sequence now
curl https://fleetdeck.co/api/v1/devices/$DEVICE_ID/sequence-runs \
--request POST \
--header "Authorization: Bearer $FLEETDECK_API_KEY" \
--header "Content-Type: application/json" \
--data '{"requestId":"run-inbox-001","sequenceId":"seq_123"}'Guides
- Webhook events and delivery: payload, headers, retries.
- Verify webhook signatures: Node and Python.
- Zapier, Make and n8n.
- Slack, Discord and Telegram alerts.
- Google and Apple Calendar subscription.
- CSV export of run history.
