Join us live on October 16-18th for our virtual DevFest. Register now.

Get message

Action ID
actions.intent.GET_MESSAGE
Description

Search and view messages, such as text messages, voice messages, or emails. Filter messages by description and date range using the message.description and message.temporalCoverage intent parameters to present the most relevant ones to the user. Determine the message format (like voice, video, or text) using the message.disambiguatingDescription intent parameter. Note that the voice and video message formats are distinct from the format of an attachment to a text message.

For messages received by the user, determine the sender using the message.sender.name, message.sender.email, and message.sender.telephone intent parameters.

For messages sent by the user, determine the recipient using the message.recipient.name, message.recipient.email, and message.recipient.telephone intent parameters.

We also recommend creating deeper, voice-forward experiences by integrating our partner solution for messaging.

Locale support

Functionality Locales
Preview creation using App Actions test tool en-US
User invocation from Google Assistant en-US

Example queries

The following fields represent essential information that users often provide in queries that trigger this built-in intent:

message.temporalCoverage
message.description
message.disambiguatingDescription
message.recipient.name
message.recipient.email
message.recipient.telephone
message.sender.name
message.sender.email
message.sender.telephone

Other supported fields

The following fields represent information that users often provide to disambiguate their needs or otherwise improve their results:

message.@type
message.recipient.@type
message.sender.@type

Android Slices

We recommend implementing Android Slices for this built-in intent. An Android Slice presents information or interaction options from your app to improve user engagement in the Google Assistant.

Supported text values by field





Inventory availability by field


Sample actions.xml

For information about the actions schema, read Create actions.xml.

Handle intent parameters as URL parameters

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.GET_MESSAGE">
    <fulfillment urlTemplate="myapp://custom-deeplink{?description,temporalCoverage,disambiguatingDescription,senderName,senderEmail,recipientName,recipientEmail,senderTelephone,recipientTelephone}">
      <!-- Eg. description = "Message topic or message content" -->
      <!-- (Optional) Require a field eg.description for fulfillment with required="true" -->
      <parameter-mapping urlParameter="description" intentParameter="message.description" required="true" />
      <!-- Eg. temporalCoverage = "2017-06-01T13:00:00Z/2018-03-11T15:30:00Z" -->
      <parameter-mapping urlParameter="temporalCoverage" intentParameter="message.temporalCoverage" />
      <!-- Eg. disambiguatingDescription = "Video" -->
      <parameter-mapping urlParameter="disambiguatingDescription" intentParameter="message.disambiguatingDescription" />
      <!-- Eg. senderName = "John Doe" -->
      <parameter-mapping urlParameter="senderName" intentParameter="message.sender.name" />
      <!-- Eg. senderEmail = "johndoe@gmail.com" -->
      <parameter-mapping urlParameter="senderEmail" intentParameter="message.sender.email" />
      <!-- Eg. recipientName = "Matthew" -->
      <parameter-mapping urlParameter="recipientName" intentParameter="message.recipient.name" />
      <!-- Eg. recipientEmail = "matthew@gmail.com" -->
      <parameter-mapping urlParameter="recipientEmail" intentParameter="message.recipient.email" />
      <!-- Eg. senderTelephone = "123-456-7890" -->
      <parameter-mapping urlParameter="senderTelephone" intentParameter="message.sender.telephone" />
      <!-- Eg. recipientTelephone = "012-345-6789" -->
      <parameter-mapping urlParameter="recipientTelephone" intentParameter="message.recipient.telephone" />
    </fulfillment>

    <!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
    <fulfillment urlTemplate="myapp://deeplink" />
  </action>
</actions>

Use inline inventory to guide query matching

message.disambiguatingDescription is a field that supports inline inventory. By defining an <entity-set> for message.disambiguatingDescription, you can uniquely identify entities that are of interest to your app or restrict fulfillment to the set of supported entities.

In the following example, when the user query matches the disambiguatingDescription_one entity, Assistant provides the associated identifier, ID_ONE, as the URL parameter disambiguatingDescription to fulfillment.

If there is no inventory match, the text value received in the query for message.disambiguatingDescription is passed as-is.

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.GET_MESSAGE">
    <fulfillment urlTemplate="myapp://deeplink{?disambiguatingDescription}" >
      <!-- disambiguatingDescription = "ID_ONE" or "ID_TWO"  -->
      <!-- If no inventory match, disambiguatingDescription is a text value, such as "Video" -->
      <!-- (Optional) Use entityMatchRequired="true" to require inventory match for fulfillment -->
      <parameter-mapping urlParameter="disambiguatingDescription" intentParameter="message.disambiguatingDescription" />
    </fulfillment>

    <!-- Define parameters with inventories here -->
    <parameter name="message.disambiguatingDescription">
      <entity-set-reference entitySetId="disambiguatingDescriptionEntitySet"/>
    </parameter>
  </action>

  <entity-set entitySetId="disambiguatingDescriptionEntitySet">
    <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="disambiguatingDescription_one" alternateName="@array/disambiguatingDescription_one_synonyms"/>
    <entity identifier="ID_TWO" name="disambiguatingDescription_two" alternateName="@array/disambiguatingDescription_two_synonyms"/>
  </entity-set>
</actions>

Derive fulfillment URL using inline inventory

The url attribute associated with the entity can be used to determine the fulfillment URL if there is an inventory match. In the following example, when the user query matches the disambiguatingDescription_one entity, Assistant provides myapp://deeplink/one as the fulfillment URL.

  <?xml version="1.0" encoding="utf-8"?>
  <!-- This is a sample actions.xml -->
  <actions>
    <action intentName="actions.intent.GET_MESSAGE">
      <!-- Use url from inventory match for deep link fulfillment -->
      <fulfillment urlTemplate="{@url}" />

      <!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
      <fulfillment urlTemplate="myapp://deeplink" />

      <!-- Define parameters with inventories here -->
      <parameter name="message.disambiguatingDescription">
        <entity-set-reference entitySetId="disambiguatingDescriptionEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="disambiguatingDescriptionEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="disambiguatingDescription_one" alternateName="@array/disambiguatingDescription_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="disambiguatingDescription_two" alternateName="@array/disambiguatingDescription_two_synonyms"/>
    </entity-set>
  </actions>
  

JSON-LD sample

The following JSON-LD sample provides some example values that you can use in the App Actions test tool:

{
  "@context": "http://schema.org",
  "@type": "Message",
  "description": "Message topic or message content",
  "disambiguatingDescription": "Video",
  "recipient": {
    "@type": "Person",
    "email": "matthew@gmail.com",
    "name": "Matthew",
    "telephone": "012-345-6789"
  },
  "sender": {
    "@type": "Person",
    "email": "johndoe@gmail.com",
    "name": "John Doe",
    "telephone": "123-456-7890"
  },
  "temporalCoverage": "2017-06-01T13:00:00Z/2018-03-11T15:30:00Z"
}