Closed diamondobama closed 4 years ago
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!
and we'll verify it.
ℹ️ Googlers: Go here for more info.
@googlebot I signed it!
On Fri, Feb 14, 2020 at 1:28 PM googlebot notifications@github.com wrote:
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data https://cla.developers.google.com/clas and verify that your email is set on your git commits https://help.github.com/articles/setting-your-email-in-git/.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version https://opensource.google/docs/cla/#troubleshoot).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data https://cla.developers.google.com/clas and verify that your email is set on your git commits https://help.github.com/articles/setting-your-email-in-git/.
- The email used to register you as an authorized contributor must also be attached to your GitHub account https://github.com/settings/emails.
ℹ️ Googlers: Go here https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2FGoogleCloudPlatform%2Fdialogflow-integrations%2Fpull%2F17 for more info.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/dialogflow-integrations/pull/17?email_source=notifications&email_token=ABXOUQ5UILN3LUKEKMBFTLLRCZ56LA5CNFSM4KVGHVG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELYQISQ#issuecomment-586220618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXOUQZWPJIFOQBWRKLJE5TRCZ56LANCNFSM4KVGHVGQ .
Twilio accepts location and media sharing from a platform like WhatsApp. When this content comes in, the
body.Body
parameter is left empty and additional parameters are added for these content types. Dialogflow however, can't process an empty body content, hence the request fails.For this purpose, if location is shared, we should pass
geoLocation
in thebody
parameter; if it's any other media type, we get the type fromMediaContentType0
and pass that.Then, on Dialogflow side, we process this information by providing training data that matches e.g. geolocation, image/jpeg, audio/mp3, application/pdf...etc. And we read additional information through the fulfillment in
req.originalDetectIntentRequest.payload
e.g.req.originalDetectIntentRequest.payload.MediaUrl0
.