---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Add an automated playbook to an app in Creator Studio

# Add an automated playbook to an app in Creator Studio {#ariaid-title1}

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

Create an automated playbook, which is a process that runs whenever a record is created or updated by the app's specified form.

## Before you begin

Playbooks run on the records generated by catalog items you create for the app, so you must add forms to the app before you can add automation. You can use only published forms (that is, forms that have been marked as ready) to create automations. For more information, see [Working with forms in Creator Studio](https://www.servicenow.com/docs/MnEjqHT4MYv1XEBrspUPqQ "To add items or services to your catalog, you must create a different form for each thing being requested.").

To add a playbook, you must be given permission to work on the app.

## About this task

Note:  
For example, you can build a travel request app where people can ask for permission for different types of travel, which automatically routes the request to a manager for approval.

## Procedure

1. Go to AllApp EngineCreator Studio to see all the apps on the Creator Studio home page.
2. Open the app that you want to add automation to.
3. Select + Add automation for the form that you want to add a playbook to.  
   Note:  
   If your app has a lot of forms, you can use the search box in the navigation panel to search for a specific form.  
   The following rules apply:
   * If the form is still in draft, a message pops up telling you that you must publish the form first. Check out [Publish a form for your app in Creator Studio](https://www.servicenow.com/docs/8Wm55Bm5Q1sZmiRB8KSX0w "Publishing forms once they're ready makes them available as catalog items in the production instance for published apps.") for more information.
   * You can select only published forms to run the playbook. If you published a form and then edit it, you can't use the version that's being edited in a condition for a playbook, for example as a trigger for the automation. However, you can use the published version of the form or publish the version that you're editing, which makes its question answers available to use in playbook conditions.{#creator-studio-add-automation__crs-auto-publish-trigger}
   * The table for the form you choose is the app's underlying table, which is specified when the app is created. However, your admin can change the table, see [Administering an app's underlying table](https://www.servicenow.com/docs/0GRcrDmQOwTlrwnXvuBHKw "Admins can change the default table that apps built in Creator Studio save their requests to.") for details. If you get a message that playbook creation is unavailable, contact your admin to verify the table for the app.
   {#creator-studio-add-automation__ul_ann_hr2_y2c}
4. Specify the playbook's General attributes in the Create playbook modal.  
   {#creator-studio-add-automation__table_eld_vcg_l1c__entry__2}

   | Field | Description |
   |-|-|
   | Playbook name | Descriptive name for the playbook you're creating. |
   | Description | Brief explanation of what the playbook does, for example, the end goal for the record type. |
   [Table 1. General playbook definition fields]

   {#creator-studio-add-automation__table_eld_vcg_l1c}  
   Figure 1. Create a playbook
5. Specify the Schedule for the playbook.
   1. Select the type of Trigger that initiates the playbook.  
      {#creator-studio-add-automation__table_hp1_52g_l1c__entry__2}

      | Trigger | Description |
      |-|-|
      | Form submitted | Start running the playbook when a user submits the form you chose. |
      | Form updated | Start running the playbook when a user updates the form you chose. |
      | Form submitted or updated | Start running the playbook when a user submits or updates the form you chose. |
      [Table 2. Playbook trigger options]

      {#creator-studio-add-automation__table_hp1_52g_l1c}  
      Note:  
      You can't change an playbook's trigger type after you finish creating the playbook. Instead, create a new playbook with a different trigger.

      However, you can edit the trigger condition, such as making the
      playbook run conditionally based on a specific answer to a question. For more information, see [Edit the trigger for a playbook in Creator Studio](https://www.servicenow.com/docs/UErzktjrW7OGuLH2niKwgA "Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running.").
   2. If you chose a trigger that includes a form being updated, specify how often that app should Run your playbook.  
      The options are:
      * Once
      * For each unique change
      * Only if not currently running
      * For every update
      {#creator-studio-add-automation__ul_e1b_4fg_l1c}
   3. Specify the conditions that must be met for the playbook to begin running by selecting Add conditions.  
      * If you want to trigger the playbook based on the value of a column in a table, select the [Field](https://www.servicenow.com/docs/nliD8WmMVPd9fJnZiLDpOw#gloss-field-creator-studio "A field in Creator Studio is a column on the app's underlying table. If you're using condition builder, a field is either a column on the table or a question from the form.") that you want to be the trigger, as well as its condition Operator and the specific trigger Value. For example, when a Start date is after the Date needed.{#creator-studio-add-automation__crs-trigger-question-ph-1}
      * If you want to trigger the playbook based on the response from a form, select Questions as the trigger Field. Then select the question you want in the Question field, the condition Operator and the answer's Value.  
        Figure 2. Question answer as trigger for an automation {#creator-studio-add-automation__crs-trigger-question-ph-2}

      {#creator-studio-add-automation__ul_fk1_r44_sbc}

      Add as many conditions as you need. For more information, see [Create a condition statement using the condition builder](https://www.servicenow.com/docs/access?context=create-cond-state-using-cond-build&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US).{#creator-studio-add-automation__crs-trigger-conditions-many}
   4. Select Create.
   {#creator-studio-add-automation__substeps_ldr_42g_l1c}

## Result

Congrats:  
Congratulations, you've created an automation!

## What to do next

Next, you need to add activities to the playbook. For more information, see [Add activities to an app's playbook in Creator Studio](https://www.servicenow.com/docs/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.").

*[\>]: and then