feat(whatsapp): send native location request from get user data - #1135
Open
JuanBifrost wants to merge 1 commit into
Open
feat(whatsapp): send native location request from get user data#1135JuanBifrost wants to merge 1 commit into
JuanBifrost wants to merge 1 commit into
Conversation
Co-authored-by: JuanBifrost <JuanBifrost@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When Get User Data uses the Location reply format on WhatsApp, the step now sends Cloud API
interactive.location_request_message(the native “Send location” button) using the connected channel token. Other channels keep a text prompt.The inbound pin is stored as
lat,lngon the output custom field. Typedlat,lngis still accepted as a fallback.Tested in production on a WhatsApp Cloud API channel.
How to test
latitude,longitude.Screenshots
Native Cloud API location button (Get User Data, Location format):
Contact sends the pin; the step stores
lat,lngon the output field. Any followinglat/lonlines in the chat come from a separate Execute JavaScript mapping step, not from this PR: