- Action ID
actions.intent.GET_INVOICE
- Description
-
Present a user's bill or invoice. Determine what invoice the user is requesting or present multiple items, if applicable.
We recommend that you specify entities for
invoice.forService.name
.
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
Other supported fields
The following fields represent information that users often provide to disambiguate their needs or otherwise improve their results:
invoice.@type
invoice.forService.@type
invoice.forService.name
invoice.forService.provider.@type
invoice.forService.provider.name
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_INVOICE">
<fulfillment urlTemplate="myapp://custom-deeplink{?forServiceName,providerName}">
<!-- Eg. forServiceName = "Utility" -->
<!-- (Optional) Require a field eg.forServiceName for fulfillment with required="true" -->
<parameter-mapping urlParameter="forServiceName" intentParameter="invoice.forService.name" required="true" />
<!-- Eg. providerName = "Example Provider" -->
<parameter-mapping urlParameter="providerName" intentParameter="invoice.forService.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
invoice.forService.name
is a
field that supports inline inventory.
By defining an <entity-set>
for invoice.forService.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
forServiceName_one
entity, Assistant provides the associated identifier, ID_ONE
, as
the URL parameter forServiceName
to fulfillment.
If there is no inventory match, the text value received in the query for
invoice.forService.name
is passed
as-is.
<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
<action intentName="actions.intent.GET_INVOICE">
<fulfillment urlTemplate="myapp://deeplink{?forServiceName}" >
<!-- forServiceName = "ID_ONE" or "ID_TWO" -->
<!-- If no inventory match, forServiceName is a text value, such as "Utility" -->
<!-- (Optional) Use entityMatchRequired="true" to require inventory match for fulfillment -->
<parameter-mapping urlParameter="forServiceName" intentParameter="invoice.forService.name" />
</fulfillment>
<!-- Define parameters with inventories here -->
<parameter name="invoice.forService.name">
<entity-set-reference entitySetId="forServiceNameEntitySet"/>
</parameter>
</action>
<entity-set entitySetId="forServiceNameEntitySet">
<!-- Provide an identifier per entity -->
<entity identifier="ID_ONE" name="forServiceName_one" alternateName="@array/forServiceName_one_synonyms"/>
<entity identifier="ID_TWO" name="forServiceName_two" alternateName="@array/forServiceName_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
forServiceName_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_INVOICE">
<!-- 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="invoice.forService.name">
<entity-set-reference entitySetId="forServiceNameEntitySet"/>
</parameter>
</action>
<entity-set entitySetId="forServiceNameEntitySet">
<!-- Provide a URL per entity -->
<entity url="myapp://deeplink/one" name="forServiceName_one" alternateName="@array/forServiceName_one_synonyms"/>
<entity url="myapp://deeplink/two" name="forServiceName_two" alternateName="@array/forServiceName_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": "Invoice", "forService": { "@type": "Service", "name": "Utility", "provider": { "@type": "Organization", "name": "Example Provider" } } }