Astara Connect

Connect AI agents to Astara Connect, the connected-vehicle telematics platform from mobility group Astara. Agents track vehicles and trackers, create and delete points of interest, read telemetry, and set tracking schedules per fleet.

31 actions API key available

Platform Documentation ↗

A fleet policy change asks for tracking hours to be narrowed to the working week

Agent reads the current timetable with List Tracking Schedules and the fleet with List Company Trackers

Agent confirms the target timezone identifier against List Timezones before building the timetable

Agent replays recent activity from List Trips against the proposed hours to find trips that fall outside them

Agent stages the replacement timetable and its exception dates without applying anything

Fleet operations receives the staged timetable alongside the trips it would have stopped recording

Fleet operations approves before Delete Tracking Schedule and Create Tracking Schedule run, because the interval between them records nothing

What This Integration Enables

Astara Connect is the connected-vehicle platform from Astara, the Madrid-based mobility group, and it is built around the tracker rather than the vehicle. A tracker is an OEM, OBD, CANbus, or IoT device with an identity (make, model, VIN, license plate), a provider, a validation status, a last known position, and a heartbeat. That distinction matters when you automate against it, because a vehicle can exist in your fleet system while its tracker sits at wrong_tracker_id and quietly reports nothing. Agents register trackers, correct their identifiers, organize them into groups, and delete or disconnect them. They read trips for a company or a group over a date range, pull the dates on which a tracker moved at all, and aggregate distance and driving time per tracker. They create and delete Points of Interest and query public ones by proximity, and they define the tracking schedules that control the hours during which tracker information is stored at all.

Three things are worth being direct about. Astara Connect exposes no geofence object through this connector, and there is no geofencing action here. Points of Interest are single Point locations with a name, coordinates, and optional tags, created with Create POI and removed with Delete POI, and there is no update operation for them. Second, this connector has no triggers, so FlowRunner receives no events from Astara Connect. Groups do carry a webhook URL that Register Group and Update Group can set, and that field points Astara Connect at an endpoint of your choosing; it does not create a FlowRunner trigger and nothing is delivered into a flow as a result. Flows here start from a schedule, from a dispatch system, or from a fleet record changing somewhere else, and read Astara Connect when they get there. Third, on top of the fleet surface sit Astara Play services: license-plate vehicle lookups, fuel station detail with current prices per liter, and nearby electric-vehicle charge points from Open Charge Map. Those are what turn a tracker roster into something an operations agent can actually reason about.

Without FlowRunner

Tracker onboarding is a form-filling job Each vehicle is registered by hand and its validation status is checked days later, if at all

Trackers stuck at wrong_tracker_id go unnoticed A mistyped VIN or IMEI looks like a working tracker on the roster and reports nothing

Emissions reporting is a quarterly spreadsheet exercise Distance and WLTP figures are pulled and combined manually when the report is due

With FlowRunner

Registration and verification run as one pass Register Tracker writes the vehicle and the agent watches its validation status move off pending on the next sweep

Bad tracker IDs surface as a work queue List Company Trackers filtered on validation status turns the unverified set into a list someone can act on

Emissions computed from the trips themselves Calculate CO2 Emissions derives per-trip grams from each vehicle's WLTP value and aggregates them by day

Use Case Scenarios

Fleet Onboarding and Validation Sweep

New vehicles arrive and each needs a tracker on the roster. The agent calls Register Tracker with the company OID, the tracker ID, the provider, and the connection type, then assigns it to the right fleet group with Add Trackers To Group. Newly registered trackers start at pending or wrong_tracker_id, so a later sweep runs List Company Trackers filtered on validation status and reads Get Tracker for each one that has not moved. Where the identifier looks transposed, the agent cross-checks the plate with Get Vehicle Info By Plate and the make against List Vehicle Makes And Models, then corrects it with Update Tracker, which restarts provider verification. Anything still unverified after the pass goes to fleet operations in Slack as a named list rather than a count.

Sustainability Reporting from Real Trips

