Create photograph

Action ID
actions.intent.CREATE_PHOTOGRAPH
Description
Open the camera function in an app. Determine EXIF data key-value properties like picture format, filter, or capture mode using the photograph.image.exifData.name and photograph.image.exifData.value intent parameters.

Locale support

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

Example queries

Other supported fields

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

photograph.@type
photograph.image.@type
photograph.image.exifData.@type
photograph.image.exifData.name
photograph.image.exifData.value

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.CREATE_PHOTOGRAPH">
    <fulfillment urlTemplate="myapp://custom-deeplink{?name,value}">
      <!-- Eg. name = "CameraFace" -->
      <!-- (Optional) Require a field eg.name for fulfillment with required="true" -->
      <parameter-mapping urlParameter="name" intentParameter="photograph.image.exifData.name" required="true" />
      <!-- Eg. value = "CameraFaceFrontCamera" -->
      <parameter-mapping urlParameter="value" intentParameter="photograph.image.exifData.value" />
    </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

photograph.image.exifData.value is a field that supports inline inventory. By defining an <entity-set> for photograph.image.exifData.value, 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 value_one entity, Assistant provides the associated identifier, ID_ONE, as the URL parameter value to fulfillment.

If there is no inventory match, the text value received in the query for photograph.image.exifData.value is passed as-is.

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

    <!-- Define parameters with inventories here -->
    <parameter name="photograph.image.exifData.value">
      <entity-set-reference entitySetId="valueEntitySet"/>
    </parameter>
  </action>

  <entity-set entitySetId="valueEntitySet">
    <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="value_one" alternateName="@array/value_one_synonyms"/>
    <entity identifier="ID_TWO" name="value_two" alternateName="@array/value_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 value_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_PHOTOGRAPH">
      <!-- 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="photograph.image.exifData.value">
        <entity-set-reference entitySetId="valueEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="valueEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="value_one" alternateName="@array/value_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="value_two" alternateName="@array/value_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": "Photograph",
  "image": {
    "@type": "ImageObject",
    "exifData": {
      "@type": "PropertyValue",
      "name": "CameraFace",
      "value": "CameraFaceFrontCamera"
    }
  }
}