# Onfleet integrations: tasks and orders

> Create a task, create an order and create a route plan in Onfleet, and start a workflow when Onfleet sends “Task started”.

**Canonical page:** https://tray.ai/connectors/onfleet-integrations/
**Categories:** Supply chain
**Connects through:** HTTP Connector

## Overview

Onfleet is last-mile delivery management software for dispatching drivers, planning routes, tracking deliveries, and notifying recipients. Tray.ai connects to Onfleet through the HTTP Connector, so your workflows can call the Onfleet API alongside the rest of your stack.

## Use cases

### Tasks

Read and create tasks in Onfleet from any Tray.ai workflow. The Onfleet API covers calls such as create a task and list tasks.

- Create a task
- List tasks
- Get a task

### Orders

Read, create, update, and delete orders in Onfleet from any Tray.ai workflow. The Onfleet API covers calls such as create an order and get orders.

- Create an order
- Get orders
- Update an order

### Route plans

Read, create, update, and delete route plans in Onfleet from any Tray.ai workflow. The Onfleet API covers calls such as create a route plan and get a route plan.

- Create a route plan
- Get a route plan
- Update a route plan

### Webhooks

Update webhooks in Onfleet from any Tray.ai workflow. The Onfleet API covers calls such as update a webhook and manage webhook secrets.

- Update a webhook
- Manage webhook secrets

### Onfleet events

Start a Tray.ai workflow the moment something happens in Onfleet. Onfleet sends events such as task started and task ETA to a Tray.ai webhook trigger.

- Task started
- Task ETA
- Task arrival

## Challenges Tray.ai solves

### Keeping Onfleet credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Onfleet credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Onfleet API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Onfleet API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Onfleet?

Yes. Tray.ai connects to Onfleet through the HTTP Connector, which calls the Onfleet API directly. Any call the Onfleet API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Onfleet?

The Onfleet API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Onfleet connector?

Onfleet runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Onfleet connector from the Onfleet API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/