--- sourceDocument: Zurich Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/build-workflows Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Checklist Task activity # Checklist Task activity {#ariaid-title1} * Release version: Zurich * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Checklist Task Activity The Checklist Task activity enables agents to complete all items in a task checklist efficiently. Key inputs include the Checklist Owner, Checklist Items, and Checklist Name, which are essential for configuring the activity within a playbook. This activity is designed for users with specific roles, such as admin and playbook.admin, allowing them to incorporate it into their playbooks seamlessly. Show full answer Show less ## Key Features * **Activity Configuration:** Users can configure the activity properties panel to set values for various inputs, including label, description, run conditions, and start rules. * **Start Rules:** Customize when the checklist activity begins, either upon stage or playbook initiation, or after specific activities/stages. * **Skip Options:** Define groups or users who can skip the checklist activity if enabled. * **Checklist Ownership:** Assign a user as the checklist owner and customize checklist items and names for clarity. * **Task Association:** Link the checklist to a specific task record, ensuring it is displayed within the associated task. * **SLA Visibility:** Optionally show SLA countdown details to monitor task timelines. ## Key Outcomes By utilizing the Checklist Task activity, ServiceNow customers can ensure that agents follow through on all checklist items, enhancing task completion tracking and accountability within their workflows. This structured approach improves operational efficiency and helps maintain clarity in task management. Prompt an agent to complete all items in a task checklist. The key inputs for this activity are the Checklist Owner, Checklist Items, and Checklist Name fields under the [Inputs](https://www.servicenow.com/docs/~WqXqRLGME7lKpf3P4dIQg#checklist-task-activity__table_cjj_sr3_plb) section. ## Roles and availability {#checklist-task-activity__section_pwq_rb5_kcb} This activity is available as a common activity. Users with the admin, playbook.admin, or pd_author can add this activity to a playbook. ## Common properties {#checklist-task-activity__section_yb4_zq3_plb} These properties are common to all to activities in Playbooks. 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 [Dot-walking examples](https://www.servicenow.com/docs/access?context=dot-walking-examples&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US). {#checklist-task-activity__table_ajt_sr3_plb__entry__3} | 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 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. {#checklist-task-activity__ul_f4z_nq1_ppb}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. {#checklist-task-activity__ul_zzc_3ls_m1c} | | 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](https://www.servicenow.com/docs/0bU5ECLrTgx0LIrj6BCf~w "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."). Note: Select Show additional options to see this field. | [ ] {#checklist-task-activity__table_ajt_sr3_plb} ## Inputs {#checklist-task-activity__section_bgh_1r3_plb} 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://www.servicenow.com/docs/hC2JPXxYVpwMpyvSURl_5w#activity-definitions__activity-experience). {#checklist-task-activity__table_cjj_sr3_plb__entry__3} | Input | Type | Description | |-|-|-| | Skip Assignment Group | Reference.Group \[sys_user_group\] | Group that is allowed to skip this activity when Can Skip is enabled. Note: If Can Skip is enabled, and you do not specify a Skip Assignment Groupor Skip Assigned To, all users will be able to skip this activity. | | Skip Assigned To | Reference.User \[sys_user\] | User that is allowed to skip this activity when Can Skip is enabled. Note: If Can Skip is enabled, and you do not specify a Skip Assignment Groupor Skip Assigned To, all users will be able to skip this activity. | | Checklist Owner | Reference.User \[sys_user\] | The user who owns this checklist. | | Checklist Items | String | The items you want display in your checklist. | | Checklist Name | String | The name to display for the checklist. | | Task | Reference.Task \[task\] | Reference a record to associate with the checklist activity. The checklist is also displayed in the associated task record. Note: When a specific task record is associated with the checklist, the state of the checklist does not change if you run the playbook again. When you don't provide a specific task record, a new private task record is created for each run.

| | Show SLA | True/False | Option to show SLA countdown details for the task. Note: Select Show additional options to see this field. | | Can Skip | True/False | Option to allow agents to skip the checklist and to continue through the playbook. | [ ] {#checklist-task-activity__table_cjj_sr3_plb} ## Additional properties {#checklist-task-activity__section_l44_5dy_m1c} Move stuff here. ## Outputs {#checklist-task-activity__section_unx_fr3_plb} These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity: {#checklist-task-activity__table_mv2_rr3_plb__entry__3} | Output | Type | Description | |-|-|-| | Checklist Task | Reference.Task \[task\] | Task record that updates when this activity completes. | [ ] {#checklist-task-activity__table_mv2_rr3_plb} ## UI Layouts {#checklist-task-activity__id_xrs_lww_41c} Set properties for how the activity renders during a playbook run. *[\>]: and then