A sustainability report needs per-vehicle emissions rather than an estimate from fuel receipts. On a schedule, the agent lists the fleet with List Company Trackers, calls Calculate CO2 Emissions across those trackers for the reporting window, and pairs it with Get Tracker Trip Stats for total kilometers and moving time. Robust Output means a vehicle with missing catalog data returns a per-tracker error code instead of failing the whole run, so the agent can separate the vehicles it computed from the vehicles it could not and report both honestly. The result appends to a tracking sheet in Google Sheets with the incomplete trackers named alongside the totals.

Changing What the Fleet Records

Operations wants tracking narrowed to the working week, so drivers are not recorded on personal time. This is not a reporting change, it is a change to what data exists. The agent reads the current timetable with List Tracking Schedules, validates the timezone identifier against List Timezones, and replays List Trips over the last month against the proposed hours to show which real trips would have gone unrecorded. There is no update operation for a schedule, so applying the change means Delete Tracking Schedule followed by Create Tracking Schedule, and the fleet records nothing in between. The agent stages all of it and hands the decision to a person.

Human-in-Loop Highlight

The gate is the tracking schedule, and it is there because a schedule is not a filter on the data, it is the definition of which data exists. Astara Connect's schedules "define the timetable during which tracker information is stored", so hours outside the timetable are not hidden, they are never captured, and no later query brings them back. The connector also gives you no way to edit one: the action list is List Tracking Schedules, Create Tracking Schedule, and Delete Tracking Schedule, with no update. Changing a timetable therefore means destroying the old one and building a new one, and whatever the fleet does between those two calls is gone. So the agent does the work and stops short of the switch. It posts the staged timetable to fleet operations with the evidence attached: "New Mon to Fri 07:00 to 19:00 Europe/Madrid timetable is ready for 214 trackers. Replaying last month, 63 trips totalling 1,180 km fall outside these hours and would not have been recorded. Applying this means Delete Tracking Schedule then Create Tracking Schedule, and nothing is stored between the two calls. Apply, adjust the hours, or add exception dates?" Registration, verification, correction, and reporting all run without anyone watching. The decision about what the fleet stops remembering belongs to a person who can be asked why.

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

31 actions

Trackers

List Trackers Returns the trackers that belong to a company. Filter to a single group with Group OID, and narrow by validation status. Each tracker includes its OID, tracker ID, provider, object identity (make, model, VIN, license plate), last position, and heartbeat.
Get Tracker Retrieves the full detail of a single tracker by its OID, including tracker ID, object identity, provider, type, vehicle type, validation status, last known position, heartbeat, and per-property readings.
Register Tracker Registers a new tracker in a company. Requires the company OID, a tracker ID (VIN, IMEI, license plate, or provider identifier), the data provider, and the connection type. Optionally assign it to a group, set the vehicle type, and provide object identity fields (make, model, VIN, license plate). Newly registered trackers start with a pending or wrong_tracker_id validation status.
Update Tracker Updates the object identity, tracker ID, vehicle type, or connection type of an existing tracker. At least one attribute must be provided. Correcting the tracker ID restarts provider verification, moving a wrong_tracker_id status back to pending.
Delete Tracker Deletes or disconnects a tracker by its OID. Trackers with no historical data are removed entirely, while connected trackers are set to disconnected and keep their historical data accessible to the owner.

Groups

List Groups Returns the list of groups the authenticated account belongs to. Each group includes its OID, name, slug, description, webhook, email, and the parent company. Returns an empty list when the account belongs to no groups.
Register Group Registers a new group in a company. Groups organize trackers in a custom way (for example a "sales" group). Requires the company OID, a name, and a unique slug (alphanumeric, no spaces or special characters). Optionally set a webhook URL and a notification email. The webhook URL points Astara Connect at an endpoint of your choosing and does not create a FlowRunner trigger.
Update Group Updates one or more properties of an existing group by its OID. Updatable fields are name, slug, company OID, webhook, and notification email.
Delete Group Removes a group from the system by its OID. The trackers that belonged to the group are not deleted, only their group association is removed.
Add Trackers To Group Assigns one or more existing trackers to a group by their OIDs. Use this to organize trackers, for example grouping all vehicles used by a specific team.
Remove Trackers From Group Removes one or more trackers from a group by their OIDs. The trackers themselves remain registered in the company.
List Group Trackers Returns the trackers that belong to a specific group, identified by the group OID.

