Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Google Assistant

With Twilio Autopilot you can build Google Assistant actions. On this page we'll walk you through how to link Google Assistant so you can build Google Assistant Actions with Autopilot.

To set Google Assistant, follow these steps:

  1. Go to and create a project.
  2. Define a Google Action Manifest. You'll need:
    • A unique name to describe your action. "REPLACE_THIS" in this example.
    • One or more "trigger" phrases that Google Home will listen for to activate this skill
    • Your Autopilot URL for Google Assistant.
    • You'll need this file to define your manifest:
    • {
       "actions": [
           "description": "Default Welcome Intent",
           "name": "MAIN",
           "fulfillment": {
             "conversationName": "REPLACE_THIS"
           "intent": {
             "name": "actions.intent.MAIN",
             "trigger": {
               "queryPatterns": [
                 "talk to REPLACE_THIS"
       "conversations": {
         "REPLACE_THIS": {
           "name": "REPLACE_THIS",
           "url": "https://<ACCOUNT_SID>/<ASSISTANT_SID>/google-assistant"
       "locale": "en"

Create your own version of the above file with your own names, phrases and URL filled in.

Create Project on Google

Follow the action project setup on the following page. You will be using the "gaction" CLI tool to upload the JSON file you defined above. This will create your project and wire up its fulfillment URL.

There is no need to define actions or intents in Google, as Autopilot will be taking care of the interaction model.

Once completed, you should be able to go into the test portion of the console, invoke your skill by using the trigger phrase and see your request in the Autopilot logs.

Autopilot URL Parameters

Parameter Description

A string representing the unique name of the destination Task. If no TargetTask is provided, the destination task is determined by the natural language understanding.

TargetTask is useful when you want to control what task a user is routed to.


Lets you send Inbound Context to Autopilot. Should be a JSON string containing key-value pairs to insert into the Autopilot memory before starting a dialogue with the bot.

Useful for passing data stored in third party systems like a CRM into Autopilot

Example 1: Using TargetTask parameter at the end of the URL<ACCOUNT_SID>/<ASSISTANT_SID>/google-assistant?TargetTask=handle_appointment_confirmation

Any message sent to number or messaging service configured with this URL will land in the handle_appointment_confirmation task.

Example 2: Passing Inbound Context with Memory<ACCOUNT_SID>/<ASSISTANT_SID>/google-assistant?Memory={"CarModel":"Diablo","CarMake":"Lamborghini","CarYear":"2019"}

Any message sent to a bot with this URL will insert CarModel, CarMake and CarYear into the Autopilot Memory.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.