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 widgets and slices

We recommend implementing Android widgets for this built-in intent. A widget presents information or interaction options from your app to improve user engagement in Google Assistant. Widgets are available for App Actions implementations using shortcuts.xml.

If you have a legacy App Actions implementation using actions.xml, use Android slices instead. We recommend migrating your implementation to shortcuts.xml to take advantage of widgets fulfillment and other improvements.

Supported text values by field





Inventory availability by field


Sample XML files

For information about the shortcuts.xml schema, see Create shortcuts.xml.

Handle BII parameters

shortcuts.xml

<?xml version="1.0" encodin>g<="utf-8"?
!-- This is a sam>p<le shortcuts.xml --
shortcuts xmlns:android="http://schemas.and>roi<d.com/apk/res/android"
  capability android:nam>e=&qu<ot;actions.intent.GET_MESSAGE"
    intent
      android:action="android.intent.action.VIEW"
      android:targetPackage="YOUR_UNIQUE_APPLIC>ATION_I<D"
      android:targetClass="YOUR_TARGET_CLASS&q>uot;
  <    !-- Eg. description = "Message topic or message content" --
      paramet>er
    <    android:name="message.description"
        android:key=&quo>t;descr<iption"/
      !-- Eg. temporalCoverage = "2017-06-01T13:00:00Z/2018-03-11T15:30:00Z&qu>ot; --
<      parameter
        android:name="mes>sage.te<mporalCoverage"
        android:key="temporalCoverage"/
      !-- Eg. disambiguatingDescription = &q>uot;Vid<eo" --
      parameter
      >  andro<id:name="message.disambiguatingDescription"
        android:key="disamb>iguatin<gDescription"/
      !-- Eg. senderName> = &quo<t;John Doe" --
      parameter
        android:name="message.sender.name">
      <  android:key="senderName">/
     < !-- Eg. senderEmail = "johndoe@gmail.com" --
      parameter
        android:name>="<message.sender.email"
        android:key=>"s<enderEmail"/
      !-- Eg. recipientName = "Matthew" --
      parameter
       > androi<d:name="message.recipient.name"
 >       <android:key="recipientName"/
      !-- Eg. recipientEmail = "matthew@gmail.com&qu>ot; --
<      parameter
        android:name="mes>sage.re<cipient.email"
        android:key="recipientEmail"/
      !-- Eg. senderTelephone = &q>uot;1<23-456->789<0" --<>/span>
 <     param>eter
        android:name="message.sender.telephone"
        android:key="senderTelephone"/
      !-- Eg. recipientTelephone = "012-345-6789" --
      parameter
        android:name="message.recipient.telephone"
        android:key="recipientTelephone"/
    /intent
  /capability
/shortcuts

actions.xml

<?xml version="1.0" encodin>g<="utf-8"?
!-- This is a s>a<mple ac>tio<ns.xml --
actions
  action intentName="ac>tions<.intent.GET_MESSAGE"
    fulfillment urlTemplate="myapp://custom-deeplink{?description,temporalCoverage,disambiguatingDescription,senderName,senderEmail,recipientName,recipientEmail,s>enderTe<lephone,recipientTelephone}"
      !-- e.g. description> = &quo<t;Message topic or message content" --
      !-- (Optional) Require a field eg.d>escript<ion for fulfillment with required="true" --
      parameter-mapping urlParameter="des>criptio<n" intentParameter="message.description" required="tru>e"< /
      !-- e.g. temporalCoverage = "2017-06-01T13:00:00Z/2018-03-11T15:30:00Z" --
>      p<arameter-mapping urlParameter="temporalCov>erage&q<uot; intentParameter="message.temporalCoverage" /
      !-- e.g. disambiguatingDescription = "Vid>eo"<; --
      parameter-mapping urlPar>ameter=<"disambiguatingDescription" intentParameter="message.disambiguatingD>escript<ion" /
      !-- e.g. senderName = ">;John D<oe" --
      parameter-mapping urlParameter="senderName" intentParamet>er=&quo<t;message.sender.name" /
      !>-- e.g.< senderEmail = "johndoe@gmail.com" --
      parameter-mapping urlParameter=&quo>t;sende<rEmail" intentParameter="message.sende>r.email<" /
      !-- e.g. recipientName = "Matthew" --
      parameter-mapping urlP>aramete<r="recipientName" intentParameter=>"m<essage.recipient.name" /
      !-- e.g. recipientEmail = "matthew@gmail.com" ->-
     < parameter-mapping urlParameter="recipient>Email&q<uot; intentParameter="message.recipient.email" /
      !-- e.g. senderTelephone = "1>23-45<6-7890"> --
  <    parameter-mapping urlParameter="senderTelephone" intentParameter="message.sender.telephone" />
    <  !-- e.g. recipientTelephone = "012-34>5-6<789&quo>t<; --
   >   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