Points of Interest

List POIs Returns the Points of Interest (POIs) associated with a company or a group. Provide either the company OID or the group OID to scope the results.
Get Public POIs Returns public POIs. With no filters it returns all available public POIs. Filter by proximity using latitude, longitude, and an optional radius in meters (defaults to 30), and by tags or an info object.
Create POI Creates a Point of Interest from a single Point location. Provide a name and the latitude and longitude, and optionally tags, an info object, and whether the POI is public. Assign to a specific company with the optional company OID.
Delete POI Deletes a Point of Interest by its OID.

Telemetrics

List Trips Returns the trips belonging to a company or a group. Provide either the company OID or the group OID. Filter by a date range (start date and end date in YYYY-MM-DD) and by a single tracker ID. Results are paginated 10 at a time using the next and previous cursors returned by a prior call. With no dates, only today's trips are returned.
Get Tracker Trip Dates Returns the list of dates on which a given tracker recorded at least one trip. Useful for building a calendar view of tracker activity.
Get Tracker Trip Stats Returns aggregated trip statistics for a tracker from its creation to its last heartbeat: total kilometers (kms) and total moving time in seconds (time). Filter by a date range using start date and end date in YYYY-MM-DD.

Tracking Schedules

List Tracking Schedules Returns tracking schedules. Provide a company OID to list all of a company schedules, or a schedule OID to fetch one specific schedule. Schedules define the timetable during which tracker information is stored.
Create Tracking Schedule Registers a new tracking schedule for a company. Requires a name, a timezone, and a schedule object with a weekly timetable and optional exceptions. The timetable maps weekday keys (Mon, Tue, Wed, Thu, Fri, Sat, Sun) to arrays of hour ranges, for example {"Mon":[["8:00","10:00"]]}.
Delete Tracking Schedule Removes a tracking schedule by its OID.
List Timezones Returns the list of timezone identifiers supported for tracking schedules, for example UTC, Europe/Madrid, and America/New_York.

Companies

List Company Trackers Returns the trackers belonging to a company with rich filtering and sorting. Filter by validation status, whether the tracker is active, or a single tracker ID. Order by start date, end date, or tracker ID, ascending or descending. Set Return All to disable pagination, or page through results with the next and previous cursors.
List Company Groups Returns the groups that belong to a company, identified by the company OID.

Vehicles

List Vehicle Makes And Models Lists the vehicle makes and models available in the Astara Connect database. With no parameters it returns all registered makes. Provide a make name to list that make models, or set Include All to return every make with its models.
List Vehicle Versions Retrieves the vehicle versions for a given model ID, including name, number of doors, transmission, engine displacement and power, motorization, and fuel types.

Astara Play Services

Calculate CO2 Emissions Computes per-trip CO2 emissions in grams for one or more trackers and aggregates them by day. Emissions are derived from each vehicle WLTP value and the distance traveled per trip. Filter by an optional time range with start time and end time (YYYY-MM-DD HH:MM:SS). When Robust Output is enabled the calculation tolerates missing data per tracker and returns per-tracker error codes instead of failing.
Get Vehicle Info By Plate Returns vehicle information provided by Astara Play for a given license plate, including category, vehicle type, environmental sticker, and the license registration month and year.
Get Fuel Station Info Returns detailed information for a fuel station provided by Astara Play, including address, brand, opening hours, coordinates, and current fuel prices per liter by fuel type.
List Nearby Charge Points Returns electric-vehicle charge points from Open Charge Map within a radius (in kilometers, default 0.5) of a latitude and longitude. Returns at most 100 charge points regardless of radius.

Frequently Asked Questions

What can FlowRunner do with Astara Connect?

FlowRunner agents can run List Trackers, Get Tracker, and Register Tracker in Astara Connect, plus 28 more actions.

Does connecting Astara Connect to FlowRunner require OAuth?

No. Astara Connect connects to FlowRunner with an API key, no OAuth flow required.

Can Astara Connect trigger a FlowRunner workflow automatically?

Astara Connect doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Astara Connect

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us