Action ID
:   `actions.intent.START_EXERCISE`

Description

:   Initiate the user's fitness-related physical activity in real-time (for
    example, live tracking of a run). Determine the physical activity to be
    initiated first, if required.

    We recommend that you specify entities for `exercise.name`.

    This built-in intent uses enumerated values for some parameters. Parameters that follow this
    pattern are listed in [Supported text field values](https://developer.android.com/reference/app-actions/built-in-intents/health-and-fitness/start-exercise#supported-text-id-values) below,
    with the enumerated parameter values they support.

## Example queries

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

- Start my run using ExampleProvider.
- Track my hike using ExampleProvider.
- Start walking for one hour using ExampleProvider.

## Recommended fields

The following fields represent essential information that users often
provide in queries that trigger this built-in intent:
[`exercise.name`](https://schema.googleapis.com/name)   

## Other supported fields

The following fields represent information that users often provide to
disambiguate their needs or otherwise improve their results:
[`exercise.@type`](https://schema.googleapis.com/Exercise)   
[`exercise.duration`](https://schema.googleapis.com/duration)   

## Supported text values by field

`exercise.@type`

- Exercise

`exercise.name`

- Aerobics
- Bench Press
- Biking
- Burpee
- Climbing
- Cross Fit
- Crunch
- Hiking
- Kayaking
- Lunge
- Other
- Plank
- Pull-up
- Push-up
- Rowing
- Running
- Sit-up
- Skiing
- Snow boarding
- Squat
- Stretching
- Surfing
- Swimming
- Walking
- Yoga

## Inventory availability by field

`exercise.name`

- Inline inventory

## Foreground app invocation

This built-in intent supports [foreground app invocation](https://developer.android.com/guide/app-actions/foreground-app).

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

The following example queries are specific to intent matching for foreground app invocation:

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

- Start my run
- Track my hike

## Sample XML files

For information about the `shortcuts.xml` schema, see [Create shortcuts.xml](https://developer.android.com/guide/app-actions/action-schema).


| **Deprecation notice:** Google is ending support for App Actions implemented using the
| `actions.xml` resource file. Please use the
| [Actions.xml migration guide](https://developer.android.com/guide/app-actions/legacy/migration-guide) to update your
| actions to use the fully supported Android Shortcuts framework. For details on
| the Shortcuts framework, see [App Actions overview](https://developer.android.com/guide/app-actions/overview).

<br />

### Handle BII parameters

### shortcuts.xml


```world-of-warcraft-toc
<?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.START_EXERCISE">
    <intent
      android:action="android.intent.action.VIEW"
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <!-- Eg. name = "Running" -->
      <parameter
        android:name="exercise.name"
        android:key="name"/>
      <!-- Eg. duration = "PT1H" -->
      <parameter
        android:name="exercise.duration"
        android:key="duration"/>
    </intent>
  </capability>
</shortcuts>
      
```

<br />

### actions.xml


```world-of-warcraft-toc
<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.START_EXERCISE">
    <fulfillment urlTemplate="myapp://custom-deeplink{?name,duration}">
      <!-- e.g. name = "Running" -->
      <!-- (Optional) Require a field eg.name for fulfillment with required="true" -->
      <parameter-mapping urlParameter="name" intentParameter="exercise.name" required="true" />
      <!-- e.g. duration = "PT1H" -->
      <parameter-mapping urlParameter="duration" intentParameter="exercise.duration" />
    </fulfillment>

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

<br />

### Use inline inventory

### shortcuts.xml


`exercise.name` is an
intent parameter that supports [inline inventory](https://developer.android.com/guide/app-actions/action-schema#inline-inventory).
By defining a `<shortcut>` for `exercise.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
`name_one`
shortcut, Assistant provides the associated shorcut identifier, `ID_ONE`, as
the URL parameter `name`
to fulfillment.

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

```transact-sql
<?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.START_EXERCISE">
    <intent
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <parameter
        android:name="exercise.name"
        android:key="name"/>
      <parameter
        android:name="exercise.duration"
        android:key="duration"/>
    </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.START_EXERCISE">
        <parameter-binding
          android:value="name"
          android:key="exercise.name"/>
      </capability-binding>
    </shortcut>
</shortcuts>
      
```

<br />

### actions.xml


`exercise.name` is an
intent parameter that supports [inline inventory](https://developer.android.com/guide/app-actions/action-schema#inline-inventory).
By defining an `<entity-set>` for `exercise.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
`name_one`
entity, Assistant provides the associated identifier, `ID_ONE`, as
the URL parameter `name`
to fulfillment.

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

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

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

  <entity-set entitySetId="nameEntitySet">
  <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="name_one" alternateName="@array/name_one_synonyms"/>
    <entity identifier="ID_TWO" name="name_two" alternateName="@array/name_two_synonyms"/>
  </entity-set>
</actions>
```

<br />

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
`name_one`
entity, Assistant provides `myapp://deeplink/one` as the fulfillment
URL.

```transact-sql
  <?xml version="1.0" encoding="utf-8"?>
  <!-- This is a sample actions.xml -->
  <actions>
    <action intentName="actions.intent.START_EXERCISE">
      <!-- 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="exercise.name">
        <entity-set-reference entitySetId="nameEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="nameEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="name_one" alternateName="@array/name_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="name_two" alternateName="@array/name_two_synonyms"/>
    </entity-set>
  </actions>
  
```

<br />

## JSON-LD sample

The following JSON-LD sample provides some example values that you can
use in the App Actions test tool:

```carbon
{
  "@context": "http://schema.googleapis.com",
  "@type": "Exercise",
  "duration": "PT1H",
  "name": "Running"
}
```