--- title: "HERE Integration" description: "Add HERE location intelligence to agent workflows. Agents geocode addresses into coordinates and back, search nearby places, power address autocomplete, calculate driving, walking, cycling, or truck routes, and enrich place IDs with full details." url: https://flowrunner.ai/integrations/here date_modified: 2026-08-04T10:04:16-07:00 --- # HERE [Utilities & Personal](https://flowrunner.ai/integrations/category/utilities-personal) Add HERE location intelligence to agent workflows. Agents geocode addresses into coordinates and back, search nearby places, power address autocomplete, calculate driving, walking, cycling, or truck routes, and enrich place IDs with full details. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [HERE website](https://here.com/) · [Platform Documentation](https://www.here.com/docs/) · Capability data verified 2026-07-28 1. A new order arrives with a customer-entered delivery address 2. Geocode Address converts the free-form address into coordinates with a match quality score 3. High-quality matches proceed; low-scoring matches queue with the ranked candidates attached 4. Calculate Route computes the truck route from the assigned depot with distance and travel time 5. The delivery plan updates with the route summary, and the stop joins the day's sequence 6. Dispatch sees the planned route and flagged addresses in the morning board 7. A dispatcher resolves the low-confidence addresses before vehicles roll, because a wrong geocode committed to a route costs a missed delivery window and a driver's hour ## What This Integration Enables HERE built its location stack for the industries where being wrong about geography costs money: automotive, logistics, fleet. That heritage shows in the details this connector exposes, truck as a first-class transport mode, match quality scores on every geocode, per-capability services tuned for their job. FlowRunner agents convert addresses to coordinates and back, search places and points of interest, power type-ahead address entry, calculate routes for car, pedestrian, bicycle, or truck, and hydrate any HERE place ID into a full record. - Geocode form and CRM addresses into coordinates with ranked, scored matches - Turn device GPS coordinates into human-readable street addresses - Calculate driving, walking, cycling, and truck routes with distance and duration - Find businesses and points of interest near any location - Add address autocomplete to intake forms and chat flows - Enrich saved place IDs with contact details, categories, and opening hours Coordinates written to records steer real vehicles and real commitments, which is why FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) checkpoint sits at the confidence boundary the API itself reports. ### Without FlowRunner **Addresses are trusted as typed**: Free-form entries go straight to drivers, and the bad ones are discovered curbside **Routes are planned for cars**: Travel estimates ignore truck restrictions, and the shortcut on the map is a low bridge in reality **Location questions interrupt people**: "What's near this customer" and "how far is that stop" are someone's manual lookup ### With FlowRunner **Every address carries coordinates and a confidence score**: Geocoding runs at intake, and only the uncertain matches consume human attention **Routes match the vehicle**: Truck mode routing respects the realities that car directions ignore **Location intelligence is a workflow step**: Nearby search, autocomplete, and place lookup run inline wherever flows need them ## Use Case Scenarios ### Clean coordinates from the moment a lead exists A [Typeform](https://flowrunner.ai/integrations/typeform) submission delivers a mailing address. The agent geocodes it, attaches the coordinates and normalized address, and writes the lead to [HubSpot](https://flowrunner.ai/integrations/hubspot). Low match scores route to review with the ranked candidates rather than silently taking the top hit. Territory assignment, distance-based routing, and coverage reporting all inherit coordinates that were verified once, at the door. ### Fulfillment planning with truck-honest ETAs Each new [Shopify](https://flowrunner.ai/integrations/shopify) order gets its shipping address geocoded and a Calculate Route run in truck mode from the nearest warehouse. Distance and travel time land on the order record, and the day's dispatch summary posts to [Slack](https://flowrunner.ai/integrations/slack). Delivery promises get made against routes a truck can actually drive, and the orders whose addresses would not geocode cleanly are fixed before they become a driver's problem. ### Coverage analysis across a service territory For each customer coordinate, the agent runs Discover Places to map the service points, partners, or competitors nearby, hydrates the notable ones with Lookup Place for hours and contact details, and logs the results to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The territory review works from a systematically assembled picture instead of anecdotes, and the gaps in coverage show up as empty rows, not surprises. ## Human-in-Loop Highlight Geocode Address hands back a ranked list with a match quality score, which is the API candidly saying "here is my best guess and how sure I am." The costly failure is ignoring that candor: auto-committing a mediocre match writes plausible-looking coordinates onto an order, and everything downstream, the route, the ETA, the driver's afternoon, executes faithfully against the wrong point on the map. So the score is the gate. High-confidence matches flow into records and routes untouched, and low scorers stop and present their candidates, the customer's raw entry against each normalized alternative, for a dispatcher who recognizes that "Industrial Pkwy" and "Industrial Park Way" are different streets in this town. Route calculations run freely since a recomputed route costs nothing, but the coordinates they are computed from get verified while fixing them is still free, before a vehicle is rolling toward the wrong one. 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 6 actions ### Geocoding 2 - **Geocode Address** Converts a free-form address or place name into coordinates, returning ranked matches with latitude and longitude, a normalized address, a HERE place ID, and a match quality score. Supports location bias and country restriction. - **Reverse Geocode** Converts coordinates into the nearest street address and place, with normalized address, place ID, and distance from the query point. ### Search 3 - **Discover Places** Searches businesses and points of interest matching a free-form query near a location, returning ranked results with title, category, address, coordinates, distance, and a place ID. - **Autosuggest** Returns type-ahead place and address suggestions for a partial query near a location, with highlighted match ranges and place IDs. The engine behind search-as-you-type intake. - **Lookup Place** Retrieves the full record for a HERE place ID: address, coordinates, categories, contact details, and opening hours when available. The hydration step after any search or geocode. ### Routing 1 - **Calculate Route** Calculates a route between origin and destination for car, pedestrian, bicycle, or truck transport modes via HERE Routing v8, returning route options with total distance, duration, and per-section summaries, with return types from summary to polyline to turn-by-turn actions. ## Frequently Asked Questions ### What can FlowRunner do with HERE? FlowRunner agents can run Geocode Address, Reverse Geocode, and Discover Places in HERE, plus 3 more actions. ### Does connecting HERE to FlowRunner require OAuth? No. HERE connects to FlowRunner with an API key, no OAuth flow required. ### Can HERE trigger a FlowRunner workflow automatically? HERE doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at HERE?** This integration exposes HERE 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/here. Site index: https://flowrunner.ai/llms.txt