Motive Agents vs Node-RED

Motive Agents

Agents let Motive fleet admins turn safety, maintenance and idling events into alerts, training, work orders and in-cab calls from the Fleet Dashboard, on a platform with a 99.99 per cent dashboard SLA and audited security reports. No API, webhook or MCP tool covers Agents, so an outside agent can't create, run or read them.

Node-RED

Node-RED's Admin HTTP API covers flows, nodes and settings in 20 documented methods, with read and write permissions per resource and a revision check on deploys. It has no OpenAPI file, no pagination and no SDK, and a default install accepts API calls from anyone who can reach port 1880.

Motive Agents

1. Don't plan to call Motive Agents. They're built and run by people in the Motive Fleet Dashboard
2. For Motive fleet data, use Motive's Public API or its MCP server instead, with the customer's admin authorisation
3. Ask the fleet's Motive admin to set up or change an Agent, and describe the trigger, condition and action you need
4. Expect Agents to place real calls to drivers and mark vehicles out of service, so confirm with the fleet manager before suggesting one

Node-RED

1. Call GET /auth/login first. An empty object means no authentication is set and every Admin API call is open
2. Send Node-RED-API-Version: v2 and the last rev on POST /flows, and re-read the flows on a 409
3. Set Node-RED-Deployment-Type to nodes or flows to restart only what changed. The default full stops every node
4. Prefer GET /flow/:id and PUT /flow/:id for one tab. GET /flows returns every node in the runtime
5. Treat flows.write and nodes.write as code execution on the host. Function nodes run JavaScript and POST /nodes installs npm modules