--- sourceDocument: Australia Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Add and configure an activity in a playbook # Add and configure an activity in a playbook {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Add and configure an activity in your playbook. ## Before you begin Role required: playbook.admin or pd_author Review [Stages and activities](https://www.servicenow.com/docs/rKfk_1F6UNvKpNYY2zKPag "In Playbook, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process."). ## Procedure 1. Add an activity. | View | Steps | | Diagram | 1. Select the + icon in the first stage. 2. In the mini-picker, select the square icon ![Square activity icon in Diagram view mini-picker.]() to add an activity. 3. In the activity picker, search for an activity to add. Note: Select the application first, and then the activity from the resulting list. {#add-configure-activity__ol_fln_kmv_21c} | | Board | 1. Select + Add activity in the first stage. 2. In the activity picker, search for an activity to add. Note: Select the application first, and then the activity from the resulting list. {#add-configure-activity__ol_w35_j5v_21c} | |-|-| {#add-configure-activity__choicetable_e2d_3mv_21c} Your new activity appears in the stage, and the Activity properties panel appears. 2. Under the Details tab, fill in the details of your activity. 1. Provide the basic details of the activity. |-|-| | Label | Enter a unique, user-facing name for your activity. This name appears to agents and fulfillers during runtime of your playbook. | | Description | Optionally, enter some descriptive details about your activity. | | Start Rule | Choose when you want your activity to start running. Options include: * 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. {#add-configure-activity__ul_y5d_dnv_21c} | [Table 1. Required inputs] {#add-configure-activity__table_lwk_5mv_21c} {#add-configure-activity__substeps_dxs_rmv_21c} 1. **Optional:** Show additional options the activity for [even more granular control](https://www.servicenow.com/docs/8nWqSR4oExewiXrZPYPXFg "Display detailed instructions to guide end users through your playbook."). Warning: Changing the advanced property fields of an activity can potentially break your automation. Make sure you understand how the playbook and its activities flow before you make changes. {#add-configure-activity__substeps_y51_mqs_d1c} | Option | Description | | Display order | Define the order in which this activity will appear during a playbook run. | | Run condition | After the activity starts, the activity runs only if specific conditions are met. | | Start with delay | Specify a duration of time to wait before running an activity whose start rule and conditions have been met. For more information, see [Start with delay input properties](https://www.servicenow.com/docs/EdInaaLAHZCnrBcJbs96Lw "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."). | | Restart rules | Choose what this activity does when a playbook is restarted: * Skip on restart: Skip this activity when the run is due to a restart. * Run always: Always run this activity, including first runs. * Skip on first run: Skip this activity during the first run. {#add-configure-activity__ul_tfw_wxr_rzb}For more information, see [Configure restart for Playbooks](https://www.servicenow.com/docs/fDTysgsDrbJu17~DEIy2tg "Configure restart so that agents and fulfillers in Playbook Experience can restart a playbook from the beginning, or from a specific stage or activity."). | |-|-| {#add-configure-activity__choicetable_n4l_ydt_vlb} 3. Open the Automation tab. Automation, inputs, and outputs sections appear. Automation : See or open the action, subflow, or flow that drives the activity. Inputs : Configure inputs for the action, subflow, or flow that is driving the activity. Not all activities require user input. Outputs : Outputs of the action, subflow, or flow that is driving the activity. 4. Under the Inputs section, define the values of the activity's inputs. Configure inputs with a hardcoded value, or by [dot-walking to a data pill](https://www.servicenow.com/docs/access?context=c_DotWalking&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US) (![Data pill picker icon]()) to use data from previous activities, the playbook trigger, from the playbook parent table, or from the playbook inputs. Tip: You can use both text and multiple pills in any other rich text or HTML input fields. 5. Open the UI Layout tab. Depending on the UI Layout associated with the activity, different sections and fields appear under the activity definition's Activity Experience. These sections and fields let you set up the activity data that renders during the runtime Playbook Experience. Note: All UI Layouts, except for Record generator, display an Associated Record section. For information on how to set up or edit the Associated Record section in an activity definition, see [Create an activity definition](https://www.servicenow.com/docs/YKo~qF7plLOp9f6SFvnhRg "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."). 6. **Optional:** Specify if an AI Agent performs the activity, and how. To learn more, see [Configuring Agentic Playbooks](https://www.servicenow.com/docs/9TEM76VbAOC6~vBGpHFzZg "As a playbook author in Workflow Studio, configure AI Agents to perform a playbook activity."). 7. Click Save and close to save the details of your activity. At any point while in the Playbooks builder, you can add more activities to a stage as described in the previous steps. 8. **Optional:** If the activity you want to add is not in the activity picker, create the activity definition. 1. Under your stage, click + Add activity. The activity picker appears. 2. Click the Create a new activity button. 3. Fill in the following fields. {#add-configure-activity__substeps_lbn_npb_g5b} | Option | Description | | Label | Enter a unique, user-facing name for your activity. This name appears to agents and fulfillers during runtime of your playbook. | | Accessible From | Where the activity is accessible from. Make the activity accessible to other applications by setting the Accessible from field to All application scopes. Restrict access by setting the field to This Application Scope Only. | | Table | Optionally, set to the table associated with the activity. | | Application | Read-only field that indicates which applications can use this activity. | | Description | Optionally, enter some descriptive details about your activity. | | Automation Plan | Select the subflow or action that you want to use to automate your activity. | | Activity Experience | Optionally, set the activity's experience type, which helps to define how the activity renders in user-facing views of a playbook card at runtime. | |-|-| {#add-configure-activity__choicetable_cf4_jqb_g5b} 9. Click Submit to finish creating your activity definition. Your activity is defined. ## What to do next Set up the Playbook Experience for you agents and fulfillers.