Onfleet
Run last-mile delivery through Onfleet: create, list, read, update and delete tasks with their destinations and recipients, and read the workers, teams and hubs those tasks are assigned to.
OCNORA ships 8 typed Onfleet operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Onfleet
- Authentication
- API key
- Credential
- {"api_key": "…", "webhook_secret": "<hex from the dashboard>"}the API key, or {"api_key": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- Two credentials, and the second is not optional here: the API key registers the webhook, and the organisation's webhook secret (Configuration → API & Webhook → Show Secret, a hexadecimal string) is what every delivery is verified against. No Onfleet API call returns that secret, so it has to be stored on the connection.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Onfleet
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 1
Read and search 5
Update 1
Delete and cancel 1
A sample Onfleet workflow
- 1Eventtrigger.onfleet_eventStart a run when Onfleet fires a webhook trigger (task, worker, route plan).
- 2Get Taskonfleet.get_taskRead one task, with its destination, recipient and completion detail.
- 3Create Taskonfleet.create_taskCreate a delivery or pickup task, with its destination and recipient.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Create TaskCreate a delivery or pickup task, with its destination and recipient.onfleet.create_task
- Delete TaskDelete a task that has not yet started or been completed.onfleet.delete_task
- Get TaskRead one task, with its destination, recipient and completion detail.onfleet.get_task
- List HubsList every hub, with its address and the teams that use it.onfleet.list_hubs
- List TasksRead one page of the organisation's tasks from a starting time.onfleet.list_tasks
- List TeamsList every team, with its workers, managers and hub.onfleet.list_teams
- List WorkersList the organisation's drivers, optionally filtered by team or state.onfleet.list_workers
- Update TaskChange named fields on an existing task, leaving the rest alone.onfleet.update_task
Onfleet questions
- How does OCNORA authenticate with Onfleet?
- With a stored API key credential, shaped {"api_key": "…", "webhook_secret": "<hex from the dashboard>"} or the API key, or {"api_key": "…"}. A connection test can check it when you add it.
- What can I automate with Onfleet?
- 8 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Onfleet operation I need is not listed?
- Where Onfleet has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Onfleet?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Onfleet calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Onfleet workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.