--- title: "Smartcar Integration" description: "Connect AI agents to vehicles across 40+ car brands through Smartcar. Agents read odometer, GPS location, fuel, and battery telemetry, look up vehicle attributes, and send remote lock or unlock commands from a workflow." url: https://flowrunner.ai/integrations/smartcar date_modified: 2026-08-04T10:04:16-07:00 --- # Smartcar [Utilities & Personal](https://flowrunner.ai/integrations/category/utilities-personal) Connect AI agents to vehicles across 40+ car brands through Smartcar. Agents read odometer, GPS location, fuel, and battery telemetry, look up vehicle attributes, and send remote lock or unlock commands from a workflow. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 7 actions · OAuth · available [Smartcar website](https://smartcar.com/) · [Platform Documentation](https://smartcar.com/docs) · Capability data verified 2026-08-12 1. The fleet telemetry schedule fires each morning 2. List Vehicles enumerates the connected fleet 3. Get Odometer, Get Location, and Get Battery or Get Fuel run per vehicle to capture the day's snapshot 4. Readings are compared against thresholds: low charge, low fuel, service-due mileage 5. The fleet channel gets the snapshot with flagged vehicles on top 6. When a vehicle needs a remote unlock, for a locked-out driver or a handoff, the fleet manager confirms the request against the vehicle's current location before Lock or Unlock fires, because opening a car's doors remotely is a physical security decision 7. On confirmation, Lock or Unlock dispatches the command and the outcome logs ## What This Integration Enables Fleet telematics has historically meant per-brand apps, aftermarket hardware, or spreadsheets fed by drivers. Smartcar collapses that: one OAuth connection reads telemetry and sends commands across 40+ car brands through the vehicle's own built-in connectivity. This connector puts that surface in FlowRunner workflows, where vehicle data can finally meet the dispatch board, the maintenance schedule, and the delivery queue that give it meaning. - Track odometer, GPS location, fuel, and battery across a mixed-brand fleet - Monitor EV state of charge and remaining range to schedule charging and dispatch - Log periodic telemetry snapshots to spreadsheets and databases for reporting - Confirm make, model, and year before issuing reads or commands - Send remote lock and unlock commands as reviewed workflow steps The line between reading a vehicle and commanding one is the line FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline draws: telemetry flows freely, and the command that opens doors waits for a person. ### Without FlowRunner **Telemetry is a phone call**: Odometer readings and fuel levels come from asking drivers, whenever they answer **Charging is managed by anxiety**: EV state of charge is unknown until a vehicle cannot make its route **Lockouts mean driving a key over**: A driver locked out means an hour of someone else's day and a stalled route ### With FlowRunner **The fleet reports itself**: Odometer, GPS, fuel, and battery snapshots log on schedule across every brand in one API **Charging is scheduled from data**: State-of-charge thresholds trigger charging plans before range becomes a roadside problem **Remote unlock is minutes, with sign-off**: A confirmed request opens the vehicle from the workflow, logged and attributed ## Use Case Scenarios ### The fleet snapshot that replaces the Monday phone tree Each morning the agent walks List Vehicles, pulls Get Odometer, Get Location, and the appropriate energy reading per vehicle, and appends the snapshot to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Vehicles crossing service mileage or sitting below charge thresholds get flagged in the [Slack](https://flowrunner.ai/integrations/slack) digest. The fleet manager starts the week with a current picture instead of a collection of guesses. ### EV charging scheduled by state of charge Overnight, the agent reads Get Battery across the electric vehicles. Any unit below the threshold for tomorrow's routes triggers a charging assignment, and a vehicle whose range cannot cover its planned route gets swapped in the dispatch plan before the driver arrives. The failure mode this kills, discovering at 7am that the van has 40 kilometers of range, stops being a story anyone tells. ### Dispatch that knows where the vehicles actually are Before assigning a pickup, the agent pairs Get Location with the worker roster from [Onfleet](https://flowrunner.ai/integrations/onfleet) to match the nearest available vehicle to the job. After the route completes, a confirmed Lock or Unlock secures the vehicle, and the driver gets an SMS confirmation via [Twilio](https://flowrunner.ai/integrations/twilio). Assignment quality stops depending on what the dispatcher remembers about who parked where. ## Human-in-Loop Highlight Lock or Unlock sends a command to a physical vehicle's doors, and the unlock direction is the one that matters: a car opened remotely at the wrong moment is exposed cargo, an insurance question, or a safety incident, and no log entry undoes it. The command also cannot be verified the way a database write can; the API returns success, but the vehicle sits wherever it sits. So unlock requests carry context before they carry out: which vehicle, confirmed via Get Vehicle, its current position from Get Location, who requested the unlock and why. The fleet manager cross-checks that the requester is actually standing at the car and approves. Lock commands after completed routes run on a lighter standing approval, because the failure mode of an extra lock is an inconvenience, not an exposure. Telemetry reads never gate at all. The connector's autonomy is proportional to what each action can put at risk. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 7 actions ### Vehicles 2 - **List Vehicles** Returns the vehicle IDs the connected account and token can control, paginated by limit and offset. The enumeration step every fleet sweep starts from. - **Get Vehicle** Retrieves a vehicle's static attributes: make, model, and model year. The confirmation read before commands, so the right doors open. ### Telemetry 4 - **Get Odometer** Reads total traveled distance in kilometers or miles by unit system. The input behind maintenance schedules and utilization reporting. - **Get Location** Reads the vehicle's last known GPS position as latitude and longitude. The dispatch and verification read. - **Get Fuel** Reads a combustion or hybrid vehicle's tank status: remaining range, percentage, and fuel amount, in the selected unit system. - **Get Battery** Reads an EV or plug-in hybrid's high-voltage battery: estimated remaining range and state of charge percentage. The number charging plans are built on. ### Security 1 - **Lock or Unlock** Sends a lock or unlock command to the vehicle's doors, returning a success status. Requires the control\_security permission and a vehicle that supports remote control. The command this page's human gate exists for. ## Frequently Asked Questions ### What can FlowRunner do with Smartcar? FlowRunner agents can run List Vehicles, Get Vehicle, and Get Odometer in Smartcar, plus 4 more actions. ### Does connecting Smartcar to FlowRunner require OAuth? Yes. Smartcar connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Smartcar trigger a FlowRunner workflow automatically? Smartcar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Smartcar?** This integration exposes Smartcar to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/smartcar. Site index: https://flowrunner.ai/llms.txt