# Location Sharing node & Media node enhancements

## Release Summary

The focus of the release was to introduce bi-directional [location sharing](https://clickatell.gitbook.io/flow/user-facing-nodes/display-nodes/location-sharing) via the WhatsApp channel and to further enhance the [Media node](https://clickatell.gitbook.io/flow/user-facing-nodes/display-nodes/user-facing-interactions-media-node). 

### **NEW FEATURES**

[**Location sharing** **node**](https://clickatell.gitbook.io/flow/user-facing-nodes/display-nodes/location-sharing)

When using Chat Flow, users can now add a new **Location Sharing node** into their flows to either send a location pin to the end-user OR receive a location pin from the end-user and use the latitude, longitude, location name, and address within their flow. 

*Note: this is available for use on the **WhatsApp** channel only.* 

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2FaNRQLPzAzYvkJfhdmR1F%2Fimage.png?alt=media&#x26;token=0251590c-37db-4fbc-820b-bc582b5f8b9a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2Fm9k9ROXO1RWkLVNimgtq%2Fimage.png?alt=media&#x26;token=feefdd0d-24c0-47aa-b432-42ddeebb821d" alt=""><figcaption><p>Outbound (left) and inbound (right) location sharing</p></figcaption></figure>

**ENHANCEMENTS**

[**Media node enhancements**](https://clickatell.gitbook.io/flow/user-facing-nodes/display-nodes/user-facing-interactions-media-node)

Previously, using the Media node to send outbound media to an end-user would cause the current flow to end. With the latest release, we’ve made an important enhancement to the Media node such that the flow-builder now has the option to specify a next step/flow that the flow must logically continue to after sending an outbound media file to an end-user. This allows for a much smoother experience for both the user and the flow-builder to use as an alternative to the ‘stop-and-start’ feel when sending outbound media.&#x20;

Flow-builders can also now specify the file name that is displayed to the end-user when sending media files by optionally entering a file name to override the existing one with.

<figure><img src="https://2380245535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl8ao2e7ogQyZBti1BuxA%2Fuploads%2FbD7Il2GiXz45mjduIZNJ%2Fimage.png?alt=media&#x26;token=c291c397-d2fc-4e36-80d9-16de752935dc" alt=""><figcaption><p>Select whether the session should end (left) or continue (right) after outbound media node</p></figcaption></figure>