Use the Onfleet CLI from KosmoKrator to call Onfleet tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Onfleet can be configured headlessly with `kosmokrator integrations:configure onfleet`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure onfleet --set api_key="$ONFLEET_API_KEY" --enable --read allow --write ask --jsonkosmokrator integrations:doctor onfleet --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API keyapi_key. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
api_key
ONFLEET_API_KEY
Secret secret
yes
API Key
url
ONFLEET_URL
URL url
no
API Base URL
Call Onfleet Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Onfleet.
onfleet.onfleet_list_tasks
Read read
List delivery tasks from Onfleet. Filter by state (0=unassigned, 1=assigned, 2=active, 3=completed), worker, team, or time range. Returns task details including destination, recipient, and completion status.
Parameters
state, worker, organization, team, completeBeforeAfter, completeBeforeBefore, from, to, lastUpdated, query
Get detailed information about a specific delivery task by its ID. Returns destination, recipient, worker assignment, completion details, and tracking info.
Create a new delivery task in Onfleet. Requires a destination address and recipient details. Optionally assign to a worker or team, set time windows, and add notes.
Update an existing delivery task in Onfleet. Only the fields you provide will be changed. You can update destination, assignment, notes, time windows, and more.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
onfleet.onfleet_list_tasks
List delivery tasks from Onfleet. Filter by state (0=unassigned, 1=assigned, 2=active, 3=completed), worker, team, or time range. Returns task details including destination, recipient, and completion status.
Task state filter: 0=unassigned, 1=assigned, 2=active, 3=completed.
worker
string
no
Filter tasks assigned to a specific worker ID.
organization
string
no
Filter tasks by organization ID.
team
string
no
Filter tasks by team ID.
completeBeforeAfter
string
no
ISO 8601 timestamp — list tasks completed after this time.
completeBeforeBefore
string
no
ISO 8601 timestamp — list tasks with completeBefore before this time.
from
string
no
ISO 8601 timestamp — list tasks created after this time.
to
string
no
ISO 8601 timestamp — list tasks created before this time.
lastUpdated
string
no
ISO 8601 timestamp — list tasks updated after this time.
query
string
no
Search query to filter tasks by recipient name, notes, or tracking URL.
onfleet.onfleet_get_task
Get detailed information about a specific delivery task by its ID. Returns destination, recipient, worker assignment, completion details, and tracking info.
Create a new delivery task in Onfleet. Requires a destination address and recipient details. Optionally assign to a worker or team, set time windows, and add notes.
Update an existing delivery task in Onfleet. Only the fields you provide will be changed. You can update destination, assignment, notes, time windows, and more.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.