---
schema_version: "1"
id: a8f3bfdd1df12db5118036e788f8b63474d81bf1bf3971ab9f7c9543f59087d9
title: Build Flows for the Field Service Mobile App
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/mfs_flow_build.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.mfs_flow_build.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ffe3df72e9b6a19659c20e6f08b01167693db211760de4137c6eb868b329bb20
description: Create, activate, and manage flows for the Field Service mobile app in the drag-and-drop Flow Builder.
products:
  - Field Service
release: "264"
---
# Build Flows for the Field Service Mobile App

Create, activate, and manage flows for the Field Service mobile app in the drag-and-drop Flow Builder.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">The Field Service core features, managed package, and mobile app are available in <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">To access the Field Service mobile app, users need the Field Service Mobile user license.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d78440e82">User Permissions Needed</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d78440e82 ">To open, edit, or create a flow in Flow Builder:</td>

              <td class="slds-cell-wrap" style="vertical-align:top;" headers="d78440e82 ">Manage Flow</td>

            </tr>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d78440e82 ">To run flows from the app:</td>

              <td class="slds-cell-wrap" style="vertical-align:top;" headers="d78440e82 ">Run Flows</td>

            </tr>
          </tbody>
        </table>

Creating flows for the Field Service mobile app uses the same [Flow Builder](https://help.salesforce.com/articleView?id=flow_builder.htm&language=en_US) you know and love. Here are some basic guidelines to follow.

- Save your flows as the **Field Service Mobile Flow** type.
- Include help text on each screen so that users understand what is expected of them.
- Don’t ask more than one question per screen, especially if a screen involves picklists.

Some special flows, like image upload flows and signature capture flows, are great additions to the Field Service mobile app.

- **[Create a Flow to Capture Images in the Field Service Mobile App](https://help.salesforce.com/s/articleView?id=service.mfs_flow_build.htm&release=264.0.0&type=5)**  
    Create a flow that lets your team capture images from the Field Service mobile app. For example, make it easy for mobile workers to save photos of a customer’s asset before and after service.
- **[Customer Signatures on Service Reports with a Flow](https://help.salesforce.com/s/articleView?id=service.mfs_flow_build.htm&release=264.0.0&type=5)**  
    Using an app extension, you can add a final step to capture a customer’s signature at the end of a flow.

#### See Also

- [Flow Builder Tour](https://help.salesforce.com/s/articleView?id=platform.flow_builder.htm&type=5&language=en_US)
- [Flow Screen: File Upload](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp_fileupload.htm&type=5&language=en_US)
- [_Trailhead_: Customize User Settings](https://trailhead.salesforce.com/content/learn/modules/field-service-mobile/customize-user-settings)
- [Field Service Guidelines for Using Signatures on Service Reports](https://help.salesforce.com/s/articleView?id=service.fs_signature_guidelines.htm&release=264.0.0&type=5 "Field service workers can capture signatures from customers and partners on service reports. On the service report template, you define the number and type of signatures allowed.")

## Create a Flow to Capture Images in the Field Service Mobile App

Create a flow that lets your team capture images from the Field Service mobile app. For example, make it easy for mobile workers to save photos of a customer’s asset before and after service.

1. Build a flow with a Screen element that contains a File Upload component.
    
    An API name is generated when you label your flow. You need the API name to connect the flow to the Field Service mobile app.
2. Save your flow as the **Field Service Mobile Flow** type.

You can now connect the flow to the Field Service app with an app extension or Quick Action, just like any other flow.

## Customer Signatures on Service Reports with a Flow

Using an app extension, you can add a final step to capture a customer’s signature at the end of a flow.

After you [build a flow](https://help.salesforce.com/articleView?id=flow_builder.htm&language=en_US), create an app extension with these settings, which don't affect the rest of your flow. When the mobile app detects the Service\_Report\_Flow name, it launches the Service Report preview interface when your flow is complete.

- Label—Enter the text that you want to appear in the Actions tab. For example, My Service Report Flow.
- Type—Select **Flow**.
- Name—Enter Service\_Report\_Flow.
- Scoped to Object Types—Enter ServiceAppointment.
- Launch Value—Enter the API name of the flow that you want to conclude with signature capture.

Because the API name of the service report flow is unique, you can have only one Service\_Report\_Flow at a time.