--- 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 a playbook # Create a playbook {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Enable playbook owners to configure and organize multiple instances of Workflow Studio content into an automated business process on the ServiceNow AI Platform®. ## Before you begin * [Activate playbooks](https://servicenow-prod.fluidtopics.net/WGnuOOfoRkRoInZNrUgJ2Q#activate-process-automation-designer "Activate the Workflow Studio application to create flows, playbooks, and more for any of your use cases.") for your appropriate application. * Familiarize yourself with the tables and relationships that your application uses for the playbook that you want to create. * Make sure to familiarize yourself with any features that your business uses to automate operations on the ServiceNow AI Platform, such as [flows](https://servicenow-prod.fluidtopics.net/MZ8lCO1cEtmajyF9Lm~DJA "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://servicenow-prod.fluidtopics.net/RuDk1UQNCznz2WVPyuKK7w "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://servicenow-prod.fluidtopics.net/h1Pr8891nD96A6Bu67wsaw "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."). * Learn how to [get started with ServiceNow® Process Automation](https://servicenow-prod.fluidtopics.net/nQsD7bvzN_P1NilfxA~gkg "Learn how Process Automation applications can help you use the ServiceNow AI Platform to transform your manual business processes into digitized, automated workflows."). * Role required: admin, playbook.admin, or playbook.write. {#create-process-definition__ul_nxj_jtw_5lb} ## About this task ## Procedure 1. Navigate to AllWorkflow StudioPlaybooks. The Workflow Studio landing page appears. Playbooks are shown by default, but you can toggle to flows, subflows, actions, and decisions. 2. In the upper right corner, click New and select Playbook from the drop-down menu. The Playbooks builder details screen for a new playbook opens in a new tab. 3. Fill in the following fields. | Field | Action | | Playbook name | Enter a unique, user-facing name for your playbook. This name appears to agents and fulfillers during runtime of your playbook. | | Description | Optionally, enter some descriptive details about your playbook. | | Application | Choose an application scope that you want your playbook to run in. Selecting Global lets your playbook run in any application scope. For more information, see [Application scope](https://www.servicenow.com/docs/access?context=c_ApplicationScope&version=yokohama&pubname=yokohama-application-development&ft:locale=en-US). | |-|-| {#create-process-definition__choicetable_ndc_pgy_5lb} The builder displays in Diagram view by default, but you can select Board view to switch views. Switch between views anytime as you build your playbook. 4. [Configure your trigger.](https://servicenow-prod.fluidtopics.net/4iDfe4VOXmhPSU_7SaQ0AA "Begin building your playbook by adding and configuring the trigger.") 5. [Add a stage.](https://servicenow-prod.fluidtopics.net/Vk3iDYyg_Df62zD4oj~nDQ "Add and configure a stage in your playbook.") 6. [Add an activity.](https://servicenow-prod.fluidtopics.net/eH66_4Re8HXK8adZ1kzWiw "Add and configure an activity in your playbook.") 7. Keep adding stages and activities according to your manual playbook. For an example of how to design an entire digitized process with Playbooks, see [Create a sample playbook](https://servicenow-prod.fluidtopics.net/OynyzdxYrLI2quKA_FNsJg "Create a sample playbook to standardize and automate how Service Desk agents handle chat interactions with VIP users."). 8. **Optional:** If you don't see the activity you need to add in the activity picker, [create an activity definition](https://servicenow-prod.fluidtopics.net/txabHiyOd98TDVW_VnbpsQ "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."). 9. **Optional:** [Add a decision activity.](https://servicenow-prod.fluidtopics.net/4rX5cqI_FXRlYNq~tfDHiQ "Create and define branches with different conditions for different paths that an agent can follow in playbook.") 10. **Optional:** [Add parallel activities.](https://servicenow-prod.fluidtopics.net/PNev5QskKuGUAmoIHUw0fQ "Add branches for activities and stages that run in parallel to another branch of activities and stages.") 11. **Optional:** [Add optional activities.](https://servicenow-prod.fluidtopics.net/pJEY3EDh5wh5XlpPOIG19Q#optional-activities "Enable your agents and fulfillers to add additional activities as they go through a playbook.") 12. After you've added all appropriate stages and activities to your playbook, select Activate in the header. Activating your playbook publishes it so that it runs when triggered. Note: If you change your playbook after activating it, the system saves your changes but deactivates your playbook. You must click Activate again to publish any new changes to your playbook. For more information, see [Playbook statuses and activation states](https://servicenow-prod.fluidtopics.net/skGeGc2aqJDyD26MRxZeBA "View your playbook's status in the main header of the Playbooks builder. This status indicates whether the playbook is active or inactive."). ## Result When your playbook's trigger conditions are met, your playbook runs. As a result, 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 that renders as a playbook, see [Create a sample playbook](https://servicenow-prod.fluidtopics.net/OynyzdxYrLI2quKA_FNsJg "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. **Related concepts** * [Playbook variants](https://servicenow-prod.fluidtopics.net/GVWJgqB5zsu~dhYdlcwbzQ "Use one playbook for multiple scenarios.") * [Restart](https://servicenow-prod.fluidtopics.net/Wspo~mL~PLaIR_qH8U~0ow "Give agents and fulfillers the ability to restart a playbook, stage, or activity.") **Related tasks** * [Test a playbook](https://servicenow-prod.fluidtopics.net/hBc4z~5wYyr9VRNRiyWx6w "Verify that your playbook works as expected by running the playbook with test trigger data. Identify and resolve all errors before activating your playbook.") * [Duplicate Playbooks](https://servicenow-prod.fluidtopics.net/FG8Yib3DdOE7eqFS0UZDdA "Make a copy of an existing playbook with the same trigger, stages, activities, and experience configurations as the original. Edit the duplicated playbook to quickly create a working variation.") * [Add translations for playbooks](https://servicenow-prod.fluidtopics.net/2cAVnfubx4wqzbHx6tFSwQ "Make playbooks available in multiple languages during runtime, to support worldwide business processes.") *[\>]: and then