FleetDeckDocs

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 pathScopeUse
GET /api/v1/meAny valid keyConnection test: account, key scopes, expiry and assigned device IDs.
GET /api/v1/devices/{deviceId}/sequencesdevices:readFind the sequenceId to run.
POST /api/v1/devices/{deviceId}/sequence-runsdevices:controlRun a saved sequence now (requestId required).
GET|POST /api/v1/devices/{deviceId}/touch-schedulesdevices:read / jobs:write + devices:controlList or create schedules.
POST|DELETE /api/v1/devices/{deviceId}/touch-schedules/{scheduleId}jobs:writePause, resume, move or delete a schedule.
GET /api/v1/devices/{deviceId}/touch-runs?format=csvdevices:readRun 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