--- sourceDocument: Zurich Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/build-workflows Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Playbook record generator # Playbook record generator {#ariaid-title1} Release version: Zurich Updated September 15, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Playbook record generator The Playbook Record Generator enables users to create new records seamlessly within the Playbook Experience before a process starts. It integrates a dynamic form as the first activity in a playbook process, allowing users to submit record data directly through the playbook interface. This tool is essential when playbooks require a record to exist to trigger automated processes and provides a guided, user-friendly record creation workflow. Show full answer Show less ## When to Use This feature is ideal for record-based playbooks that automatically start upon record creation. For scenarios requiring on-demand playbook launches or user-supplied inputs at launch, alternative methods like on-demand launcher properties are preferred. ## How It Works * The playbook initially displays a preview of the full process with a dynamic first step containing the new record form. * Users complete and submit the form, which creates the record and triggers the associated process definition. * The process transitions smoothly from preview to running state without the user leaving the playbook interface. * The record generator activity type updates from "Record Generator" to "Record" once the record exists. ## Configuration and Customization * Multiple record generators can be configured per table; the one with the lowest order value is selected by default. * Administrators can customize the record generator activity name, form view, and process definition shown before record creation. * The submit button (default label: "Continue") is a declarative action, allowing label, styling, and condition customizations. * Playbook layouts automatically handle redirecting users to the newly created record; for custom layouts, developers must bind the component and handle record creation events to manage navigation. ## Practical Benefits for ServiceNow Customers * Enables streamlined record creation directly within playbooks, improving user experience and process consistency. * Supports complex process definitions by ensuring records exist before process initiation. * Offers flexibility to tailor the record creation form and process flow to organizational needs. * Facilitates seamless transitions from record creation to process execution without interrupting user workflow. Use the playbook record generator to guide a user through the record creation process using the Playbook Experience. Playbooks requires a record to be created or updated before a process can start. However, you can use the playbook record generator to enable users to create a record using the playbook experience. You can then configure your workspace or UI Builder page to display the record generator Playbook Experience component in place of the standard new record form. The component appears when a user opens a new record tab. ## When to use the record generator {#playbook-record-generator-overview__section_when_to_use} The record generator is best suited to record-based playbooks that start automatically when the record is created. If you need to launch a playbook on demand or supply inputs at launch time rather than through a triggered record, consider on-demand launcher properties instead. ## How the record generator works {#playbook-record-generator-overview__section_how_it_works} Before the record exists, the playbook displays a representation of the process definition configured for the record generator. A dynamically inserted first activity contains the new record form, while the remaining activities in the process stay pending. This preview lets the user see the full process up front without a record backing it yet. Playbook record generator inserts a record generator activity as the first step within a specified process definition created with Playbooks. This record generator activity contains a new record form. After a user submits the form, the system creates the record. Record creation normally triggers the process definition shown in the preview. If no process definition is running after submission, the playbook manually triggers the one shown to the user before record creation. The record generator activity's type then changes from Record Generator to Record, because it's now associated with the created record. The running process replaces the preview without the user leaving the playbook, for a seamless and guided record creation experience. ## Selecting a record generator {#playbook-record-generator-overview__section_selecting} You can configure more than one record generator for the same table. When several record generators apply, the one with the lowest Order value is selected by default. A caller can override this default selection explicitly by supplying a process definition or record generator identifier in the query passed to the playbook component. ## Configuration options {#playbook-record-generator-overview__section_config_options} Administrators can specify the name of the record generator activity, the form view, and the process definition shown to the user before the record is created. The button the user selects to submit the form (Continue) is itself a declarative action. Administrators can override its label, styling, or conditions the same way they would customize any other declarative action. ## Redirect to the created record {#playbook-record-generator-overview__section_redirect} The out-of-the-box playbook layouts handle the refresh and redirect to the newly created record automatically. If you build a custom layout, you're responsible for wiring this yourself: binding the playbook component to the target parent table, and handling the event the component dispatches when the record is created so your page can route to it. * **[Configure a playbook record generator](https://www.servicenow.com/docs/aFoyjQ142OWYkHxzbtDXlA)** Configure a record generator to let a user create the parent record for a process from inside the Playbook Experience. * **[Edit a record after record generator submission](https://www.servicenow.com/docs/4inWd5ZcVz__Ue0CqXZwkQ)** Keep a record editable after a playbook record generator creates it.