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


---

# Create an action as an activity automation plan

# Create an action as an activity automation plan {#ariaid-title1}

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

Create an example action to configure and run as an activity from Playbooks.

## Before you begin

Role required:

* This task requires some knowledge of creating flows in Workflow Studio environment. For more information, see [Building flows](https://servicenow-prod.fluidtopics.net/rdjXjcHvTmif13bwuZtdtg "Workflow Studio is the default ServiceNow AI Platform process automation builder used to create flows. Workflow Studio replaces the Workflow Editor.").
* This task requires some knowledge of server-side scripting. For more information, see [Server-side
  scripting](https://www.servicenow.com/docs/access?context=c_ServerScripting&version=australia&pubname=australia-api-reference&ft:locale=en-US).
* admin
{#create-automation-plan__ul_npb_y3m_vlb}

## About this task

Each activity definition requires an automation plan to run Workflow Studio content. The automation plan tells the Workflow Studio Playbooks builder what input values to use when running an action or
subflow. An automation plan can specify static default values or can prompt playbook
owners to provide dynamic values when they add an activity to a playbook.

In this example, you create a reusable Workflow Studio action to use as
an activity's automation plan. The action you create associates a Task \[task\] record
with a parent record.

## Procedure

1. Navigate to AllProcess AutomationFlow Designer.
2. In the main header, click + NewAction.  
   The Action Properties screen appears.
3. In the Action Properties screen, fill in the following fields:  
   {#create-automation-plan__table_mqd_d1t_xlb__entry__2}

   | Field | Action |
   |-|-|
   | Name | Enter <kbd class="ph userinput">Associate Record with Parent</kbd>. |
   | Application | Leave Global selected. |
   | Accessible From | Leave All application scopes selected. |
   [ ]

   {#create-automation-plan__table_mqd_d1t_xlb}
4. Click Submit.  
   The Workflow Studio design environment appears.
5. Under the Action Outline, click Inputs.
6. In the Action Input header, click + Create Input, and then fill in the following fields:  
   {#create-automation-plan__table_h3z_xbt_xlb__entry__2}

   | Field | Action |
   |-|-|
   | Label | Enter <kbd class="ph userinput">Record</kbd>. |
   | Name | Enter <kbd class="ph userinput">record</kbd>. |
   | Type | Select Reference.Task\[task\] |
   [ ]

   {#create-automation-plan__table_h3z_xbt_xlb}
7. In the Action Input header, click + Create Input, and then fill in the following fields:  
   {#create-automation-plan__table_zlk_2ct_xlb__entry__2}

   | Field | Description |
   |-|-|
   | Label | Enter <kbd class="ph userinput">Parent Record</kbd>. |
   | Name | Enter <kbd class="ph userinput">record</kbd>. |
   | Type | Select Reference.Task\[task\] |
   [ ]

   {#create-automation-plan__table_zlk_2ct_xlb}
8. Click the add a new step icon (![Add a new step icon]()).  
   The Select Step to add screen appears.
9. Under ServiceNow Data, select the Update Record step.  
   The Update Record step appears in the Action Outline under Inputs.
10. In the Record field, click the data pill picker icon (![Data pill picker icon]()), and then dot-walk to InputsRecord.
11. Under Field Values, click +Add Field Value, and then select Parent from the list.
12. Next to the Parent field, click the data pill picker icon (![Data pill picker icon]()), and then dot-walk to InputsParent Record.
13. Under the Action Outline, click Outputs.
14. Under Action Output, click + Create Output, and then fill in the following fields:  
    {#create-automation-plan__entry__26}

    | Field | Action |
    |-|-|
    | Label | Enter <kbd class="ph userinput">Record</kbd>. |
    | Name | Enter <kbd class="ph userinput">record</kbd>. |
    | Type | Select Reference.Task\[task\] |
    [ ]

15. In the Action Output header, click + Create Output, and then fill in the following fields:  
    {#create-automation-plan__table_zx4_f2t_xlb__entry__2}

    | Field | Action |
    |-|-|
    | Label | Enter <kbd class="ph userinput">Parent Record</kbd>. |
    | Name | Enter <kbd class="ph userinput">record</kbd>. |
    | Type | Select Reference.Task\[task\] |
    [ ]

    {#create-automation-plan__table_zx4_f2t_xlb}
16. In the Action Output header, click Exit Edit Mode.
17. Next to the Record output's Value column, click the data pill picker icon (![Data pill picker icon]()), and then dot-walk to InputsRecord
18. Next to the Parent Record output's Value column, click the data pill picker icon (![Data pill picker icon]()), and then dot-walk to InputsParent Record.
19. In the main header, click SavePublish to make your action available to add to an activity definition's automation plan.

## Result

You can now add your custom Workflow Studio action to an automation plan for your custom activity definition.

## What to do next

Add your custom action to an automation plan when you [Create an activity definition](https://servicenow-prod.fluidtopics.net/YKo~qF7plLOp9f6SFvnhRg "Specify the action or subflow you want an activity to run. Configure the inputs you want playbook designers to set when adding the activity to a playbook. Select the experience you want end users to have when the activity runs.").
**Related concepts**   

* [UI Layouts](https://servicenow-prod.fluidtopics.net/2aQht1gdhm2cRy7lrUDwNQ "A UI Layout describes what properties and components to use when an activity renders as a card in a Playbook Experience.")  
**Related tasks**   

* [Create an activity definition](https://servicenow-prod.fluidtopics.net/YKo~qF7plLOp9f6SFvnhRg "Specify the action or subflow you want an activity to run. Configure the inputs you want playbook designers to set when adding the activity to a playbook. Select the experience you want end users to have when the activity runs.")

*[\>]: and then