Create call

shortcuts.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample shortcuts.xml -->
<shortcuts xmlns:android="http://schemas.android.com/apk/res/android">
  <capability android:name="actions.intent.CREATE_CALL">
    <intent
      android:action="android.intent.action.VIEW"
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <!-- Eg. callFormat = "Audio" -->
      <parameter
        android:name="call.callFormat"
        android:key="callFormat"/>
      <!-- Eg. name = "John Doe" -->
      <parameter
        android:name="call.participant.name"
        android:key="name"/>
      <!-- Eg. telephone = "012-345-6789" -->
      <parameter
        android:name="call.participant.telephone"
        android:key="telephone"/>
      <!-- Eg. identifier = "John_Doe_User_Id" -->
      <parameter
        android:name="call.participant.identifier"
        android:key="identifier"/>
    </intent>
  </capability>
</shortcuts>
      

actions.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.CREATE_CALL">
    <fulfillment urlTemplate="myapp://custom-deeplink{?callFormat,name,telephone,identifier}">
      <!-- e.g. callFormat = "Audio" -->
      <!-- (Optional) Require a field eg.callFormat for fulfillment with required="true" -->
      <parameter-mapping urlParameter="callFormat" intentParameter="call.callFormat" required="true" />
      <!-- e.g. name = "John Doe" -->
      <parameter-mapping urlParameter="name" intentParameter="call.participant.name" />
      <!-- e.g. telephone = "012-345-6789" -->
      <parameter-mapping urlParameter="telephone" intentParameter="call.participant.telephone" />
      <!-- e.g. identifier = "John_Doe_User_Id" -->
      <parameter-mapping urlParameter="identifier" intentParameter="call.participant.identifier" />
    </fulfillment>

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

shortcuts.xml

call.callFormat is an intent parameter that supports inline inventory. By defining a <shortcut> for call.callFormat, 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 callFormat_one shortcut, Assistant provides the associated shorcut identifier, ID_ONE, as the URL parameter callFormat to fulfillment.

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

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample shortcuts.xml -->
<shortcuts xmlns:android="http://schemas.android.com/apk/res/android">
  <capability android:name="actions.intent.CREATE_CALL">
    <intent
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <parameter
        android:name="call.callFormat"
        android:key="callFormat"/>
      <parameter
        android:name="call.participant.name"
        android:key="name"/>
      <parameter
        android:name="call.participant.telephone"
        android:key="telephone"/>
      <parameter
        android:name="call.participant.identifier"
        android:key="identifier"/>
    </intent>
    </capability>
    <!-- Short and long labels must be @string resource. -->
    <shortcut
      android:shortcutId="ID_ONE"
      android:shortcutShortLabel="@string/shortcut_short_label"
      android:shortcutLongLabel="@string/shortcut_long_label">
      <capability-binding android:key="actions.intent.CREATE_CALL">
        <parameter-binding
          android:value="callFormat"
          android:key="call.callFormat"/>
      </capability-binding>
    </shortcut>
</shortcuts>
      

actions.xml

call.callFormat is an intent parameter that supports inline inventory. By defining an <entity-set> for call.callFormat, 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 callFormat_one entity, Assistant provides the associated identifier, ID_ONE, as the URL parameter callFormat to fulfillment.

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

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

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

  <entity-set entitySetId="callFormatEntitySet">
  <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="callFormat_one" alternateName="@array/callFormat_one_synonyms"/>
    <entity identifier="ID_TWO" name="callFormat_two" alternateName="@array/callFormat_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 callFormat_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.CREATE_CALL">
      <!-- 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="call.callFormat">
        <entity-set-reference entitySetId="callFormatEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="callFormatEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="callFormat_one" alternateName="@array/callFormat_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="callFormat_two" alternateName="@array/callFormat_two_synonyms"/>
    </entity-set>
  </actions>