--- sourceDocument: Yokohama Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Working with automation in Creator Studio # Working with automation in Creator Studio {#ariaid-title1} * Release version: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Working with automation in Creator Studio Automation in Creator Studio enables ServiceNow customers to simplify and streamline task fulfillment by using playbooks---automated workflows triggered by specific events. Playbooks guide agents and fulfillers through consistent processes, improving task execution and enhancing the customer experience. They consolidate business decisions and workflows across the organization, reducing manual intervention and guesswork. Show full answer Show less Playbooks are based on forms that must be published before use, and multiple playbooks can be added to an app to cover various scenarios. ## Key Features * **Playbooks:** Set of actions triggered by events (triggers) to automate workflows, including activities such as assigning tasks, requesting approvals, sending emails, and creating new tasks. * **Activities:** Automated steps within a playbook that define workflow actions. These can be standard or custom activities provided by admins or the ServiceNow AI Platform owner. * **Decisions and Branches:** Conditional logic that creates different workflow paths based on outcomes, enabling dynamic task routing and handling. * **Parallel Processes:** Support for simultaneous execution of multiple workflow branches to enhance efficiency. * **Triggers:** Events that start playbooks, such as record creation or updates to specific statuses. * **Board and Diagram Views:** Two interfaces for building and managing playbooks---Diagram view for visualizing and adding decisions, Board view for rearranging activities. ## Practical Workflow and Usage ServiceNow customers can create, edit, activate, copy, and delete playbooks within Creator Studio to tailor automation to their app's needs. Playbooks run on records in the ServiceNow AI Platform's Request App Workspace, guiding fulfillers through the required steps to complete tasks effectively. Key automation tasks include: * Adding automated playbooks triggered by form submissions or status changes. * Incorporating activities to define what happens during playbook execution. * Adding decisions to create conditional paths and handle complex workflows. * Using parallel processes to run multiple task branches concurrently. * Editing triggers to control when playbooks start. * Activating playbooks in non-production environments before production deployment. ## Benefits for ServiceNow Customers * Automates task assignment and approvals, reducing manual workload for fulfillers. * Ensures consistent handling of requests and tasks across teams. * Improves transparency by clearly showing next steps in workflows. * Enables reuse of existing activities and business decisions, speeding up app development. * Supports customization through custom activities and integration with Workflow Studio for complex automation needs. How do you simplify and streamline tasks for fulfillers? Use automation! For example, you can have a task assigned automatically to someone based on what type of request it is. We'll use playbooks to accomplish adding this automation to your app. Summary: After reading this section, you'll understand how to use [automation](https://servicenow-prod.fluidtopics.net/nliD8WmMVPd9fJnZiLDpOw#gloss-automation "Tasks or requests moving through a workflow without manual intervention.") to do the following things: * Use playbooks to guide agents and fulfillers through processes from start to finish, improving the customer experience and the way tasks are carried out. * Create a consistent process for your tasks or activities to be carried out. * Consolidate business decisions and processes across the organization. {#creator-studio-working-with-automations__ul_bjy_p32_w1c} Note: Because playbooks are based on forms, you must publish a form (mark it as ready) before you use it to create a playbook. For more information, see [Publish a form for your app in Creator Studio](https://servicenow-prod.fluidtopics.net/8Wm55Bm5Q1sZmiRB8KSX0w "Publishing forms once they're ready makes them available as catalog items in the production instance for published apps."). [Playbooks](https://servicenow-prod.fluidtopics.net/nliD8WmMVPd9fJnZiLDpOw#gloss-playbook-creator-studio "A set of automated activities that occur based on a trigger. For example, sending an email when a request is approved. Think of playbooks as pre-programmed workflows that kick in after a form is submitted. They are like if/then statements: If this happens, then that will happen.") are a series of steps triggered by an event. You can add multiple playbooks to an app if needed Key terms: Activity : Activities in a playbook complete automated tasks, such as obtaining approvals, assigning records, and sending email. Automation : Tasks or requests moving through a workflow without manual intervention. Playbook : A set of actions based on an initiating action called a trigger. Record : A task or request that must be acted on. All rows in ServiceNow tables are individual records. Records have different states depending on what actions have been taken. Trigger : The event that starts making the playbook run. Workflow : The path a record takes from creation to completion. ## What is automation? {#creator-studio-working-with-automations__section_btj_1xf_l1c} Automation in Creator Studio enables you to create simplified playbooks, which are basic, automatic workflows. Simple playbooks consist of a trigger (such as a record changing states, or a user choosing a specific answer for a question) and an activity (such as the record being assigned to a new person). Playbooks enable you to add the following: * Activities to your automation to define the workflow's path. * Decisions to create different paths, or branches, depending on the decision's outcome. * Custom activities defined by your admin or ServiceNow AI Platform owner. {#creator-studio-working-with-automations__ul_dcn_3k2_w1c} Playbooks take the guess work out of assigning tasks and help users focus on the tasks and information that matter to their job. A well-designed playbook can do these things: * Automatically start or trigger changes for different types of records, such as task assignments. * Reuse activities and business decisions from other workflows you've already created. * Clearly show the next steps that fulfillers must take to move to the next step of completing the record's life cycle. {#creator-studio-working-with-automations__ul_ifb_wk2_w1c} There are several types of activities that you can add to playbooks that, when paired with decisions, remove the manual thinking behind what to do next when addressing tasks. Depending on your configuration, some of the activities you can add include: * Request approval for a task * Assign the task to someone * Create a new task as a next step * Send an email * Choose a custom action configured by your admin {#creator-studio-working-with-automations__ul_trf_rzm_n1c} Note: In addition to creating custom activities, your admin can also hide standard activities, so you may not see all of the above options. You can even use answers from a playbook's associated form to power activities. For example, if someone's requesting a gift box and they answer Yes to the question "Do you eat meat?" then you can create an Assign to activity to route the gift box to the Meat department for fulfillment. You can also use a placeholder activity for more complex activities that must be configured outside of Creator Studio, or for another activity to be swapped in later. Complex activities are configured in a different tool called Workflow Studio. ## What goes into building automation? {#creator-studio-working-with-automations__section_vbx_xzf_l1c} Automations in Creator Studio include the following parts.{#creator-studio-working-with-automations__table_gdk_c1g_l1c__entry__2} | Concept | Description | |-|-| | Playbook | An automatic workflow that guides users through tasks based on the record's status changes. Find out more about creating playbooks in [Add an automated playbook to an app in Creator Studio](https://servicenow-prod.fluidtopics.net/BtrH~tpDUQA20gzYOiIszg "Create an automated playbook, which is a process that runs whenever a record is created or updated by the app's specified form."). | | Trigger | The event that specifies when the playbook should start running, such as when a form is submitted or updated to a specific status. Check out [Edit the trigger for a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/UErzktjrW7OGuLH2niKwgA "Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running.") for more information. | | Activity | The thing that happens during the playbook, such as assigning a task or requiring approval. Note: If you're already familiar with optional activities in playbooks, that's great! However, to keep automations streamlined and simple, Creator Studio doesn't support optional activities. If you must create optional activities, you can add a placeholder activity in Creator Studio and then edit the placeholder in Workflow Studio or swap it out for another activity later in Creator Studio. Additionally, admins can create custom activities for you to include in a playbook. Learn how to add activities in [Add activities to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/OM8G1brxpfBAO~nPDBgBig "Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes."). | | Decision | A series of inputs, conditions, and results that create different branches, or conditional paths that users follow based on the decision's outcome. Get the scoop on adding decisions in [Add a decision to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/kxurYRo8b2qVeHW~0BURcw "Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio."). | | Branch | A distinct path from a decision's outcome, or what happens for each of the decision's possible choices. For more information, see [Add a decision to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/kxurYRo8b2qVeHW~0BURcw "Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio."). | | Parallel process | Branches for activities and stages that run in parallel to another branch of activities. Learn about parallel processes in [Add a parallel process to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/Fi~4GBJ9TxZJibtVwEn_BQ "Create parallel processes in Creator Studio to make things happen in your app at the same time."). | | Connectors | Lines that connect activities and decisions in a playbook that enable you to add more activities, decisions, and parallel processes. You can drag connectors between activities to create parallel activities. | [Table 1. Automation parts] {#creator-studio-working-with-automations__table_gdk_c1g_l1c} ## Board and Diagram views of a playbook {#creator-studio-working-with-automations__section_glv_3lx_m1c} Creator Studio offers two ways of working with playbooks: the Board view and the Diagram view. The Diagram view is a visually intuitive diagram that shows you the order that activities occur in the playbook. When you select an activity, such as the trigger or a decision, a modal pops up where you can edit its details. You must use the Diagram view to add decisions.Figure 1. Diagram view of the playbook The Board view is a more traditional layout, which shows each activity as a card in the navigation panel. When you select an activity, for example a task, its editable details appear in the canvas for you to work with them. You must use the Board view to rearrange activities.Figure 2. Board view of the playbook This help document will primarily give instructions using the Diagram view, with alternate directions on how to complete automation tasks in the Board view. ## Where do playbooks run in the ServiceNow AI Platform? {#creator-studio-working-with-automations__section_jfb_tb3_q1c} Users work on requests in the Request App Workspace on the ServiceNow AI Platform, which lists a record for each request. The playbooks run on the specified records in the app's workspace category. Specifically, the Catalog tasks tab of the record details walks users through the activities they must do to complete the task and close the record. * **[Workflow for creating automations in Creator Studio](https://servicenow-prod.fluidtopics.net/EyxhW640VTtOgN7MvWAhTA)** Provide your organization's fulfillers with guidance when addressing records generated from the app by adding automated playbooks to it. * **[Add an automated playbook to an app in Creator Studio](https://servicenow-prod.fluidtopics.net/BtrH~tpDUQA20gzYOiIszg)** Create an automated playbook, which is a process that runs whenever a record is created or updated by the app's specified form. * **[Copy an automated playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/MXeylKzlHh8PP9GJ7Y7VaQ)** Duplicate an existing playbook and make small changes to it, which may be faster than creating an entirely new automated playbook. * **[Add activities to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/OM8G1brxpfBAO~nPDBgBig)** Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes. * **[Add a decision to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/kxurYRo8b2qVeHW~0BURcw)** Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio. * **[Add a parallel process to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/Fi~4GBJ9TxZJibtVwEn_BQ)** Create parallel processes in Creator Studio to make things happen in your app at the same time. * **[Edit the trigger for a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/UErzktjrW7OGuLH2niKwgA)** Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running. * **[Edit a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/hyfw~CGCr6l3RNni~1tG4w)** Update a playbook to change its settings, or rearrange or remove tasks, to make it work for your app. * **[Activate a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/HqFaahmY_GASP0jsdLE2WA)** Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production. * **[Delete a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/WBFV4TbkGelMFsMW_5J7Cw)** Delete a playbook to remove it from the app completely.