shortcuts.xml

message.disambiguatingDescription is an intent parameter that supports inline inventory. By defining a <shortcut> 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 shortcut, Assistant provides the associated shorcut 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" encodin>g<="utf-8"?
!-- This is a sam>p<le shortcuts.xml --
shortcuts xmlns:android="http://schemas.and>roi<d.com/apk/res/android"
  capability android:nam>e=&qu<ot;actions.intent.GET_MESSAGE"
    intent
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID&q>uot;
  <    android:targetClass="YOUR_TARGET_CLASS"
      parameter
        android:n>ame=&qu<ot;message.description"
        android:key="description"/
      parameter
       > androi<d:name="message.temporalCoverage"
        android:key="temporalCoverage"/
      parameter
     >   andr<oid:name="message.disambiguatingDescription"
        android:key="disam>biguati<ngDescription"/
      parameter
        android:name="message.sender.name">;
     <   android:key="senderName"/
      parameter
        android:name="message.se>nder.em<ail"
        android:key="senderEmail"/
      parameter
        android:name=&q>uot;mes<sage.recipient.name"
        android:key="recipientName"/
      parameter
       > androi<d:name="message.recipient.email"
        android:key="recipientEmail"/
      param>eter
<       > andr<oid:name=&q>uot;m<essage.sender.telephone"
        android:key=&quo>t;sen<derTelephone"/
      parameter
        android:name="message.recipient.telephone"
        android:key="recipientTelephone"/
    /intent
    /ca>pabilit<y
    !-- Short and long labels must be @string resource. ->-
    sho<rtcut
      android:shortcutId="ID_ONE"
      android:shortcutShortLabel="@string/shortcut_short_label"
    >  andro<id:shortcutLongLabe>l=&qu<ot;@strin>g</shortcut_>long_label"
      capability-binding android:key="actions.intent.GET_MESSAGE"
        parameter-binding
          android:value="disambiguatingDescription"
          android:key="message.disambiguatingDescription"/
      /capability-binding
    /shortcut
/shortcuts

actions.xml

message.disambiguatingDescription is an intent parameter 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" encodin>g<="utf-8"?
!-- This is a s>a<mple ac>tio<ns.xml --
actions
  action intentName="ac>tions<.intent.GET_MESSAGE"
    fulfillment urlTemplate="myapp://dee>plink{?<disambiguatingDescription}" 
      !-- disambiguati>ngDescr<iption = "ID_ONE" or "ID_TWO"  --
      !-- If no inventory match, d>isambig<uatingDescription is a text value, such as "Video" --
      !-- (Optional) Use en>tityMat<chRequired="true" to require inventory match for fulfillment --
      parameter-mapping urlParameter=&>quot;<disambiguati>ngDesc<ription" intentParameter="message.di>sambi<guatingDescription" /
    /fulfillment

    !>-- Defi<ne parameters with inventories here --
    parameter name="messag>e.dis<ambiguatin>gDe<scripti>on&q<uot;
      entity-set-reference entitySetId="disambigu>ati<ngDescriptionEntitySet"/
    /para>meter<
  /action

  entity-set entitySetId="disambiguatingDescriptionEntitySet"
  !-- Provide an identifier per entity --
>    e<ntity identifier="ID_ONE" name="disambiguatingDescription_one" alternateName="@array/disambiguatingDe>scr<iption_one_>s<ynonyms&>quot;/
    entity identifier="ID_TWO" name="disambiguatingDescription_two" alternateName="@array/disambiguatingDescription_two_synonyms"/
  /entity-set
/actions

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" encodin>g=&<quot;utf-8"?
  !-- This is a s>amp<le acti>ons.x<ml --
  actions
    action intentName="ac>tions.i<ntent.GET_MESSAGE"
      !-- Use url from inventory matc>h for d<eep link fulfillment --
      fulf>illment <urlTemplate="{@url}" /

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

  >    !--< Define parameters with inventories here --
      >parameter< name="message.disambiguatingDescription"
        entity-set>-refere<nce entity>SetId<=">disamb<iguatingDescriptionEntitySet"/
      /parameter
    /a>ction

<    entity-set entitySetId=&quo>t;disam<biguatingDescriptionEntitySet"
      !-- Provide a URL per entity --
      entity url="myapp://deeplink/one" name=&quo>t;disam<biguatingDescription_one" alternateName="@array/disambiguatingDescription_one_synonyms"/
      entity url="myapp:>//dee<plink/two&q>uot<; name=&>quot;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"
}