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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Generate a playbook

# Generate a playbook {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Provide an image, text, or both inputs to Now Assist to generate a playbook.

## Before you begin

Learn how to write prompts to generate better playbooks. For more information, see [General Guidelines for Building Playbooks with Now Assist](https://www.servicenow.com/docs/7RIEqZH6J_Bz2NGJBrqeVA "See guidelines and examples for using the Now Assist Playbooks capabilities.").  
Role required:

* admin, playbook.admin, pd_author, or a delegated developer permission
* now.assist.creator
{#generate-a-playbook-outline__ul_jq2_qgx_tbc}

## Procedure

1. Navigate to AllWorkflow Studio.  
   The Workflow Studio landing page appears. Playbooks is shown by default, but you can toggle to flows, subflows, actions, and decisions.
2. Open the New drop-down menu and select Playbook.  
   The new playbook opens in a Workflow Studio tab. Build with Now Assist is the default method, but you can switch to Build from scratch.
3. On the Build with Now Assist tab, fill in the following fields.  
   {#generate-a-playbook-outline__table_ubj_vbf_dbc__entry__2}

   | Field | Description |
   |-|-|
   | Playbook name | Unique, user-facing name for your playbook. This name also appears to agents and fulfillers during runtime. |
   | Now Assist input | Describe the playbook using text, an image, or both. Make sure your image is the right format and size. : * The image should be in JPG, JPEG, PNG, or WEBP format. * By default, the image should be 5MB or less. Note: To change the max image size, change the com.glide.attachment.max_get_size system property. To earn more about changing the max image size, see [Change the maximum image size](https://www.servicenow.com/docs/2WLiOlRYfJnMqPhzoiOpBA "Adjust the maximum size that is accepted for images used for playbook generation."). {#generate-a-playbook-outline__ul_chx_13d_tcc} Make sure your image is clear and visible. : * Upload an image that is clear and visible to the human eye. Make sure that any writing is legible. If you can't what's in an image, neither can Now Assist. If the image is unclear in any way, Now Assist returns an error and cannot generate a preview. This error is also displayed if an image is not a business process. * When uploading an image, it is the primary input by default. You can use the text description to add more context about the business process in your uploaded image. Note: Since an image is the primary input, you will receive an error for a unusable or unclear image even if you include a valid text input. {#generate-a-playbook-outline__ul_kjn_wfd_tcc} Be precise and descriptive in any text input. : * Describe each stage and activity in as much detail as you can. * Specify the order that stages and activities run in. * Specify if any stages or activities run at the same time. {#generate-a-playbook-outline__ul_zzb_hbd_tcc} |
   | Application | 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=xanadu&pubname=xanadu-application-development&ft:locale=en-US). Important: You can't change the application scope of a playbook after you've generated a preview for it. |
   [ ]

   {#generate-a-playbook-outline__table_ubj_vbf_dbc}
4. Select Generate playbook preview.  
   Workflow Studio uses your image and text inputs to build a playbook. If successful, Workflow Studio displays a preview of the playbook in diagramming view.

   Now Assist does its best to guess which common activities to use in your generated playbook, and inserts placeholder activities when it is unable to guess.

   <br />

5. **Optional:** Scroll horizontally in the preview, and zoom in and out as needed.
6. Review the preview of the playbook for accuracy.
7. **Optional:** If the playbook doesn't meet your requirements, try updating your image or text inputs according to [General Guidelines for Building Playbooks with Now Assist](https://www.servicenow.com/docs/7RIEqZH6J_Bz2NGJBrqeVA "See guidelines and examples for using the Now Assist Playbooks capabilities."), and select Regenerate preview.
8. If you're ready to generate your playbook, select Save and edit playbook.  
   Note:  
   Generating or regenerating a playbook preview counts as 10 assists. To track your Now Assist usage, see [Monitoring Now Assist usage in Subscription Management](https://www.servicenow.com/docs/access?context=monitoring-now-assist-usage&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US). Opening a playbook does not count as an assist.  
   A playbook outline is generated, and common activities are inserted where possible.
9. **Optional:** To view the prompt that was used to generate a playbook, navigate to More actions menuPropertiesGeneralNow Assist directions.  

   <br />

   <br />

10. Configure your trigger.  
    For more information about triggers, see [Configure your trigger.](https://www.servicenow.com/docs/E7cq4KjIlhw6z2xPYX3PWQ "Begin building your playbook by adding and configuring the trigger.")
11. Configure placeholder activities by manually selecting the placeholder activity.  
    Tip:  
    To generate recommendations for activity definitions from Now Assist instead, see [Generate playbook recommendations](https://www.servicenow.com/docs/xnhACgteTgb4EJ3uDItYtA#generate-playbook-recommendations "Select the activity definition for a placeholder activity from a list of AI-generated recommendations. The system generates recommendations based on an activity’s name and description.").
    1. Select a placeholder activity that you want to configure ( ![Placeholder activity icon.]()).  
       You can also hover over the placeholder activity and select the replace activity icon (![Icon for replacing an activity]() in the mini-picker to directly open the activity picker.
    2. **Optional:** Update the Label and Description, if needed.
    3. Under the Activity definition field, select the edit button (![Edit icon in the playbook builder.]()).  
       The activity picker is displayed.
    4. In the activity picker, search for the activity, subflow, or action to add.  
       Note:  
       Select the application first, and then the activity from the resulting list. For more information about subflows or actions, see [subflow, or action](https://www.servicenow.com/docs/i8OqLCQBMmV0nFVRcvKTfw "Include all automation assets in the activity picker to add a subflow, flow, or action directly to your playbook without having to create an activity definition.").
    5. Configure the activity inputs.  
       For more information about common activities and their inputs, see [Playbooks reference](https://www.servicenow.com/docs/CS8qfoIsa1hJ_wXAWJ9d5g "Guides, lists, tables and more that you can reference as you work with Playbooks and their associated components."). {#generate-a-playbook-outline__configure-activity-inputs}
    {#generate-a-playbook-outline__configure-activity-inputs} {#generate-a-playbook-outline__substeps_ccv_vm2_r1c}
12. **Optional:** If you don't see the activity that you want to add in the activity picker, create an activity definition.  
    For more information, see [create an activity definition](https://www.servicenow.com/docs/pITWPHnYSkeaUF7LTFisuw "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.").
13. After you configure all your stages and activities, select Activate in the header.  
    Activating your playbook publishes it so that it runs when triggered.
14. **Optional:**  
    Note:  
    When you change your playbook after activating it, the system saves your changes but deactivates your playbook.
    To publish any new changes to your playbook, select Activate again.  
    For more information, see [Playbook statuses and activation states](https://www.servicenow.com/docs/VWGWzkBVZhIuBkA3l99udw "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 [Design an automated process](https://www.servicenow.com/docs/OYIpG~u5ZGYDHucY5Xce5A "Transform an example manual business process into a well-designed, automated process that runs on the ServiceNow AI Platform.").

## What to do next

Design the Playbook Experience for your agents and fulfillers in UI Builder. To learn how to design and customize the runtime playbook experience in UI Builder, see [Customize the Playbook Experience](https://www.servicenow.com/docs/0k7A_E~Wzxq~uHN1bSBgZg "Customize the layout of your Playbook Experience with base system modular components, templates, and more via integrated UI Builder functionality.").

*[\>]: and then


