I have a google action which I am trying to export as an Alexa skill using these instructions. https://dialogflow.com/docs/integrations/alexa-exporter
The Alexa Skills Kit console asks for an HTTPS service endpoint, but I don't know what to set here
Is it the same as the Webhook fulfillment URL in dialogflow ?
Also when I try opening the https webhook url in the browser I get this error -
Action Error: no matching intent handler for: null
This does not "export a Google Action" for use as a Skill.
What it does is let you use Dialogflow to help define the user Intents, phrases, and Slot Entities that the legacy Skill Console expected. In particular it does not send your Alexa voice commands to Dialogflow for processing. The "fulfillment" section for Dialogflow is not used for Alexa handling.
Alexa still expects either an AWS Lambda or an HTTPS webhook to be specified where you will do the processing using its JSON format.
Related
Is possible to call a skill from Alexa using an API?
When I search about this i find things about use API inside skill code from developer.amazon.com, but in this case we use API in skill. Not the API calling this skill from a request
Is possible to do this?
Short answer: Not today
Why? Because using Alexa requires an account and no API is available to login as a user on Alexa. Maybe one day, that would be helpful.
We are working on the Alexa Skill that uses the Google OAuth API for account linking. Everything works well on the Alexa skill.
Now, When we use the account linking using google account. On the OAuth consent screen when the Google API Application type is selected to internal Shows the correct details i.e. Choose an account to continue to {Application Name}. But When the Application type is selected to Public it shows the wrong details i.e. Choose an account to continue to {amazon.com}. Which is incorrect amazon.com isn't requesting for the information?
Our Google API Project isn't verified yet.
Any leads will be helpful.
Thanks.
All public applications should apply for verification. If you are not using sensitive scopes, you should apply for brand verification for your app name to be displayed.
Read more about brand verification here: https://support.google.com/cloud/answer/9110914?hl=en&ref_topic=3473162#verification-types
I'm looking to move from Slack to Hangouts Chat, but heavily rely on getting alerts on chat sent from email. What's the easiest way to create an Alert in Hangouts Chat like the Email App in Slack.
The way the Slack App works is that it provides a specialized email address like: randomKey#company.slack.com
then when an email is received to the specialized email address it posts the contents to a channel.
any help would be appreciated. Currently I see other suggestions out there that do time-based triggers with email filters (How to trigger a Google Apps Script once an email get in the inbox?). But not sure if this is the easiest way / best way.
As of now, there is no direct integration between hangouts chat and Gmail. There are some workarounds that you can use to achieve your goal. The most popular approach is to use Push Notification Services of Gmail API using Pub/Sub which reads a particular email received in your inbox. Receiving this email you can then invoke your hangouts chat or send alerts to hangouts chat room via webhook.
Push Notification Documentation
Hangouts Chat API Documentation
Hope this answers your question!!!
I am using node.js, Alexa sdk with express for handling requests and responses. How can I get skill id from the response which is alexa sending to my endpoint?
The skill Id is the application id inside the session object.
alexaResponse.session.application.applicationId
I am developing a custom skill in Alexa, and just trying to return a hard coded response on a https service endpoint on port 8443 based on my sample utterances and intent schema defined on Amazon Alexa Console.
While testing from Alexa Service Emulator i am getting error There was an error calling the remote endpoint, which returned HTTP 405 : Method Not Allowed
While accessing the endpoint URL from POSTMEN i do get below mentioned response
{"response":{"shouldEndSession":true,"outputSpeech":{"text":"All appliance are working as expected","type":"PlainText"}},"sessionAttributes":{},"version":"1.0"}
I am finding it hard to understand where i am doing wrong.
Alexa is pretty picky when it comes to hosting skills externally. It sounds like this could be the issue. It can be done, you just have the follow the rules Alexa defines.
From the docs
The service must support HTTP over SSL/TLS, leveraging an Amazon-trusted certificate.
The service must accept requests on port 443
For testing, Amazon accepts different methods for providing a certificate.
For details, see the “About the SSL Options” section of Registering and Managing Custom Skills in the Developer Portal.