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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Automated Update Record activity

# Automated Update Record activity {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Update a record without pausing the playbook to ask for user input. When the activity
runs, it immediately updates the record and continues to the next activity in the playbook. The
record must meet server-side validation rules such as data policies, business rules and
dictionary-defined mandatory fields but ignores UI policies.

## Roles and availability {#automated-update-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.
{#automated-update-record-activity__ul_mcq_1c5_kcb}

## Inputs {#automated-update-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=australia&pubname=australia-platform-user-interface&ft:locale=en-US). {#automated-update-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: 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. {#automated-update-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. {#automated-update-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/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."). Note: Select Show additional options to see this field. |
| Record | Reference | Reference to the record you want to update. |
| Table | Table Name | Table containing the record to update. |
| Fields | Template Value | Field values to change during record update. |
[ ]

{#automated-update-record-activity__table_ajt_sr3_plb}

## Outputs {#automated-update-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: {#automated-update-record-activity__table_mv2_rr3_plb__entry__3}

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

{#automated-update-record-activity__table_mv2_rr3_plb}

*[\>]: and then