---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Stages and activities

# Stages and activities {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Stages and Activities in Playbooks

In ServiceNow Playbooks,activitiesare individual steps within a broader business process, whilestagesgroup multiple activities into logical sequences aligned with your cross-enterprise workflow.
This structure enables you to design clear, stepwise playbooks that guide users through complex processes efficiently.
Show full answer Show less  

## Key Features

* **Stages:** Represent collections of sequenced activities. You can add stages via the Board or Diagram views in the design environment, helping organize your process flow logically.
* **Activities:** Represent single steps drawn from activity definitions. Activities can be added from a common list, custom applications, or automation assets. You may also create custom activity definitions if no existing activity fits your use case.
* **Activity Types:**
  * **Interactive Activities:** Require user input during playbook execution.
  * **Non-Interactive Activities:** Execute automatically without user input.
  * **Optional Activities:** Can be added on-the-fly by agents or fulfillers during run-time.
* **Configuration Details:** Each stage and activity has configurable properties such as labels, descriptions, start rules, and run conditions accessible via the side panel in the design environment.
* **Start Rules:** Define when a stage or activity begins, e.g., when the playbook starts, after specific stages or activities finish, or when a stage starts.
* **Activity Inputs \& Outputs:** Inputs provide the data needed for activities to run, which can be static or dynamically derived from prior activity outputs or record fields using dot-walking. Outputs indicate expected results after execution.
* **Automation Assets:** Subflows, flows, or actions can be integrated directly into playbooks without creating new activity definitions, streamlining automation inclusion.
* **Advanced Features:** Support for decision branches, optional activities, parallel branches, and dynamic input configurations based on other fields or API responses.
* **State Management:** Use existing ServiceNow AI Platform state models to align playbook design with the lifecycle of related record types. Activity state mapping allows overriding playbook card statuses for better tracking.
* **Design Considerations:** Include timing controls like delay inputs to manage when activities or stages run, allowing for user action time or scheduled waits.

## Practical Benefits for ServiceNow Customers

By structuring complex workflows into stages and activities, ServiceNow customers can create clear, adaptable playbooks that guide agents and fulfillers through processes with precision and flexibility. The ability to mix interactive and automated steps, insert optional activities, and configure dynamic inputs ensures playbooks can be tailored to real-world operational needs. Leveraging automation assets and state models reduces development effort and aligns playbook execution with existing process states, enhancing consistency and efficiency across the enterprise.  
In Playbooks, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process.

## Stages {#process-automation-designer-lanes-activities__section_kwx_fxy_qlb}

Group activities by the stages of your business process, and sequence activities in an order that makes sense for your cross-enterprise workflow. A stage is made up of many sequenced activities that are grouped in a logical way. In the Playbooks Board view of the design environment, you can add a stage to your playbook by clicking + Add stage. In the Diagram view, select the + icon on connectors (lines) to add a stage.

## Activities {#process-automation-designer-lanes-activities__section_h3n_5rj_skb}

