---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Create a playbook

# Create a playbook {#ariaid-title1}

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

Create a playbook to set up an automated business process. Use Playbook builder in Workflow Studio to add stages, activities, triggers, and runtime permissions, then activate the playbook to make it available to agents and fulfillers.

## Before you begin

* Activate the Playbook application for your instance. See [Activate Playbooks](https://www.servicenow.com/docs/UbHXbn7jEOkZaN4Wi8ylWw "Activate the Workflow Studio application to create flows, playbooks, and more for any of your use cases.").
* Familiarize yourself with the tables and relationships that your application uses for the playbook that you want to create.
* Familiarize yourself with any features that your business uses to automate operations on the ServiceNow AI Platform, such as [flows](https://www.servicenow.com/docs/T7a3fbA__W0AFqe1fCEYZg "Flows automate a repeatable multi-step process. When the flow trigger conditions are met, the flow runs a sequence of reusable actions and flow logic to complete the process."), [subflows](https://www.servicenow.com/docs/M2XroYqkCUFUODPSLYrWig "Subflows automate a repeatable multi-step process that also produces an output needed by another process. When a playbook, flow, or script calls a subflow, the subflow runs a sequence of reusable actions and flow logic to complete the process and produce output values."), and [actions](https://www.servicenow.com/docs/aRtKLipkGq~lyA53_ilLhA "Actions automate a repeatable task or operation within a flow. Flows run actions by passing them data as inputs. Actions run a sequence of steps to complete the task, and pass data to the flow as outputs.").
* Role required: admin, playbook.admin, or playbook.write.
{#create-process-definition__ul_nxj_jtw_5lb}

## About this task

Use this procedure to build a new playbook from scratch. You can create a playbook with no trigger, a single trigger, or multiple triggers. If you change a playbook after activating it, the system saves your changes but deactivates the playbook. You must activate the playbook again to publish any new changes.

Fluent support for playbooks lets developers build, edit, and manage playbooks as code with the Fluent domain-specific language (DSL) in the ServiceNow IDE or a local SDK. For more information, see <https://servicenow.github.io/sdk/guides/playbook-guide>.

## Procedure

1. Navigate to AllWorkflow StudioPlaybooks.  
   The Workflow Studio landing page opens with the Playbooks list displayed by default.
2. In the upper-right corner, under New, select Playbook.
3. Fill in the following fields.  
   {#create-process-definition__table_mxp_mqm_njc__entry__2}

   | Field | Description |
   |-|-|
   | Playbook name | Unique, user-facing name for the playbook. Appears to agents and fulfillers at runtime. |
   | Application | Application scope for the playbook. Select Global to run the playbook in any application scope. |
   | Description | Descriptive details about the playbook. |
   [Table 1. Playbook fields]

   {#create-process-definition__table_mxp_mqm_njc}
4. Select Build playbook.  
   The builder displays in Diagram view by default, but you can select Board view to switch between views anytime as you build your playbook.  
   ![Diagram and Board view toggle]()  
5. Select the Start node.  
   The Playbook properties side panel opens.
6. Under the Details tab, fill in the fields.  
   You can also update the Playbook name and Description.{#create-process-definition__table_lhw_frm_njc__entry__2}

   | Field | Description |
   |-|-|
   | Limit playbook executions for each parent record to | Maximum number of times the playbook can run for a single parent record. |
   | Execution type | Type of playbook to create. * **Record driven:** Playbook tied to a record. Triggered on demand or automatically based on record operations. Data from the playbook is stored on that record. * **Standalone:** Single-session playbook that does not store data to a record. Must be manually triggered or called from another playbook. {#create-process-definition__ul_c2r_5vm_njc} |
   | Parent table | Table that provides trigger records and other playbook inputs. Required for Knowledge and Email activities. |
   | Allow this playbook to be restarted during runtime | When selected, runtime users can restart the entire playbook during a run. |
   [Table 2. Playbook properties: Details tab fields]

   {#create-process-definition__table_lhw_frm_njc}
7. Under the Inputs tab, add inputs for a playbook to launch with.  
   Inputs defined here are accessible throughout the playbook via dot-walking and dot notation, for example `inputs.inputName`, and can be used in activity fields, conditions, and UI elements.  
   Tip:  
   To trigger a playbook with API inputs instead of trigger records, use the `triggerPlaybook(String scopedName, GlideRecord parentRecord)` API to trigger a playbook. For more information about the API, search <kbd class="ph userinput">triggerplaybook</kbd> on the ServiceNow Developer Site: [Playbook Experience APIs](https://developer.servicenow.com/dev.do#!/reference/api/zurich/server/sn_playbook-namespace/PlaybookExperienceScopedAPI).
8. Under the Runtime permissions tab, configure permissions for users, user groups, user criteria, and roles.
9. Configure a trigger for the playbook.  
   You can create a playbook with no trigger, a single trigger, or multiple triggers. For more information, see [Add and configure a trigger in a playbook](https://www.servicenow.com/docs/3bfjeCLPJY74BPr00YDQJw "Begin building your playbook by adding and configuring the trigger.").
10. Add activities, stages, decision nodes, and parallel branches as required to automate your process.  
    Continue adding stages and activities until your playbook reflects the full business process. For more information, see [Stages and activities](https://www.servicenow.com/docs/rKfk_1F6UNvKpNYY2zKPag "In Playbook, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process.").
11. Preview activities to confirm the activity's appearance to end users and adjust their configuration.  
    For more information about previewing activities, see [Preview an activity's runtime UI](https://www.servicenow.com/docs/QUL8QLymUWfUbt_dTn__WA "See how an activity will appear to end users when the playbook runs. Use the preview to confirm the activity's appearance in real-time, and adjust its configuration before publishing the playbook.").
12. **Optional:** Add a variant to your playbook.  
    You can use one playbook in multiple use cases by using variants. For more information, see [Playbook variants](https://www.servicenow.com/docs/SX249U7MT53FopRYlauqoA "Use one playbook for multiple scenarios.").
13. After adding all stages and activities, test the playbook.
14. After testing the playbook, select Activate in the header.  
    The playbook is published and runs when its trigger conditions are met.

## Result

When the trigger conditions of the playbook are met, the system creates a Process Execution record and renders user-facing configurations for Playbook Experience. For an example of how to digitize a manual business process, see [Create a sample playbook](https://www.servicenow.com/docs/owHMJBg5o6XDX9thzofjKQ "Create a sample playbook to standardize and automate how Service Desk agents handle chat interactions with VIP users.").

## What to do next

Set up the Playbook Experience for your agents and fulfillers.

*[\>]: and then