Automation library · Setup and learning

Onfleet tool MCP server all 37 operations

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 38 steps: large, and worth reading before you trust it with anything live.

Large

38 stepsLarge: read it before trusting it with anything live
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Service 37

The steps in the order they run, from what starts it.

  1. 1Create an adminOnfleet ToolService
  2. 2Delete an adminOnfleet ToolService
  3. 3Get many adminsOnfleet ToolService
  4. 4Update an adminOnfleet ToolService
  5. 5Add tasksOnfleet ToolService
  6. 6Get a containerOnfleet ToolService
  7. 7Update tasksOnfleet ToolService
  8. 8Create a destinationOnfleet ToolService
  9. 9Get a destinationOnfleet ToolService
  10. 10Create a hubOnfleet ToolService
  11. 11Get many hubsOnfleet ToolService
  12. 12Update a hubOnfleet ToolService
  13. 13Get my organizationOnfleet ToolService
  14. 14Get a delegatee's detailsOnfleet ToolService
  15. 15Create a recipientOnfleet ToolService
  16. 16Get a recipientOnfleet ToolService
  17. 17Update a recipientOnfleet ToolService
  18. 18Clone a taskOnfleet ToolService
  19. 19Complete a taskOnfleet ToolService
  20. 20Create a taskOnfleet ToolService
  21. 21Delete a taskOnfleet ToolService
  22. 22Get a taskOnfleet ToolService
  23. 23Get many tasksOnfleet ToolService
  24. 24Update a taskOnfleet ToolService
  25. 25Auto-dispatch a teamOnfleet ToolService
  26. 26Create a teamOnfleet ToolService
  27. 27Delete a teamOnfleet ToolService
  28. 28Get a teamOnfleet ToolService
  29. 29Get many teamsOnfleet ToolService
  30. 30Get time estimates for a teamOnfleet ToolService
  31. 31Update a teamOnfleet ToolService
  32. 32Create a workerOnfleet ToolService
  33. 33Delete a workerOnfleet ToolService
  34. 34Get a workerOnfleet ToolService
  35. 35Get many workersOnfleet ToolService
  36. 36Get the schedule for a workerOnfleet ToolService
  37. 37Update a workerOnfleet ToolService
  38. 38Onfleet Tool MCP ServerMcp triggerStarts it

How it's built

Starts on
An event in a connected app
Steps
38
Size
Large: read it before trusting it with anything live
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 38 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 38 steps before you point it at anything that matters.