MyCarTracks
LogisticsConnect AI agents to MyCarTracks, a vehicle GPS tracking and mileage logging service. Agents read vehicles, live positions, recorded trips, geofence alerts, and driver statistics so fleet mileage and location data feed reports and workflows automatically.
What This Integration Enables
MyCarTracks is a mileage ledger before it is a fleet console. The reason to connect it to an agent is not live dispatch, it is that the trips it records turn into money: reimbursement, tax deduction, cost allocation, customer billing. FlowRunner agents read vehicles and their last known positions, and pull recorded tracks with distance, duration, and start and end locations. They can drill into a track's raw trackpoints or its stops, summarize distance and driving time per vehicle or per driver over a date range, and review geofences and their enter and exit alerts. Summary results can be grouped daily, monthly, or as a single total, which means the aggregation a finance workflow needs is already computed on the platform rather than reassembled downstream.
Two details shape how workflows should be built. Trips carry a category of Personal or Business, so this connector handles records about named employees and their private travel, and a workflow that flattens that distinction has quietly changed what the data is. And Request Vehicle Position is asynchronous: it asks the device or app to report a fresh location, and the position arrives later, to be read with Get Vehicle Last Position. An agent that calls one and immediately reads the other will read a stale answer and believe it is current. Time filters throughout are Unix timestamps in milliseconds.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Monthly mileage reimbursement built from the tracking record
At month end the agent calls List Vehicles, then Get Driver Summary Stats for each driver over the period grouped monthly, and separates business from personal distance. It writes the result into Google Sheets or straight into the expense system, with the per-track detail from List Tracks kept alongside as backup. The finance owner reviews a summary rather than a raw export, and the number that gets paid traces back to specific recorded trips.
A live position feed for a small operation
On a schedule, the agent calls List Vehicle Last Positions and posts a compact fleet view into Slack or writes it into Airtable as a dashboard other systems can read. When a dispatcher needs a fresher fix on one vehicle, the agent calls Request Vehicle Position, waits, then reads Get Vehicle Last Position rather than assuming the request itself returned the answer.
Geofence activity reconciled against expected site visits
The agent pulls List Geofence Alerts for the week and compares enter and exit events against the customer sites a vehicle was scheduled to visit. Sites that were scheduled but never entered, and entries at sites nobody scheduled, are surfaced as a short list. Nobody reads a full alert log looking for the interesting rows, and the interesting rows still reach a person.
Human-in-Loop Highlight
The gate sits on Delete Track. Deleting a trip in MyCarTracks is permanent and cannot be undone, and the thing being deleted is not a log line, it is a row in the record that mileage reimbursement and tax deduction are computed from, attached to a named employee. An agent doing hygiene work will find candidates that look obviously wrong: a 0.3 kilometer track that never left the yard, a track with a start and end at the same address, a track whose speed profile reads like GPS drift under a bridge. Some of those are device noise. Some of them are a real short trip that a driver will expect to be paid for. The API cannot tell the difference and neither can the agent. So the agent builds the list and stops: "Six tracks for vehicle CZ 88-41 in July look like device artifacts. Longest is 1.1 km, 4 minutes, start and end within 60 meters. Deleting is permanent. Remove all, remove selected, or keep and mark reviewed?" The person who signs off on the mileage claim decides. The agent does the finding, which is the tedious part, and never does the erasing on its own.
Agent Capabilities
17 actionsVehicles
6- List Vehicles Lists the vehicles in the account. Used to resolve the fleet before any per-vehicle read.
- Get Vehicle Returns a single vehicle's details. Used when a workflow already knows which vehicle it is reporting on.
- List Vehicle Last Positions Returns the last known position for every vehicle. Used to build a live fleet view on a schedule.
- Get Vehicle Last Position Returns the last known position for one vehicle. Used after a fresh position request, or for a single vehicle status check.
- Request Vehicle Position Asks the device or app to report a fresh location. The position arrives asynchronously and is then read with Get Vehicle Last Position.
- Get Vehicle Summary Stats Returns distance and driving time for a vehicle over a date range, grouped daily, monthly, or as a total. Used for utilization and cost reporting.
Tracks
5- List Tracks Returns recorded trips over a period with distance, duration, and start and end locations. Used as the basis for mileage reporting and change detection.
- Get Track Returns a single trip in detail. Used when one trip needs to be inspected or exported.
- Get Trackpoints Returns the raw points that make up a trip's route. Used when the exact path matters, such as proving a route was driven.
- List Track Stops Returns the stops recorded within a trip. Used to separate driving time from time spent at customer sites.
- Delete Track Permanently removes a trip. The removal cannot be undone, so this operation is proposed to a person rather than executed on a rule.
Geofences
3- List Geofences Lists the saved zones in the account. Used to resolve site definitions before checking activity against them.
- Get Geofence Returns a single zone's definition. Used when a workflow needs the boundary detail for one site.
- List Geofence Alerts Returns enter and exit events for zones. Used to reconcile site visits against what was scheduled.
Drivers
3- List Drivers Lists the drivers in the account. Used to resolve people before per-driver reporting.
- Get Driver Last Position Returns a driver's last known position. Used when the question is about a person rather than a vehicle.
- Get Driver Summary Stats Returns distance and driving time for a driver over a date range. Used for reimbursement and per-person utilization reporting.
Frequently Asked Questions
What can FlowRunner do with MyCarTracks?
FlowRunner agents can run List Vehicles, Get Vehicle, and List Vehicle Last Positions in MyCarTracks, plus 14 more actions.
Does connecting MyCarTracks to FlowRunner require OAuth?
MyCarTracks uses a custom authentication method to connect to FlowRunner.
Can MyCarTracks trigger a FlowRunner workflow automatically?
MyCarTracks doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with MyCarTracks
$100 in credits. No card required. Connect in minutes.