--- title: "Golemio Integration" description: "Golemio is the City of Prague's open data platform, operated by Operator ICT. Agents read air quality, traffic and pedestrian counts, public transport departures, parking, waste stations, city districts and municipal facilities as structured data." url: https://flowrunner.ai/integrations/golemio date_modified: 2026-09-04T19:22:58-07:00 --- # Golemio [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Golemio is the City of Prague's open data platform, operated by Operator ICT. Agents read air quality, traffic and pedestrian counts, public transport departures, parking, waste stations, city districts and municipal facilities as structured data. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 106 actions · API key · available [Golemio website](https://operator-ict.gitlab.io/) · [Platform Documentation](https://operator-ict.gitlab.io/golemio/documentation/en/) · Capability data verified 2026-08-27 1. A scheduled check runs over the monitored waste containers on a district contract 2. List Sorted Waste Stations returns each station, its containers, the waste types they take and their current fill level 3. Get Sorted Waste Picks reads the recorded emptying events across the contract window 4. The agent separates containers that reported no pick from containers that carry no sensor at all 5. The exception list posts to the contract manager with fill level and last recorded pick per container 6. The contract manager confirms each container is genuinely monitored before a missed collection is raised against the contractor ## What This Integration Enables Golemio is Prague publishing its own operating data, run by Operátor ICT, and that provenance is the whole reason to build on it. This is not a scraped mirror of a city website. It is the municipality's own output gateway, and it covers: - environment, through air quality stations, microclimate sensors and municipal building energy consumption - movement, through bicycle and pedestrian counters, roadworks and closures, floating car data and pothole reports derived from driver alerts - public transport, from GTFS timetables and stop times through to live vehicle positions and departure boards - parking and vehicle sharing, with occupancy, tariffs, payment machines and shared fleets in both Golemio's own shape and the interoperable GBFS format - civic infrastructure, including district boundaries, gardens, playgrounds, pharmacies and clinics, libraries, police stations, municipal offices with live queue waiting times, and sorted and bulky waste One property defines how you design against it: every route Golemio publishes is a read. There is no create, update or delete operation anywhere in this connector, because the platform is a publisher of city data and not a system of record you write back to. That is not a limitation to work around, it is the shape of the problem. Every consequential act a flow takes on this data, rescheduling a crew, filing a service claim, publishing an advisory, opening a maintenance ticket, happens in a different system and under someone's name. Two vendor limits are worth designing for as well. The account is rate limited per key rather than per address, so a flow that fans out over a list of stops will trip it. And a list response is capped, with a truncated result carrying no marker that says it was truncated. ### Without FlowRunner **City data read by eye**: Someone opens a municipal dashboard, reads a number and retypes it into an internal system **Conditions discovered on arrival**: A crew finds the closure, the full car park or the queue when it gets there **Service failures argued from memory**: A missed collection or a late run is a disagreement rather than a record ### With FlowRunner **City data read by a flow**: Air quality, transport, parking and waste readings arrive as structured records on a schedule **Conditions known before dispatch**: Restrictions, occupancy profiles and live vehicle positions are checked before the route is set **Service failures evidenced**: Recorded pick events and measurement histories back the claim, with the gaps in the data stated plainly ## Use Case Scenarios ### Dispatch that already knows what the street looks like Before a delivery or service route is committed, the agent calls List Traffic Restrictions with a moment set to the planned departure time, which answers what will be in force then rather than only what applies now. Get Floating Car Data adds the observed speeds and travel times on the segments the route uses, and Get Potholes flags road damage reported by drivers along the way. Where the last leg is on foot or by shared vehicle, List Shared Vehicles and Get GBFS Geofencing Zones show what is available and where an operator will not allow a trip to end. The resulting constraints are handed to route assignment in [Onfleet](https://flowrunner.ai/integrations/onfleet), and material changes post to the dispatch channel in [Slack](https://flowrunner.ai/integrations/slack) so the coordinator sees why the plan moved. ### A facilities program that watches its own buildings A city department or an operator managing municipal sites runs a monthly energy review. List Energetics Buildings returns the monitored buildings with their meters, List Energetics Devices explains what each device measures, and List Energetics Measurements pulls consumption over the period filtered by variable and address. Get Energetics Monthly Reading answers the single building, single variable, single month question that a year on year comparison is built from. Microclimate readings from Get Microclimate Measurements sit alongside them, so a consumption jump can be checked against the temperature the building actually experienced rather than against a citywide average. The series append to a workbook in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and buildings whose usage moved beyond the review threshold are summarized into the facilities channel in [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams). ### A public-facing display that stays current on its own A building lobby or a visitor app needs departures, air quality and parking in one place. Get Departure Boards returns the live board for the nearby stops, combining timetable with real time predictions, and the route once filter is what keeps it readable instead of repeating the same line five times. Get Public Departure Board serves the lighter widget where a compact payload matters more than detail. List Air Quality Stations supplies the current index for the neighborhood, and List Air Quality Index Types turns the raw number into the band and color a person can read at a glance. List Parking Measurements adds free spaces at the nearby car parks, and Get Parking Average Occupancy answers whether there will still be space at the time a visitor is actually arriving. ## Human-in-Loop Highlight The claim a waste contract flow wants to make is that a container was not emptied on schedule. Golemio can nearly support it. Get Sorted Waste Picks returns the recorded emptying events for a monitored container, and Get Sorted Waste Measurements returns its fill level readings, so a gap in the pick record next to a rising fill level looks exactly like a missed collection. The catch is that only containers fitted with a sensor produce these records at all, and an empty result usually means the container is unmonitored rather than that no collection happened. The two are indistinguishable in the response. Raising a service level failure against a contractor on an unmonitored container is an accusation built on the absence of a sensor, and it damages a working relationship in a way that a later correction does not undo. This connector also has no operation that could file that claim, because Golemio is read only by design, so the finding has to leave through a person regardless. The agent posts to the contract manager: "Six containers on the Vinohrady round show no recorded pick across the contract window. Four are flagged as monitored in List Sorted Waste Stations and their fill readings are rising, so those look like genuine misses. Two returned no measurements at all, which most likely means no sensor rather than no collection. Confirm the monitored status on those two before I put any of this in the contractor report?" That is FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design doing the thing it exists for. The agent reconciled every container against every pick event overnight. A person decides which of them becomes a claim. 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 106 actions ### Air Quality 4 - **List Air Quality Stations** Lists Prague's air quality measuring stations with their latest readings, including the overall index and the individual component measurements. Filter to a neighborhood by coordinates and range, or to one or more city districts. - **List Air Quality Component Types** Lists the pollutant component types reported for air quality stations, each with its code, readable name and measurement unit. Used to build a picker or to label readings. - **List Air Quality Index Types** Lists the air quality index bands, with the numeric level, its label and the color associated with it. Pairs with the station readings to turn a raw index value into a readable status. - **Get Air Quality History** Returns historical readings for a time window, optionally narrowed to a single sensor. Used to chart trends or compare a current reading against the same hour on previous days. ### Traffic Counting 5 - **List Bicycle Counters** Lists the permanent bicycle counters installed across Prague, with location, direction definitions and the identifiers needed to query detections. - **Get Bicycle Detections** Returns bicycle and pedestrian counts over a time window. Readings can be aggregated into fixed buckets rather than returned raw, which is what makes daily or weekly reporting practical. - **Get Bicycle Counter Temperatures** Returns the air temperature recorded alongside the counts by counters fitted with a thermometer, using the same aggregation buckets so a temperature series joins cleanly to a count series. - **List Pedestrian Locations** Lists the pedestrian counting locations with their identifiers, names and the directions each one distinguishes. - **Get Pedestrian Measurements** Returns pedestrian counts for a location over a time window, optionally restricted to one direction of travel. Used to measure footfall before and after an event or a road closure. ### City Geography 2 - **List City Districts** Lists Prague's city districts as GeoJSON features with their boundary polygons, official names and slugs. The slug it returns is what every other district filter expects, so this is usually the first call in a district scoped flow. - **Get City District** Returns a single district by numeric identifier, including its boundary geometry and administrative details. ### Public Amenities 5 - **List Gardens** Lists Prague's public gardens and parks with location, opening hours, facilities and accessibility. Filter by proximity or district to find green space near an address. - **Get Garden** Returns a single garden or park by identifier, with its full description, opening hours, images and on-site amenities. - **List Playgrounds** Lists children's playgrounds with location, equipment, surface type and accessibility. Filter by proximity or district. - **Get Playground** Returns a single playground by identifier with its full equipment list, surface, opening hours and images. - **List Playground Properties** Lists the equipment and feature codes used across the playground dataset, each with a readable description, so codes on a record become labels. ### Public Services 10 - **List Medical Institutions** Lists Prague's medical institutions, split into pharmacies and health care facilities. Filter by group, by proximity, or decode specializations with the type list. - **Get Medical Institution** Returns a single medical institution by identifier with its address, contact details, opening hours and specialization. - **List Medical Institution Types** Lists the institution type codes used in the dataset, each with its group and a readable description. - **List Municipal Authorities** Lists Prague's municipal authority offices, split into district municipalities and city hall branches, each with address, opening hours and the agendas handled there. - **Get Municipal Authority** Returns a single municipal authority office by identifier, with its address, contact details, opening hours and agendas. - **Get Municipal Authority Queues** Returns the live waiting queues at an office, with the number of people waiting and the estimated wait per agenda. Used to tell someone when to set off, or to alert when a queue clears. - **List Municipal Libraries** Lists the branches of the Municipal Library of Prague with location, opening hours and services. Filter by proximity or district. - **Get Municipal Library** Returns a single library branch by identifier with its address, contact details, opening hours and available services. - **List Municipal Police Stations** Lists the municipal police stations with location, opening hours and contact details. Filter by proximity or district. - **Get Municipal Police Station** Returns a single police station by identifier with its address, opening hours and contact details. ### Waste Collection 9 - **List Sorted Waste Stations** Lists the sorted waste collection points with the containers at each one, the waste types they take and, for monitored containers, their current fill level. Restrict to monitored stations, which are the only ones that report occupancy. - **Get Sorted Waste Measurements** Returns the fill level readings recorded by a monitored container over a time window. Only sensor-fitted containers produce these, so an empty result usually means the container is unmonitored rather than that no data exists. - **Get Sorted Waste Picks** Returns the recorded emptying events for a monitored container over a time window. Used to verify that a collection actually happened, or to measure the interval between pickups. - **Get Sorted Waste Pick Days** Returns the scheduled collection days for a container, addressed either by its Sensoneo code or by its KSNKO register identifier. Used to publish a pickup calendar for an address. - **List Bulky Waste Stations** Lists the scheduled bulky waste collection points, each of which exists only for a stated time window, so the period filter decides whether a station is in service. - **Get Bulky Waste Station** Returns a single bulky waste collection point by its custom identifier, with its location and the exact window during which it is staffed. - **List Waste Collection Yards** Lists the permanent waste collection yards with location, opening hours and the waste categories each accepts. - **Get Waste Collection Yard** Returns a single yard by identifier with its address, opening hours, operator and the full list of waste categories it accepts. - **List Waste Collection Yard Properties** Lists the waste category codes used across the yards dataset, each with a readable description, so codes on a yard record become labels. ### Parking 11 - **List Parking Locations** Lists parking locations from the current v3 dataset, with capacity, access restrictions, parking policy and live occupancy where a source reports it. Filter by bounding box, by who the spaces are dedicated to, or by policy. - **Get Parking Location** Returns a single v3 parking location by identifier, with capacity, access rules, opening hours and tariff references. - **Get Parking Average Occupancy** Returns the typical occupancy profile of a car park, broken down by day and hour. This is what predicts whether there will be space at a future time rather than only reporting what is free now. - **List Parking Measurements** Returns live and recent occupancy measurements, with occupied and free spaces at each reading. Narrow it to one car park by identifier. - **List Parking Tariffs** Lists the published tariffs, each with its price bands and validity period. Use the validity filters to get the schedule in force on a given date. - **Get Parking Tariff** Returns a single tariff by identifier with its full price band structure and validity period. - **List Parking Machines** Lists Prague's parking payment machines and information boxes with location, code and operating status. Filter by machine type or bounding box to map the nearest place to pay. - **Get Parking Machine** Returns a single payment machine or information box by identifier with its location, code, type and status. - **List Parking Sources** Lists the upstream data sources feeding the parking datasets. The identifiers it returns are what the primary source filter on the other parking operations expects. - **List Parking Locations V2** Lists parking locations from the earlier v2 dataset, with capacity, category and last known occupancy. Kept for integrations that depend on v2 identifiers. - **Get Parking Location V2** Returns a single parking location from the legacy v2 dataset by identifier. ### Vehicle Sharing 6 - **List Shared Vehicles** Lists every currently available shared vehicle in Prague across all operators and modes, with position, battery level and the company that runs it. - **Get Shared Vehicle** Returns a single shared vehicle by identifier with its position, availability, battery or fuel level and a deep link to reserve it in the operator's app. - **List Shared Bikes** Lists the shared bikes and scooters currently available, with position, operator and reservation link. The bike only view of the sharing dataset. - **Get Shared Bike** Returns a single shared bike by identifier with its position, operator and reservation link. - **List Shared Cars** Lists the shared cars currently available, with position, operator, fuel or charge level and reservation link. - **Get Shared Car** Returns a single shared car by identifier with its position, operator, fuel or charge level and reservation link. ### GBFS Feeds 11 - **List GBFS Systems** Lists the vehicle sharing systems republished in the standard GBFS format, each with the system identifier the other GBFS operations require. GBFS is the interoperable format mapping and journey planning tools consume. - **Get GBFS Feed Index** Returns the GBFS discovery document for one system, listing every feed it publishes and the URL of each. Call it first to learn which optional feeds an operator actually supports. - **Get GBFS Versions** Returns the GBFS specification versions a system publishes, so a consumer can pick the one it understands. - **Get GBFS System Information** Returns operator level details in GBFS form, including name, operator, timezone, support contacts and app store links. - **Get GBFS System Regions** Returns the named service regions a system divides its area into. Station and pricing records reference these identifiers. - **Get GBFS Vehicle Types** Returns the vehicle types a system operates, with propulsion type, range and form factor. Free vehicle records reference these rather than repeating the details. - **Get GBFS Station Information** Returns the static details of a system's docking stations, their names, positions and capacities. - **Get GBFS Station Status** Returns the live status of docking stations, with vehicles and free docks at each. Joins to the station information on station id. - **Get GBFS Free Bike Status** Returns the dockless vehicles a system currently has available, with position, range and reservation state. - **Get GBFS System Pricing Plans** Returns the pricing plans a system publishes, with base price, currency and per minute rates. Used to estimate a trip cost before offering it. - **Get GBFS Geofencing Zones** Returns the geofenced areas an operator enforces, such as no parking or reduced speed zones, as polygons with the rules attached. Used to warn a rider before they end a trip somewhere the operator will not allow. ### Energetics 10 - **List Energetics Buildings** Lists the municipal buildings whose energy consumption Prague publishes, each with its address and installed meters. Full detail includes the nested device and organization records. - **Get Energetics Building** Returns a single monitored building by identifier, with its address, owning organization and installed metering devices. - **List Energetics Devices** Lists the metering devices, each with the variable it measures and the building it belongs to. The device identifier is what makes a measurement row interpretable. - **Get Energetics Device** Returns a single metering device by identifier with the variable it measures, its unit and its building. - **List Energetics Organizations** Lists the organizations that own the monitored buildings, such as schools and city departments. - **Get Energetics Organization** Returns a single organization by identifier, with the buildings it is responsible for. - **List Energetics Measurements** Returns consumption measurements over a date range, filtered by the variable measured and by address. Used to compare consumption year on year or to spot a building whose usage has jumped. - **Get Energetics Monthly Reading** Returns the reading for one building, one variable and one calendar month. Every parameter is required because the reading is addressed by the combination rather than looked up by a single identifier. - **Search Energetics DeD Buildings** Searches the Data enabled Development building register by free text, returning matching buildings with their geographic identifier. - **Get Energetics DeD Building** Returns a single building from the Data enabled Development register by its geographic identifier, with the energy characteristics recorded for it. ### Microclimate 3 - **List Microclimate Locations** Lists the microclimate sensor locations installed around Prague. Each location groups several measuring points. - **Get Microclimate Points** Returns the individual measuring points at a location, each with the quantities it records. - **Get Microclimate Measurements** Returns readings such as air temperature, humidity and surface temperature for a location or a single point over a time window. Used to compare shaded and unshaded parts of the same square. ### Traffic 3 - **List Traffic Restrictions** Lists roadworks, closures and other traffic restrictions in the DATEX II situation record vocabulary. Set a moment to ask what was or will be in force then rather than only what applies now. - **Get Floating Car Data** Returns speeds and travel times derived from vehicles moving through the city, for a road segment addressed by Golemio location identifier or OpenStreetMap path. - **Get Potholes** Returns pothole and road damage reports derived from driver alerts over a time window. Used to feed a maintenance backlog or to check whether a reported defect is still being flagged. ### Public Transport 11 - **Get Departure Boards** Returns the live departure board for one or more stops, combining timetable with real time predictions. Stops can be addressed by several identifier types, and the route once filter is what makes a board readable rather than repetitive. - **Get Minimal Departure Board** Returns a compact departure board for a saved preset, intended for small displays. - **List Departure Presets** Lists the saved departure board presets. Each names a fixed set of stops and filters, and is what the minimal board expects. - **Get Transfer Boards** Returns the onward connections a passenger can transfer to from a given trip, which is what an on board display shows as a vehicle approaches a stop. - **List Transport Info Texts** Returns service information notices such as diversions and lift outages, with the stops and routes each applies to. Include future notices to see what has not started yet. - **List Vehicle Positions** Returns live positions of public transport vehicles, with delay, the trip each is running and its next stop. Filter by route to follow one line. - **Get Vehicle Position By Trip** Returns the live position of the vehicle running a specific trip, optionally with the full history of positions recorded on that run. - **List Public Vehicle Positions** Returns live positions from the simplified public feed, filtered to a map bounding box and to particular lines or modes. The lighter route for driving a map view. - **Get Public Vehicle Position** Returns a single vehicle from the simplified public feed by identifier. Scopes pull in the trip, stop times, shape or vehicle description alongside the position. - **Get Public Trip** Returns a single trip from the simplified public feed, optionally enriched with stop times, route shape and vehicle description. - **Get Public Departure Board** Returns a compact departure board from the simplified public feed for a set of stops. Cheaper per departure, which suits a widget or a display. ### GTFS Schedule 9 - **List GTFS Routes** Lists the routes in the Prague GTFS schedule, with public line number, long name, transport type and branding colors. Used to build a line picker or resolve a line number to a route identifier. - **Get GTFS Route** Returns a single route by identifier with its line number, terminus names, transport type and branding colors. - **List GTFS Stops** Lists the stops with names, positions, wheelchair accessibility and the identifiers that map them onto the city's other registers. Search by name or resolve several identifiers at once. - **Get GTFS Stop** Returns a single stop by identifier with its name, position, zone, accessibility and parent station. - **Get GTFS Stop Times** Returns the scheduled calling times at a stop for a service date and time window. This is the timetable rather than the live board, so it is the right source for planning ahead or checking what should have run. - **List GTFS Trips** Lists the scheduled trips, optionally narrowed to those calling at a stop on a given service date. A trip is one individual run of a route rather than the route itself. - **Get GTFS Trip** Returns a single trip by identifier. The include toggles embed calling times, map shape, stop records, calendar and route in one response instead of four more calls. - **Get GTFS Shape** Returns the geographic shape a trip follows, as an ordered list of points suitable for drawing the line on a map. - **List GTFS Services** Lists the service calendars in force, which say which days each pattern of trips runs. Set a date to find the services active that day, for example to check whether a holiday timetable applies. ### Street Furniture 6 - **List Street Furniture Kinds** Lists the kinds of street furniture the wayfinding dataset covers: display cases, information panels, obelisks, signposts and totems. - **Get Street Furniture Metadata** Returns the metadata of the wayfinding dataset, including when it was last refreshed and which attributes each element kind carries. - **List Information Panels** Lists the wayfinding information panels with location and installation state. Scopes pull in the routes shown on each panel or the status of its display hardware, and the state filter finds panels that are only planned or already canceled. - **List Street Furniture Elements** Lists the street furniture of one kind, with position and installation details. Information panels have their own operation because they take extra filters. - **Get Street Furniture Element** Returns a single piece of street furniture by kind and identifier, with its full attribute set and installation history. - **List JIS Events** Returns the events published to Prague's unified information system displays, such as incidents, disruptions and service changes, over a display period. Shows what is currently in front of passengers on the street. ### GTFS Realtime 1 - **Get GTFS Realtime Feed** Downloads one of Prague's GTFS Realtime feeds as base64 encoded Protocol Buffer data. These are the standard machine feeds journey planners consume: trip updates carry delays, vehicle positions carry locations, and alerts carry service disruptions. The response is binary, so decode it with a GTFS Realtime library. For values a flow can use directly, prefer the vehicle position and departure board operations. ## Frequently Asked Questions ### What can FlowRunner do with Golemio? FlowRunner agents can run List Air Quality Stations, List Air Quality Component Types, and List Air Quality Index Types in Golemio, plus 103 more actions. ### Does connecting Golemio to FlowRunner require OAuth? No. Golemio connects to FlowRunner with an API key, no OAuth flow required. ### Can Golemio trigger a FlowRunner workflow automatically? Golemio doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Golemio?** This integration exposes Golemio 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/golemio. Site index: https://flowrunner.ai/llms.txt