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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Playbook record generator

# Playbook record generator {#ariaid-title1}

Release version: Brazil  
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 in ServiceNow's Playbook Experience enables users to create new records through a guided, interactive process within a playbook.
It replaces the standard new record form by embedding the record creation step directly into the playbook workflow, ensuring the record is created before the process starts.
This approach offers a seamless and transparent way for users to initiate record-based playbooks.
Show full answer Show less  

## When to Use

This feature is ideal for playbooks that are triggered automatically upon record creation. If your use case requires launching playbooks on demand or providing inputs at launch time without an underlying record, consider using on-demand launcher properties instead.

## How It Works

* The playbook displays a preview of the entire process before the record exists, with the first step dynamically inserted as a new record form.
* Users fill out and submit this form, which creates the record and triggers the process.
* After submission, the playbook transitions smoothly from the preview to the active process associated with the newly created record without leaving the playbook interface.
* The initial "Record Generator" activity changes to a "Record" activity once the record is created, reflecting its new state.

## Configuration and Selection

* Multiple record generators can be configured for the same table; the one with the lowest order value is selected by default.
* This default can be overridden by specifying a process definition or record generator identifier in the playbook component query.
* Administrators can customize the record generator activity's name, form view, and process definition displayed before record creation.
* The submit button ("Continue") is a declarative action that can be styled, relabeled, or conditioned like any other declarative action.

## Handling Redirects

Standard playbook layouts automatically refresh and redirect users to the newly created record. For custom layouts, you must bind the playbook component to the parent table and handle the record creation event to route users appropriately.  
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.