---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Create Task activity

# Create Task activity {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 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 Create Task activity

The Create Task activity in ServiceNow enables you to create a task record from previously gathered or generated data within a playbook.
This activity is available to users with admin, playbook.admin, or pdauthor roles and can be added as a common activity to any playbook.
Show full answer Show less  

## Configuration Inputs

When setting up the Create Task activity, you configure various inputs through the activity properties panel:

* **Label and Description:** Define the title and informational text shown on the activity and playbook card.
* **Run Condition:** Set conditions based on prior activity data that must be met to execute the activity.
* **Start Rule:** Choose when the activity or stage starts running, either immediately on playbook or stage start, or after specific activities or stages finish.
* **Start with delay:** Optionally delay the start of the activity or stage.
* **Assigned To:** Specify the user responsible for completing the created task.
* **Short Description:** Provide a summary of the task to be completed.
* **Wait for user input:** Optionally pause the playbook until the end user manually completes or skips the activity; editable only by playbook.admin role.

## Advanced Inputs

Additional configurations enhance control over task assignment and behavior:

* **Assignment Group for this Process Step:** Define the group allowed to perform the activity. If omitted along with Assigned To, any user can view and edit the data.
* **Assigned to this Process Step:** Specify individual users allowed to perform the activity, independent of the group.
* By default, Assignment Group and Assigned To fields map to the trigger record's respective fields, ensuring assigned users have access to the task data.
* **Task Table:** Select the task table extension where the new task record will be created.
* **Field values:** Define specific fields and values to set on the new task record.
* **Fields to show after creation:** List fields to display on the created task record.
* **Wait for Task completion:** Optionally pause the playbook until the created task is completed.

## Outputs

The activity produces outputs that can be leveraged by subsequent playbook activities:

* **Table:** Returns the name of the table containing the new task record.
* **Record:** Provides a reference to the newly created task record.

## Practical Benefits

This activity streamlines task creation within automated playbooks, assigning responsibility clearly, and allowing flexible execution conditions and pause options. It ensures that tasks are created with appropriate details and ownership, and that playbooks can wait for task completion or user input, enhancing process control and coordination.  
Create a task record from previously gathered or generated data.

## Roles and availability {#create-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.

## Inputs {#create-task-activity__section_yb4_zq3_plb}

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=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). {#create-task-activity__table_ajt_sr3_plb__entry__3}{#create-task-activity__wait-process}

| 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: 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. {#create-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. {#create-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://servicenow-prod.fluidtopics.net/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."). Note: Show additional options to see this field. |
| Assigned To | Reference.User \[sys_user\] | User responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
| Short Description | String | Summary of the task to complete. |
| Wait for user input | Choice | Option to pause the playbook until the end user manually completes or skips the activity. Only users with the playbook.admin role can edit this field. By default, the activity waits for user action or data before it completes. |
[ ]

{#create-task-activity__table_ajt_sr3_plb}

## Advanced inputs {#create-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://servicenow-prod.fluidtopics.net/r014Lhz_11xoMRZZRHOzcA#activity-definitions__activity-experience). {#create-task-activity__table_cjj_sr3_plb__entry__3}

| Input | Type | Description |
|-|-|-|
| Assignment Group for this Process Step | Reference.Group \[sys_user_group\] | Assignment group allowed to perform this playbook activity. If you don't set any values for Assignment Group or Assigned To, any user can read and edit the collected data. The Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the Assigned To field. The same users do not need to be specified in both fields. Note: By default, these fields are mapped to the Assignment Group and Assigned To fields of the trigger record. This means that users assigned to work on the parent record have access to submit, view and edit the collected data by default. |
| Assigned to this Process Step | Reference.User \[sys_user\] | User allowed to perform this playbook activity. If you don't set any values for Assignment Group or Assigned To, any user can read and edit the collected data. The Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the Assigned To field. The same users do not need to be specified in both fields. Note: By default, these fields are mapped to the Assignment Group and Assigned To fields of the trigger record. This means that users assigned to work on the parent record have access to submit, view and edit the collected data by default. |
| Task Table | Table Name | Name of the task table extension in which you want to create a task. The activity completes when this task is complete. |
| Field values | Choice | The field that you want to add to your task. |
| Add Field | Template Value | Field values to assign when creating the task record. |
| Fields to show after creation | String | Comma-separated list of fields to display for a created record. |
| Wait for Task completion | True/False | Pause the playbook until the created Task record is complete. |
[ ]

{#create-task-activity__table_cjj_sr3_plb}

## Outputs {#create-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: {#create-task-activity__table_mv2_rr3_plb__entry__3}

| Output | Type | Description |
|-|-|-|
| Table | Table Name | Table containing new record. |
| Record | Reference.Task\[task\] | Reference to record created. |
[ ]

{#create-task-activity__table_mv2_rr3_plb}

*[\>]: and then