---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Generate a playbook from text or image

# Generate a playbook from text or image {#ariaid-title1}

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

Generate a playbook using AI by providing text directions or an image.

## Before you begin

Verify that the ServiceNow Otto for Creator plugin is installed and the Playbook generation and Playbook generation with images skills are active.  
Note:  
Skills are available in AdminNow Assist AdminNow Assist SkillsCreator. If you don't see Creator under Now Assist Skills, the plugin is not installed.

For information about installing ServiceNow Otto for Creator, see [Install ServiceNow Otto for Creator](https://www.servicenow.com/docs/access?context=install-now-assist-for-creator&version=australia&pubname=australia-application-development&ft:locale=en-US)

Learn how to write prompts to generate better playbooks. For more information, see [Writing prompts](https://servicenow-prod.fluidtopics.net/S5A9Co~9fOcljojPg8bkmw#playbook-assist__writing-playbook-prompts).  
Role required:

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

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. From the New drop-down menu, select Playbook.
3. On the Create with AI tab, fill in the following fields.  
   {#generate-a-playbook-outline__id_pyq_lnx_rjc__entry__2}

   | Field | Description |
   |-|-|
   | Type | Type of the playbook you want to create. Select Standard playbook for most day to day processes. |
   | Playbook name | Unique, user-facing name for your playbook. This name also appears to agents and fulfillers during runtime. |
   | 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=australia&pubname=australia-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. |
   | Describe the playbook using these inputs | Directions for the playbook that you want to create. Image :   Attach a high quality, clear image of the process. You can compliment the image with text instructions as well. For example, if you attach an image of a flow chart, you can add additional information about the process as text directions. Knowledge Article :   Select a knowledge article based on which you want to generate a playbook. Additionally, you can add instructions in the text box to compliment the knowledge base article. Instructions only :   Provide only text instructions to generate the playbook. * 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_j3s_c2l_kjc} |
   | Execution type | The type of playbook you want to create. Record driven :   The playbook is tied to a record. It is triggered on demands, or automatically based on the record operations. Any data that comes from the playbook will also be stored on that record. Standalone :   Single session playbook that don't store data to a record. These must be manually triggered or called from another playbook. |
   | Parent table | In case of a record driven playbook, the table where the record resides. This option is not relevant for a standalone playbook. |
   | Additional properties | Option to allow the playbook to be publicly accessible. Once embedded it is set to available to unauthenticated users, as long as there aren't additional restrictions preventing the user from accessing the playbook. Note: Playbooks must be tied to a public parent table for unauthenticated users to see it in runtime. |
   [ ]

   {#generate-a-playbook-outline__id_pyq_lnx_rjc}
4. Select Generate playbook preview.  
   Based on your instructions, AI generates a preview of the playbook with all the elements and displays the preview in the diagramming view. AI adds a placeholder activity wherever a relevant activity is not found.
5. Review the generated playbook preview for accuracy.  
   If the generated playbook doesn't meet your requirements, try rephrasing your prompt according to [Writing prompts](https://servicenow-prod.fluidtopics.net/S5A9Co~9fOcljojPg8bkmw#playbook-assist__writing-playbook-prompts), and select Regenerate preview.
6. Select Save and edit playbook.
7. Configure your trigger.  
   For more information about triggers, see [Configure your trigger.](https://servicenow-prod.fluidtopics.net/3bfjeCLPJY74BPr00YDQJw "Begin building your playbook by adding and configuring the trigger.")
8. If the playbook contains placeholder activities, configure the placeholder activities manually.  
   Tip:  
   To generate recommendations for activity definitions from AI instead, see [Generate recommendations for placeholder activities](https://servicenow-prod.fluidtopics.net/ioA0i0IA3xVKw1XTgazR0A "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 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 opens.
   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://servicenow-prod.fluidtopics.net/q71gqVj4D2UP7jKAwTN8EQ "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://servicenow-prod.fluidtopics.net/TFtPYH~_IPW_VTOUI9CSGQ "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}
9. 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://servicenow-prod.fluidtopics.net/YKo~qF7plLOp9f6SFvnhRg "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.").
10. After you configure all your stages and activities, test the playbook.
11. Select Activate in the header.  
    Activating your playbook publishes it so that it runs when triggered.  
    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, you must activate the playbook again. For more information, see [Playbook statuses and activation states](https://servicenow-prod.fluidtopics.net/pbwEsrqoMOY5qjwvwAlvYw "View your playbook's status in the main header of the Playbooks builder. This status indicates whether the playbook is active or inactive.").
{#generate-a-playbook-outline__steps_lhf_qwx_rjc}

## Result

When the trigger conditions of your playbook are met, 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/owHMJBg5o6XDX9thzofjKQ "Create a sample playbook to standardize and automate how Service Desk agents handle chat interactions with VIP users.").

## 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 [Customizing the Playbook Experience](https://servicenow-prod.fluidtopics.net/uF1PCFyAedXdqjsGiLndcg "Customize the layout of your Playbook Experience with base system modular components, templates, and more via integrated UI Builder functionality.").

*[\>]: and then