> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/chat-flow/user-facing-nodes/display-nodes/location-sharing.md).

# Location sharing

Use the *Location Sharing* node to either [**send** ](#outbound-location-sharing)a location pin to a customer OR [**receive** ](#inbound-location-sharing)a location pin from the customer and use the latitude, longitude, location name, and address within your flow. 

{% embed url="<https://vimeo.com/761778223?share=copy>" %}

## Inbound location sharing

Request a location pin from your customer to use in the workflow.

To extract specific information relating to a location shared by your customers, use[ these variables](/chat-flow/variable-management-1.md#location-sharing) in your workflow.&#x20;

{% hint style="info" %}

* The "Send Location" button text cannot be edited.&#x20;
* Real-time (live) locations are not supported.&#x20;
  {% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/lcB48REAHEmSwT9F611s/image.png" alt="" width="563"><figcaption><p>Setup of a Location Sharing node (inbound) with text header.</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/j9TD2b1BxcIw77knFMLM/image.png" alt="" width="563"><figcaption><p>Example flow containing Location Sharing node (inbound)</p></figcaption></figure>

Below is an example of what the customer sees in WhatsApp when chatting with your business. The customer is asked to share their location with the business, which they can easily do by tapping the *Send location* button. The business can then utilize this information in their workflows.&#x20;

{% hint style="info" %}
On the Cloud environment, Meta does not support the header, and will only display the message and button.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/JSge1ypcvvYuUMkk3leo/image.png" alt=""><figcaption><p>Location request interactive message as seen by customers in WhatsApp</p></figcaption></figure>

## Outbound location sharing

Send a location pin to a customer they can open in their mobile device's navigation app.

{% hint style="info" %}
Real-time (live) locations are not supported.&#x20;
{% endhint %}

![Setup of a Location Sharing node (outbound)](https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/VGm58C44k7SkTBfjGjix/image.png)

![Example flow containing Location Sharing node (outbound)](https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/jR2r1O7PBk4QrVm4znXU/image.png)

Below is an example of what the customer sees in WhatsApp when chatting with your business. The business sends a location pin that the customer can open in the navigation app on their handset.

<img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/fCFg6nIu7EStulBSmMUw/image.png" alt="Busienss sending a location pin as seen by customers in WhatsApp." width="563">


---

# 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://help.clickatell.com/chat-flow/user-facing-nodes/display-nodes/location-sharing.md?ask=<question>&goal=<user_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.