All integrationsDevice Management
Motive
Work with your Motive fleet: vehicles and where they are, drivers and their hours of service, inspection reports, fault codes, harsh driving, fuel purchases, geofences and messages to drivers.
- actions
- 25
- triggers
- 11
Triggers
Start a workflow when something happens in Motive.
- New HOS violationRuns for each hours-of-service violation a driver gets, such as going over the 11-hour driving limit. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New inspection reportRuns for each vehicle inspection report (DVIR) a driver submits, with any defects found. Choose With defects to hear only about problems. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New fault codeRuns for each engine fault code a vehicle reports, with what it means. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New harsh driving eventRuns for each hard braking, acceleration or cornering event, with where it happened and how sharp it was. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New speeding eventRuns for each time a vehicle goes over the posted speed limit, with by how much and for how long. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New geofence visitRuns for each visit a vehicle makes to a geofence, such as arriving at a customer or the yard, once Motive records it. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New fuel purchaseRuns for each fuel purchase recorded in Motive, by a driver, a fuel card or a workflow. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New message from a driverRuns for each message a driver sends from the Motive Driver app. Ones from before the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New userRuns for each driver, fleet user or admin added to Motive. Users already there when the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- New vehicleRuns for each vehicle added to Motive. Vehicles already there when the workflow is turned on don't start it. It checks every minute or less often, as your workspace plan allows.
- Driver duty status changedRuns when a driver's duty status changes, such as going on duty or starting to drive. Choose a status to hear only when drivers enter it. It checks every minute or less often, as your workspace plan allows.
Actions
Steps a workflow can run in Motive.
- Get companyGet the Motive company the API key belongs to: name, address, USDOT numbers, default hours-of-service cycle and time zone.
- List usersList drivers, fleet users and admins, by role, status, duty status or name. Gets one page; to see more, run it again with the next page number.
- Get userGet one driver or user with their role, status, duty status, hours-of-service cycle and licence.
- Update userChange a driver's or user's name, email, phone or driver ID, or deactivate or reactivate them. Only the fields given change.
- List vehiclesList the fleet's vehicles with their number, VIN, plate, gateway, current driver and whether they're in service. Gets one page; to see more, run it again with the next page number.
- Get vehicleGet one vehicle with its number, VIN, plate, gateway, drivers and whether it's in service.
- Update vehicleChange a vehicle's plate, VIN, make, model, year, notes or permanent driver, take it in or out of service, or deactivate it. Only the fields given change.
- Get vehicle locationsGet where vehicles are now: position, place name, speed, heading, odometer, fuel and driver, for chosen vehicles or the whole fleet.
- Get vehicle location historyGet every point a vehicle reported on one day: where it was, when, its speed, odometer and driver.
- List assetsList trailers and other assets with their type, VIN, plate and tracking gateway. Gets one page; to see more, run it again with the next page number.
- List groupsList the company's groups (such as regions or terminals) with the group each sits under.
- Get drivers' available hoursGet how much driving, shift, cycle and break time drivers have left under hours-of-service rules, in seconds, with their duty status.
- List driver logsList drivers' daily hours-of-service logs: time driving, on duty, off duty and in the sleeper, miles, vehicles and whether they're certified.
- List HOS violationsList hours-of-service violations, such as going over the 11-hour driving limit, with the driver and when each started and ended.
- List inspection reportsList drivers' vehicle inspection reports (DVIRs) with their defects and signatures, filtered by driver, vehicle, status or date.
- List fault codesList engine fault codes vehicles reported, with what each means, whether it's still open and when it was seen.
- List harsh driving eventsList hard braking, acceleration and cornering events, with the driver, vehicle, place, speeds and coaching status.
- List fuel purchasesList fuel purchases with the amount, cost, vendor, state or province, vehicle and driver, for IFTA and fuel reports.
- Record fuel purchaseRecord a fuel purchase for a vehicle and driver, such as one from a fuel card statement, so it counts in IFTA reports.
- Delete fuel purchaseDelete a fuel purchase, such as one recorded twice.
- List geofencesList the company's geofences (yards, job sites, customers and so on) with their category, address and shape.
- Create geofenceCreate a round geofence: a centre and a radius, such as a customer site, so Motive tracks when vehicles come and go.
- Delete geofenceDelete a geofence so Motive stops tracking visits to it.
- Send message to driverSend a message to a driver (or other user), shown in the Motive Driver app.
- List messagesList messages between the office and drivers, with who sent each, who it went to and whether it was read.
No actions match that.
Automate Motive with Lodol.
Connect Motive, then hand Lodol the job in Slack, Claude or ChatGPT.
We’re letting people in a few at a time.