--- title: Create Task activity description: Create a task record from previously gathered or generated data. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/create-task-activity.html release: australia product: Workflow Studio classification: workflow-studio topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Playbooks reference, Playbooks, Workflow Studio, Build workflows] --- # Create Task activity Create a task record from previously gathered or generated data. ## 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 [Dot-walking examples](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/dot-walking-examples.md).
| 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. - **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. |
| 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://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. |
| 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. |
| 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. |
| 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. |