Logistics & Supply Chain · Integration
Onfleet
Add Onfleet to your product for your customers, and give your AI agents governed access to it.
Onfleet manages last-mile delivery, so the model is tasks assigned to drivers within teams rather than shipments handed to a carrier. That difference matters: the customer owns the fleet, so assignment, routing and proof of delivery are all things your product can influence rather than merely observe. Tasks carry a recipient and a time window, and the interesting events are state changes as a driver starts, arrives and completes. Proof of delivery, signature or photo, is attached to the completion rather than stored separately. fastn scopes each customer's key so their drivers and tasks are only ever reachable by them.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Onfleet org so deliveries are dispatched from inside your product.
Create tasks with a recipient and time window rather than exporting a list to dispatch.
Assign to a driver or a team, which is the decision the customer's operation turns on.
React to started, arrived and completed events as a delivery progresses.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which deliveries are running late and which driver holds them.
An agent creates or reassigns a task within governed permissions, with the write audited.
An agent retrieves proof of delivery for a disputed drop.
Example prompt
Which deliveries are running behind their window, and who is assigned to them?
Set up Onfleet in 4 steps
- 01Enable the Onfleet connector from your fastn dashboard.
- 02Have each customer authorise their own Onfleet account, so calls run under their credentials rather than a shared key.
- 03Decide which shipments, tracking events and orders your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Onfleet integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Onfleet integration without building it. Your customers connect their own Onfleet account inside your product and work their shipments, tracking events and orders there, with no per-customer code on your side.
- Handle the part that actually costs time: tracking data arrives from many carriers in inconsistent formats and at unpredictable times. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Onfleet update is not your on-call problem.
- One integration serves your product and your agents. The same governed Onfleet connection powers in-product features and gives AI agents scoped, audited access, so you keep physical movement and stock visible inside your product without wiring it twice.
Used by these teams
Compare with
Shippo
FedExWorks well with
ShopifyOften used alongside
Tools the same teams tend to run next to Onfleet, across other categories.
NetSuite
Stripe
QuickBooks
BigCommerceOnfleet integration FAQ
How do I add an Onfleet integration to my product?
Enable the Onfleet connector in your fastn dashboard, then let each customer authenticate their own Onfleet account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Onfleet client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Onfleet account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Onfleet account and only ever sees their own shipments, tracking events and orders. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Onfleet integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which deliveries are running late and which driver holds them.
Who maintains the Onfleet integration?
fastn does. When Onfleet changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I track shipments from Onfleet inside my product?
Yes. Shipment and tracking events are read per customer and can trigger your workflows, so status changes surface in your product instead of your users checking a carrier site.
What does my product get back from Onfleet as things move?
Whatever Onfleet actually holds. Where it moves goods, that is shipment and tracking events, read per customer and delivered as they land. Where it holds stock, levels can be read on demand or kept in step through events, so your product is not deciding on a stale count. Where it carries orders and documents between trading partners, it is the acknowledgement, ship notice or status change that says what moved.
What can I build with the Onfleet integration?
A common starting point: let a customer connect their own Onfleet org so deliveries are dispatched from inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Onfleet integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Onfleet does not change your per-connector cost. You can start free with 3 connected accounts.
Add Onfleet to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.