In Playbooks, an activity represents one step in your overall business
process. In the system, an activity is one instance of an activity definition. For more
information on activity instances and activity definitions, see the [Playbooks User Experience](https://www.servicenow.com/docs/Gg~G15WxNdRVZr4MJWUwnQ "Understand how Workflow Studio Playbooks work in the ServiceNow AI Platform to automate cross-functional processes and consolidate them into task-oriented views for your end users.") and [activity definitions](https://www.servicenow.com/docs/r014Lhz_11xoMRZZRHOzcA "Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.").

## Adding an activity to your playbook {#process-automation-designer-lanes-activities__adding-an-activity}

In the Playbooks Board view of the design environment, select + Add activity to open the activity picker. In the Diagram view, select the + icon on connectors
(lines) to open the activity picker. In the activity picker, you can search for an activity to add or select one from the list of Common Activities. To choose an activity for a custom application, first select the application and then select the activity from the resulting list within the picker.

Additionally, you can add an activity just using an [automation asset](https://www.servicenow.com/docs/mU389THCpCX6TcjWJLTNJg "Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.").

If there isn't an activity that fits your use case, you can create your own activity definition to add to the activity picker. For more information, see [create an activity definition](https://www.servicenow.com/docs/txabHiyOd98TDVW_VnbpsQ "Specify the action or subflow you want an activity to run. Configure the inputs you want playbook designers to set when adding the activity to a playbook. Select the experience you want end users to have when the activity runs.").

## Interactive and Non-Interactive activities {#process-automation-designer-lanes-activities__section_mk3_p4z_qlb}

Activity categories include:

Interactive Activities
:   When an interactive activity runs, it prompts a user for input in your playbook as it runs. For more information, see [Interactive activities](https://www.servicenow.com/docs/R8QtDzc0EgkEXDYSWFYvdA "An interactive activity prompts a user for input in your playbook as it runs.").

Non-Interactive Activities
:   When a non-interactive activity runs, it runs entirely behind-the-scenes and requires no user input. For more information, see [Non-Interactive activities](https://www.servicenow.com/docs/KWf8zLLEtOk8LLsWS_DKLA "A non-interactive activity runs entirely behind-the-scenes on the ServiceNow AI Platform and doesn't require any user input.").

Optional Activities
:   An optional activity can be inserted by agents and fulfillers during a playbook run. For more information, see [Optional activities](https://www.servicenow.com/docs/pJEY3EDh5wh5XlpPOIG19Q#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.").

## Stage and activity details {#process-automation-designer-lanes-activities__lane-activity-properties}

When you select an activity, the side panel should open. Under the Details tab of the side panel, you can add names, descriptions, and start rules to the stages and activities in your playbook. Click the show or hide additional options button to show or hide additional properties for your currently selected stage or activity. The basic details for each stage and activity
include:  

Label
:   You can enter a display name for your stage or activity. This name appears during playbook runtime.  
    Note:  
    Keep your stage and activity names brief, as the system truncates long names.

Description
:   Optionally, enter a description for your activity or stage. This description only appears within Playbooks and isn't visible during playbook runtime.

Start Rule
:   Under ScheduleStart 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.
    {#process-automation-designer-lanes-activities__ul_mnz_mwd_xkb}
:   Under ScheduleStart 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.
    {#process-automation-designer-lanes-activities__ul_ww5_ydq_sxb}

Run condition
:   Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions.

## Activity inputs {#process-automation-designer-lanes-activities__section_b5m_mm1_rlb}

Under the Automation tab of the side panel, each activity has inputs you can configure:

* To change default inputs and outputs for the activity, open and edit the source flow in Workflow Studio by selecting the Open link icon (![Open link icon]()) next to the Automation field.

  For more information on how to work with the default inputs and outputs for activities in Playbooks, see [Create an action as an activity automation plan](https://www.servicenow.com/docs/dz8QkxMWJZbWW9UhBM6vvQ "Create an example action to configure and run as an activity from Playbooks.").  
  Note:  
  You must have the appropriate user roles to access Workflow Studio and Workflow Studio. For more information, see [User access to Workflow Studio flows](https://www.servicenow.com/docs/GYXUUfIquOaOYZYuLzS2rQ "Administrators can grant users access to Workflow Studio flows by assigning delegated development permissions or directly assigning a user role. Administrators can also specify which features and content a user can access based on user roles. Application developers can access Workflow Studio functionality through APIs for flows, subflows, and actions.").
* Inputs are data that you provide so that the activity runs and performs its function appropriately. For example, a Record activity that notifies a customer of an application rejection will have message inputs for the email address, subject, body, and more.
* Expected Outputs are displayed at the bottom of the Automation tab.
{#process-automation-designer-lanes-activities__ul_kpv_3mq_sxb}

## Creating static and dynamic values for activity inputs {#process-automation-designer-lanes-activities__section_xqq_khh_rlb}

You can add dynamic data to an activity input. Click the data pill picker icon (![Data pill picker icon]()) and navigate, or dot-walk, to the data pill whose dynamic value you want to use when your activity runs. You can select dynamic data from fields in the input record. If your activity has a start rule of
After specific activities, you can also select dynamic data from the outputs of other activities in your playbook. For more information on dot-walking to related fields and records on the ServiceNow AI Platform, see [selecting fields on related tables using dot-walking](https://www.servicenow.com/docs/access?context=c_DotWalking&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US).  
Note:  
You can dot-walk to fields in a Reference but not in a Document ID or Sys ID.

The inputs for interactive activities typically provide data that renders in a playbook for an agent to interact with. The inputs for non-interactive activities can render in a playbook but don't require any user input in order
to run. For more information, see [Interactive activities](https://www.servicenow.com/docs/R8QtDzc0EgkEXDYSWFYvdA "An interactive activity prompts a user for input in your playbook as it runs.") and [Non-Interactive activities](https://www.servicenow.com/docs/KWf8zLLEtOk8LLsWS_DKLA "A non-interactive activity runs entirely behind-the-scenes on the ServiceNow AI Platform and doesn't require any user input.").

## Design considerations {#process-automation-designer-lanes-activities__section_zfx_vhk_zkb}

Refer to these design considerations when working with stages and activities:

Keep ServiceNow AI Platform state models in mind when designing your playbook
:   Some record types already have state models that describe their life cycle. Use any existing state model as a template for the design of your playbook. For more information, see [State Management](https://www.servicenow.com/docs/access?context=state-model&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).
* **[Add and configure a stage in a playbook](https://www.servicenow.com/docs/Vk3iDYyg_Df62zD4oj~nDQ)**   
  Add and configure a stage in your playbook.
* **[Activity definitions](https://www.servicenow.com/docs/r014Lhz_11xoMRZZRHOzcA)**   
  Activity definitions describe how the activities in your playbook get the data that they need when your playbook runs.
* **[Add and configure an activity in a playbook](https://www.servicenow.com/docs/eH66_4Re8HXK8adZ1kzWiw)**   
  Add and configure an activity in your playbook.
* **[Automation Assets](https://www.servicenow.com/docs/mU389THCpCX6TcjWJLTNJg)**   
  Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.
* **[Start with delay input properties](https://www.servicenow.com/docs/ZO5_TxRewwK7XqnX5otC7A)**   
  Specify a duration of time to wait before running an activity or a stage whose start rule and conditions have been met. Give users time to act during automated playbooks. Give users time to wait for a specific date and time to complete actions.
* **[Optional activities](https://www.servicenow.com/docs/pJEY3EDh5wh5XlpPOIG19Q#optional-activities)**   
  Enable your agents and fulfillers to add additional activities as they go through a playbook.
* **[Decision activities](https://www.servicenow.com/docs/4rX5cqI_FXRlYNq~tfDHiQ)**   
  Create and define branches with different conditions for different paths that an agent can follow in playbook.
* **[Questionnaire activity](https://www.servicenow.com/docs/0Zhk1Qtvq62no8BNvPsGbQ)**   
  Collects inputs from a user during a playbook run to use later in the playbook.
* **[Parallel branches](https://www.servicenow.com/docs/PNev5QskKuGUAmoIHUw0fQ)**   
  Add branches for activities and stages that run in parallel to another branch of activities and stages.
* **[Add dynamic inputs to an activity](https://www.servicenow.com/docs/8XnLc2y4MM0hKIntwpZR5A)**   
  Configure your activity to show a certain set of fields based on the value of another input, such as a selected catalog item, selected decision table, or even a REST API response.
* **[Playbook activity state mapping](https://www.servicenow.com/docs/fmXbaKoPUaBr1Y8dpLJFYA)**   
  Use playbook activity state mapping to override the status of a playbook card.

*[\>]: and then