---
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 Record activity

# Create Record activity {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Record activity

The Create Record activity in ServiceNow Yokohama release enables you to pause a playbook and prompt the end user to create a record through a specified form view.
This activity is designed to facilitate interactive record creation by configuring the target table and form view presented to the user during the playbook execution.
Show full answer Show less  

## Key Features

* **Role and availability:** Available as a common activity; users with `admin`, `playbook.admin`, or `pdauthor` roles can add it to playbooks.
* **Configurable inputs:** Set the activity's label, description, run conditions based on prior data, and scheduling rules (start rules and delays).
* **Table and form view selection:** Specify the target table for the new record and the form view used for record creation. If a form view is not specified, the default view is used. Form views can be edited or created using Form Builder within Workflow Studio.
* **Template fields:** Predefine field values to populate during record creation for user convenience and consistency.
* **Outputs:** After record creation, the activity outputs include the table name, form view used, and the unique Sys ID of the newly created record. These outputs can be used as inputs for subsequent activities in the playbook.

## Design considerations

* Create tailored form views that display only necessary fields, focusing on required fields or those validated by business logic, to streamline user input during playbook execution.
* Since Create Record is an interactive activity and requires user input, it can block dependent activities from starting. To avoid blocking, design playbooks to execute non-interactive activities before any interactive Create Record activities.  
Pause the playbook and prompt the end user to create a record in a form view. Use this activity to allow the end user to create a
record. This activity requires you to configure the desired table for which record to create, and the desired form view that the end user will see when creating the record.

## Roles and availability {#create-record-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-record-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-record-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: 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-record-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-record-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. |
| Table | Table Name | Table in which to insert new record. |
| Create Record View | String | Form view to use for record creation. If you don't provide a form view, the system uses the default view. Use the new tab button ![a button that opens a new tab]()to open and edit a form view with Form Builder in a new Workflow Studio tab. Note: Many form views are not supported in Workspace. |
| Template Fields | Template Value | Field values to set during record creation. |
[ ]

{#create-record-activity__table_ajt_sr3_plb}

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

| Output | Type | Description |
|-|-|-|
| Table | Table Name | Table containing new record. |
| Create Record View | String | Form view used for record creation. |
| Record Created | Sys ID | Unique identifier of the record that this activity created. |
[ ]

{#create-record-activity__table_mv2_rr3_plb}

## Design considerations {#create-record-activity__section_td2_fr3_plb}

Create form views for activities that you want to render in a playbook during runtime.
:   Use a form view to display only the fields your users need to create a record. Your view should display required fields or those fields validated by other business logic. See [View Management](https://www.servicenow.com/docs/access?context=view-management-overview&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US).

Run non-interactive activities before interactive activities
:   While a Create Record activity interactively gathers data from users, it prevents the playbook from starting any dependent activities. For example, a Create Record activity would prevent starting After Previous activities, which may be in other stages. Where possible, design your playbooks to run non-interactive activities before interactive activities that could block them.

*[\>]: and then