Reference · Credentials
Onfleet API credentials
Used by 2 BusyBot nodes.
Type
onfleetApi 1 field The Onfleet credential holds an API key created in your Onfleet dashboard, used by the Onfleet node and its trigger to manage tasks, workers, destinations and recipients.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | Your Onfleet API key. |
Getting your credentials
- Sign in to the Onfleet dashboard as an administrator.
- Open the settings area covering API keys and create a new key, naming it for this integration.
- Copy the key and paste it into the credential’s API Key field in BusyBot.
Permissions and scopes
The key acts on the Onfleet organization that issued it. Creating a dedicated key per integration means you can revoke this one without disturbing anything else.
Troubleshooting
- 401 Unauthorized — the key is wrong or was revoked in the dashboard.
- Task or worker not found — the ID belongs to a different organization, or the object was deleted.
- Validation errors on task creation — destination and recipient details must be complete; Onfleet rejects partial addresses.
Frequently asked questions
Who can create an Onfleet API key?
An administrator of the Onfleet organization, from the dashboard's API settings.
Should I reuse one key everywhere?
Better to create a key per integration, so this one can be revoked without disturbing your other tools.
Does one key cover the node and the trigger?
Yes, both declare the same credential type.
Nodes that use Onfleet API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.