Integrations
Zapier
Trigger Zaps from FleetDeck run results and run a saved sequence from any Zap.
Trigger a Zap from FleetDeck
- In Zapier, create a Zap with the trigger Webhooks by Zapier → Catch Hook and copy the hooks.zapier.com URL.
- In FleetDeck, add a Webhook alert with that URL and the events you want (see Webhook events).
- Press Send test in FleetDeck, then Test trigger in Zapier to load sample fields such as event, schedule name, device name, run status and run error.
- Add a Filter step, for example only continue if event is run.failed, then your action (email, sheet row, ticket).
Test the connection
Create a key in the agents dashboard for the phone. Give it devices:read to list sequences and devices:control to run them. Store the fd_ token in your tool’s secret or credential store, never in a step’s visible text.
Add a Webhooks by Zapier → Custom Request (GET) step to https://fleetdeck.co/api/v1/me with header Authorization set to Bearer fd_…. A 200 response lists the key’s scopes and device IDs. A 401 means the key is wrong, expired or revoked.
curl https://fleetdeck.co/api/v1/me --header "Authorization: Bearer $FLEETDECK_API_KEY"Run a saved sequence from a Zap
Find the sequence id once with GET /api/v1/devices/{deviceId}/sequences, or with fleetdeck sequences DEVICE.
- Action: Webhooks by Zapier → Custom Request.
- Method: POST. URL: https://fleetdeck.co/api/v1/devices/{deviceId}/sequence-runs
- Data: the JSON below. Map requestId from a unique trigger field.
- Headers: Authorization = Bearer fd_…, Content-Type = application/json.
{
"requestId": "zap-clx9delivery0001",
"sequenceId": "seq_123",
"library": false
}The response has status queued and a scheduleId. Read the outcome later from the run.* alert, by repeating the same request, or with GET /api/v1/devices/{deviceId}/touch-runs?scheduleId=…. The phone must be online and free: DEVICE_BUSY, DEVICE_OFFLINE and SCHEDULER_OFFLINE are 409/503 errors to retry later.
