Two Step Instruction activity
Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message.
Roles and availability
- This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook.
Inputs
Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see .
|
Input |
Type |
Description |
|---|---|---|
|
Label |
String |
Title to display as activity and playbook card. |
|
Description |
String |
Information to display about activity usage or outcome. |
|
Run condition |
Condition Builder |
Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions.Note: Select Show additional options to see this field. |
|
Start Rule |
Choice |
Under Schedule > Start Rule, select a start rule for when your stage should start running:- When process starts: Your stage starts running as soon as the playbook starts.
Under Schedule > Start Rule, select a start rule for when your activity should start running:- When stage starts: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered.
|
|
Start with delay |
True/False |
Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the Start with delay input properties.Note: Select Show additional options to see this field. |
|
Initial Message |
String |
Message text to display to end users when the activity state is In Progress. |
|
Completed Message |
String |
Message text to display to end users when the activity state is Completed. |
|
Skipped Message |
String |
Message text to display to end users when the activity state is Skipped. |
After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional options to display these advanced inputs. For more information, see Activity experience.
|
Input |
Type |
Description |
|---|---|---|
|
Assignment Group |
Reference.Group [sys_user_group] |
Group responsible for completing the task associated with the activity.Note: Select Show additional options to see this field. |
|
Assigned To |
Reference.User [sys_user] |
User responsible for completing the task associated with the activity.Note: Select Show additional options to see this field. |
These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:
| Output | Type | Description |
|---|---|---|
| Record | Reference.Task[task] | Reference to the record associated with the activity. |
--- title: Two Step Instruction activity description: Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/two-step-instruction-activity.html release: australia product: Workflow Studio classification: workflow-studio topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Interactive activities, Playbooks reference, Playbooks, Workflow Studio, Build workflows] --- # Two Step Instruction activity Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message. ## Roles and availability - This activity is available as a common activity. Users with the admin, playbook.admin, or pd\_author can add this activity to a playbook. ## Inputs Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the value. To learn more about the pill-picker, see . <table id="table_ajt_sr3_plb"><thead><tr><th> Input </th><th> Type </th><th> Description </th></tr></thead><tbody><tr><td> Label </td><td> String </td><td> Title to display as activity and playbook card. </td></tr><tr><td> Description </td><td> String </td><td> Information to display about activity usage or outcome. </td></tr><tr><td> Run condition </td><td> Condition Builder </td><td> Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions.**Note:** Select **Show additional options** to see this field. </td></tr><tr><td> Start Rule </td><td> Choice </td><td> Under **Schedule** > **Start Rule**, select a start rule for when your stage should start running:- **When process starts**: Your stage starts running as soon as the playbook starts. - **After specific stages**: Your stage starts running after specified stage\(s\) have finished running. Under Schedule > Start Rule, select a start rule for when your activity should start running:- **When stage starts**: Your activity starts running as soon as its stage starts running. Your stage starts running when your playbook is triggered. - **After specific activities**: Your activity starts running after specified activities have finished running. </td></tr><tr><td> Start with delay </td><td> True/False </td><td> Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the [Start with delay input properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/start-with-delay-properties.md).**Note:** Select **Show additional options** to see this field. </td></tr><tr><td> Initial Message </td><td> String </td><td> Message text to display to end users when the activity state is In Progress. </td></tr><tr><td> Completed Message </td><td> String </td><td> Message text to display to end users when the activity state is Completed. </td></tr><tr><td> Skipped Message </td><td> String </td><td> Message text to display to end users when the activity state is Skipped. </td></tr></tbody> </table>## Advanced inputs After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select **Show additional options** to display these advanced inputs. For more information, see [Activity experience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/build-workflows/workflow-studio/activity-definitions.md). <table id="table_cjj_sr3_plb"><thead><tr><th> Input </th><th> Type </th><th> Description </th></tr></thead><tbody><tr><td> Assignment Group </td><td> Reference.Group \[sys\_user\_group\] </td><td> Group responsible for completing the task associated with the activity.**Note:** Select **Show additional options** to see this field. </td></tr><tr><td> Assigned To </td><td> Reference.User \[sys\_user\] </td><td> User responsible for completing the task associated with the activity.**Note:** Select **Show additional options** to see this field. </td></tr></tbody> </table>## Outputs These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: |Output|Type|Description| |------|----|-----------| |Record|Reference.Task\[task\]|Reference to the record associated with the activity.|
| title | Two Step Instruction activity |
| description | Display a different message to end users based on the current activity state. You can specify an initial state message, a skipped state message, and a completed state message. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/two-step-instruction-activity.html |
| release | australia |
| product | Workflow Studio |
| classification | workflow-studio |
| topic_type | reference |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Interactive activitiesPlaybooks referencePlaybooksWorkflow StudioBuild workflows |