Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. Release information is not available for APIs before Chrome 42, which was released in early 2015. If you need to know the outcome of an operation, then you pass a callback function into the method. Unless the doc says otherwise, methods in the chrome.* APIs are asynchronous: they return immediately, without waiting for the operation to finish. Or it could be that they've nudged things so the whole phrase triggers an Action named "Panera" because it uses Transactions.Chrome provides extensions with many special-purpose APIs like ntime and chrome.alarms. It could be that they have registered the invocation name of "delivery from Panera" and thus "I'd like" is a suitable trigger phrase. (So we might assume that using the Action Transaction API could allow other phrases, but thats just an assumption on our part.) This sort of thing has been mentioned publicly a few times by Googlers, but you can see more about this at their I/O presentation on Discovery ( ) and a presentation by Brad Abrams ( )Įxactly which one applies to Panera is difficult to tell. There may be other cues that could influence this as well and, like other SEO influencers, Google doesn't necessarily publish what those indicators are. This is like using a search engine on your Action and having Google return a snippet in the search results. If the phrase is associated with your Action enough, it may just trigger your action directly.
Google may use these phrases, as well as others it may set, to suggest your Action to users if they use the phrase. You can think of these explicit invocations as being similar to a user entering in a specific web URL.Īdditionally, you can also register other suggested phrases. In addition to these documented ones, that page also suggests that there can be other phrases that also work the same way - for example, "ask" works as well as no trigger phrase and just using your invocation name. There are a number of specifically documented trigger phrases in addition to "talk to" which can be used with the invocation name of your action. Chances are good you're not doing anything "wrong", but at the same time the Panera demo wasn't exactly "fake" either.Īction Discovery is actually very similar to websites and SEO. So I've come to the conclusion that it just doesn't work. "Sorry, this action is not available in simulation"Īnd if I try "Talk to " on my pixel phone, the test app opens, but if I say "Order from " on my pixel, it just finds search results. When I try "Order with " I get this error. Is this a bug with Api.ai or "Actions on Google" or am I doing something wrong? I'm setting these options you see below, but it still doesn't work. I did some research and saw that this option isn't necessarily in Api.ai, but it might be in the "Actions on Google".
So I don't know if the demo was fake or not, but they didn't have to start it with Talk to Panera. So it looks like they are starting the Panera app with "I'd like delivery from Panera". Everything is working as expected except that I cannot get the assistant to recognize my application with any key words except for "Talk to ".Īt first, I didn't think that it was possible at all, but I saw the Google I/O presentation of it. I'm working with Api.ai to make an app on the Google assistant.