Get account

Action ID

actions.intent.GET_ACCOUNT

Description

Present a summary of the user's account in an app. Determine which account to view by name and description using the account.name and account.description intent parameters, if available. If an account cannot be identified using those parameters, ask the user to determine the account.

Locale support

Functionality	Locales
Preview creation using App Actions test tool	en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU, es-ES, pt-BR
User invocation from Google Assistant	en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU, es-ES, pt-BR

Example queries

en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU

• Show my ExampleProvider portfolio.
• Please show me the performance of my ExampleProvider portfolio.
• Let me see my ExampleProvider investment portfolio.
• Bring up my ExampleProvider portfolio.
• Get ExampleProvider account balance.
• What's my ExampleProvider account balance?

es-ES

• Abrir en ExampleProvider mi cartera de inversiones.
• Ver el saldo de mi cuenta de Bankia con ExampleProvider.
• Ver el rendimiento de mis valores en ExampleProvider
• Mostrar mi cartera de inversiones en ExampleProvider.
• Muestra mis inversiones en ExampleProvider.
• Quiero saber el saldo de mi cuenta a través de ExampleProvider.

pt-BR

• Usar ExampleProvider para ver meu portfólio de fundos.
• Pode ver no ExampleProvider como está o meu portfólio de investimentos?
• Mostrar meus fundos imobiliários no ExampleProvider.
• Consultar meu fundo de investimentos no ExampleProvider.
• Abra o ExampleProvider e me mostre meus investimentos.
• Abrir o ExampleProvider e ver meus investimentos.

Other supported fields

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

account.@type
account.description
account.name
account.provider.@type
account.provider.name

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

account.@type

• Account

account.provider.@type

• Organization

Inventory availability by field

account.name

• Inline inventory

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_ACCOUNT">
    <fulfillment urlTemplate="myapp://custom-deeplink{?accountName,description,providerName}">
      <!-- Eg. accountName = "utility" -->
      <!-- (Optional) Require a field eg.accountName for fulfillment with required="true" -->
      <parameter-mapping urlParameter="accountName" intentParameter="account.name" required="true" />
      <!-- Eg. description = "Description of account" -->
      <parameter-mapping urlParameter="description" intentParameter="account.description" />
      <!-- Eg. providerName = "Example Provider" -->
      <parameter-mapping urlParameter="providerName" intentParameter="account.provider.name" />
    </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

account.name is a field that supports inline inventory. By defining an <entity-set> for account.name, 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 accountName_one entity, Assistant provides the associated identifier, ID_ONE, as the URL parameter accountName to fulfillment.

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

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

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

  <entity-set entitySetId="accountNameEntitySet">
    <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="accountName_one" alternateName="@array/accountName_one_synonyms"/>
    <entity identifier="ID_TWO" name="accountName_two" alternateName="@array/accountName_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 accountName_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_ACCOUNT">
      <!-- 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="account.name">
        <entity-set-reference entitySetId="accountNameEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="accountNameEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="accountName_one" alternateName="@array/accountName_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="accountName_two" alternateName="@array/accountName_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.googleapis.com",
  "@type": "Account",
  "description": "Description of account",
  "name": "utility",
  "provider": {
    "@type": "Organization",
    "name": "Example Provider"
  }
}