FleetDeckDocs

Integrations

CSV export of run history

Download touch-schedule and sequence run history for spreadsheets and reports.

Download with curl

Use a key with devices:read for the phone and add format=csv to the run history endpoint.

Failed runs as CSV
curl "https://fleetdeck.co/api/v1/devices/$DEVICE_ID/touch-runs?format=csv&status=failed" \
  --header "Authorization: Bearer $FLEETDECK_API_KEY" \
  --output fleetdeck-runs.csv --dump-header -

Optional filters: scheduleId, status (running, completed, failed, cancelled, skipped, interrupted) and cursor to start from a previous JSON page’s nextCursor.

File format

The response is text/csv; charset=utf-8, newest run first, with the columns:

text
id,scheduleId,scheduleName,status,scheduledAt,startedAt,finishedAt,durationMs,error
  • Up to 5,000 rows. Response header X-FleetDeck-Rows has the row count and X-FleetDeck-Truncated is true when older rows exist.
  • Times are ISO 8601 UTC. durationMs is empty for runs that did not start or finish.
  • Cells that begin with =, +, -, @, tab or carriage return get a leading apostrophe so spreadsheets do not run them as formulas.

From the CLI

CLI
fleetdeck runs DEVICE_ID --csv > fleetdeck-runs.csv

The CLI pages through the JSON endpoint and writes the same columns; scheduleName stays empty there. See fleetdeck runs.

Scheduled exports

Spreadsheet import functions such as Google Sheets IMPORTDATA cannot send an Authorization header, and a key must never go in a URL. Fetch the CSV from Zapier, Make, n8n or a cron job with the header, then write the rows to your sheet.

For live updates instead of exports, send run results to a webhook and append one row per event.