--- title: Create a flow with an SLA Task trigger description: Configure your Service Level Agreement \(SLA\) definition to run a flow as the action plan. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/create-sla-task-flow.html release: australia product: Workflow Studio classification: workflow-studio topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Create a flow, Build flows, Flows, subflows, and actions, Workflow Studio, Build workflows] --- # Create a flow with an SLA Task trigger Configure your Service Level Agreement \(SLA\) definition to run a flow as the action plan. ## Before you begin - Role required: flow\_designer or admin ## About this task An SLA Task trigger only runs when a task record matches the conditions of a Service Level Agreement \(SLA\) definition. For example, you can run a flow whenever an incident record matches the **Priority 1 resolution \(8 hour\)** SLA Definition. ## Procedure 1. Navigate to **All** > **Process Automation** > **Flow Designer**. 2. Select **+ New** > **New Flow**. 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Name to uniquely identify your flow. The system computes the internal name of the flow from the name. |
| Application | Application scope to create your flow in. Global is the default. |
| Description | Description of your flow. |
| Protection | Selection to specify if the flow is read-only. You can only select a value when you create the flow in an application scope that you own. |
| Run As | Option to specify the user that runs the flow. You can select the system user or the user who initiates the session. Select the user who initiates the session option when updates should come from the user who triggered the flow. For example, use this option when you want the incident record comments to come from the user who started the flow. Settings for the Run as option in a flow don't apply to child subflows. The system runs flow actions as the user who initiates the flow. Verify that all users who can trigger a flow have the necessary security access to run its actions. The initiating user also determines user-specific settings such as date/time formats. **Note:** Inbound email flows ignore this setting and always run as the user who initiates the session. To test access controls for an inbound email flow, impersonate a typical inbound email user and manually trigger the flow. |