> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/here.md). # HERE Connect HERE Location Services to StackAI workflows. ### Connectors Choose the connector that matches your authentication method. The options below use the names shown in StackAI. | Connector | Authentication | | --------- | -------------- | | HERE | API Key | #### HERE Connect a HERE API key for Location Services workflows. **Set up in HERE** 1. Prepare the HERE account or service that the workflow will access. Grant access to the required resources and operations. 2. **API Key:** Create an API key for a HERE app with the required Location Services subscriptions. **Set up in StackAI** 1. Open **Settings → Connections**, add a connection, and select **HERE**. 2. Enter the credentials and connection details in the fields below. 3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it. **Connection fields** | StackAI field | Required | What to enter | | ------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | API Key | Yes | Create an API key for a HERE app with the required Location Services subscriptions. [Provider instructions](https://platform.here.com/admin/apps). | #### Verify the connection Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action. If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change. ### Use an action 1. Add the required **HERE** action to the workflow. 2. Select a connection when the action requests one. 3. Complete the required fields. Use the reference picker when a value comes from another workflow step. 4. Run the workflow and inspect the action’s output. Check the result before using it in a later step. ### Actions #### Geocode Address Find coordinates and address matches for an address. **Inputs** | Field | Type | Required | Description | | --------------- | ------- | -------- | ----------------------------------------------------------------- | | Address | string | Yes | Address or place to locate. | | Maximum results | integer | No | Maximum results to return. Minimum: 1. Maximum: 100. Default: 20. | **Outputs** | Field | Type | Description | | ------- | ------------- | ----------------------------------------------------------------- | | Results | object\_array | Ranked address matches with coordinates and structured addresses. | #### Reverse Geocode Coordinates Find addresses near coordinates. **Inputs** | Field | Type | Required | Description | | --------------- | ------- | -------- | ---------------------------------------------------------------- | | Latitude | number | Yes | Latitude in decimal degrees. | | Longitude | number | Yes | Longitude in decimal degrees. | | Maximum results | integer | No | Maximum results to return. Minimum: 1. Maximum: 100. Default: 1. | **Outputs** | Field | Type | Description | | ------- | ------------- | ---------------------------------------------------- | | Results | object\_array | Nearby address matches with distance from the point. | #### Calculate Route Calculate a route between two coordinate pairs. **Inputs** | Field | Type | Required | Description | | --------------- | --------------- | -------- | -------------------------------------------------------------------------------------------- | | Start latitude | number | Yes | Latitude of the starting point in decimal degrees. | | Start longitude | number | Yes | Longitude of the starting point in decimal degrees. | | End latitude | number | Yes | Latitude of the destination in decimal degrees. | | End longitude | number | Yes | Longitude of the destination in decimal degrees. | | Travel mode | select (string) | No | How to travel between the two points. Available values: Car, Walking, Bicycle. Default: car. | **Outputs** | Field | Type | Description | | ------ | ------------- | ---------------------------------------------------------- | | Routes | object\_array | Routes with sections, travel time, distance, and geometry. | #### Search Places Nearby Find nearby places matching a search. **Inputs** | Field | Type | Required | Description | | --------- | ------- | -------- | ----------------------------------------------------------------- | | Search | string | Yes | Type of place or place name to find. | | Latitude | number | Yes | Latitude in decimal degrees. | | Longitude | number | Yes | Longitude in decimal degrees. | | Limit | integer | No | Maximum results to return. Minimum: 1. Maximum: 100. Default: 20. | | Offset | integer | No | Continue a previous search. Minimum: 0. Maximum: 99. Default: 0. | **Outputs** | Field | Type | Description | | ----------- | ------------- | ------------------------------------------------------------------ | | Results | object\_array | Ranked nearby places or addresses with result types and positions. | | Next offset | integer | Offset for the next page, if available. | #### Calculate Isoline Find the area reachable within a time or distance. **Inputs** | Field | Type | Required | Description | | ----------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------- | | Center latitude | number | Yes | Latitude in decimal degrees. | | Center longitude | number | Yes | Longitude in decimal degrees. | | Range measured by | select (string) | Yes | Measure reachability by travel time or distance. Available values: Travel Time (seconds), Travel Distance (meters). | | Range value | integer | Yes | Maximum travel time in seconds or distance in meters. Minimum: 1. | | Travel mode | select (string) | No | How to travel. Available values: Car, Walking, Bicycle. Default: car. | **Outputs** | Field | Type | Description | | --------------- | ------------- | -------------------------------------------------- | | Reachable areas | object\_array | Reachable area polygons and their requested range. | ### Important behavior Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data. The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stackai.com/integrations/catalog/here.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.