Onfleet MCP integration for AI agents.
Connect AI agents to Onfleet through 7 structured actions, including get task, create task, delete task, and clone task. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Onfleet integration exposes
The Onfleet Agent App exposes 7 provider-backed actions for productivity and location work. Its current contract lets an authorized agent get one onfleet task by id, create a pickup or delivery task in onfleet, and delete an unstarted onfleet task. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Onfleet account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Onfleet capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_taskREADGet one Onfleet task by ID.
INPUTS: taskId
create_taskWRITECreate a pickup or delivery task in Onfleet.
INPUTS: destination / recipients / merchant / executor / completeAfter
delete_taskHIGH IMPACTDelete an unstarted Onfleet task.
INPUTS: taskId
clone_taskREVIEWClone an existing Onfleet task with optional metadata and field overrides.
INPUTS: taskId / options
complete_taskREVIEWForce complete an active Onfleet task as successful or failed.
INPUTS: taskId / completionDetails
list_tasksREADList Onfleet tasks in a time range with cursor pagination and task filters.
INPUTS: from / to / lastId / state / worker
update_taskWRITEUpdate supported fields on an Onfleet task.
INPUTS: taskId / notes / metadata / customFields / destination
INPUT CONTRACTS
Know what the action needs before it runs.
get_task
taskIdOPTIONAL- The Onfleet task identifier.
create_task
destinationREQUIRED- An existing destination ID or an inline destination object.
recipientsREQUIRED- Zero or one recipients for the task.
merchantOPTIONAL- The organization ID displayed to the recipient.
executorOPTIONAL- The organization ID responsible for fulfilling the task.
completeAfterOPTIONAL- The earliest completion time in Unix milliseconds.
delete_task
taskIdOPTIONAL- The Onfleet task identifier.
clone_task
taskIdREQUIRED- The Onfleet task identifier.
optionsOPTIONAL- Options controlling which task data is copied and overridden.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Task
Get one Onfleet task by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_taskControl Create Task
Create a pickup or delivery task in Onfleet. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_taskVerify with List Tasks
List Onfleet tasks in a time range with cursor pagination and task filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_tasksSAFETY BOUNDARY
Operate Onfleet with explicit limits
- Authorize Onfleet with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_task` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Onfleet rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Onfleet task completed successfully.
CONNECTION MODEL
API key
Onfleet API key used as the Basic Auth username. Create or manage it in Configuration > API & Webhook: https://docs.onfleet.com/reference/scope-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Onfleet.