---
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 in ServiceNow enables users to create new records directly within the Playbook Experience, providing a seamless and guided workflow before the actual record exists.
This feature is designed for record-based playbooks that start automatically upon record creation, allowing you to replace the standard new record form with a playbook-driven form embedded in your workspace or UI Builder page.
Show full answer Show less  

## How It Works

* The record generator inserts a first-step activity in the playbook process, presenting a new record form before the record exists.
* Users complete and submit the form, triggering record creation and automatically starting the associated playbook process.
* The initial preview process is replaced by the live process linked to the newly created record without leaving the playbook interface, ensuring a smooth user experience.
* If no process is running post-submission, the playbook manually triggers the previewed process.

## When to Use

This tool is ideal for automating workflows that depend on a record being created upfront and starting the playbook immediately. For playbooks that require launching on demand or input at launch time, on-demand launcher properties are recommended instead.

## Configuration Options

* Multiple record generators can be configured per table; the one with the lowest order number is selected by default unless explicitly overridden via query parameters.
* Administrators can customize the record generator activity name, form view, and the process definition shown before record creation.
* The submission button ("Continue") is a declarative action that can have its label, style, and conditions customized.

## Integration with Decision Tables

Decision tables can provide initial data values for the record generator by supplying outcomes that populate template fields of the new record, enabling dynamic record creation based on business rules. However, the record generator and decision tables do not link automatically; you must configure this connection explicitly.

## Redirect and Layout Handling

* Predefined playbook layouts automatically refresh and redirect users to the newly created record.
* If you create custom layouts, you must handle the binding to the parent table and listen for the record creation event to implement redirection yourself.

## Post-Creation Record Editing

It is possible to keep the record editable after it is created by the playbook record generator, supporting continued updates within the playbook experience.  
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.

## Relationship to decision tables {#playbook-record-generator-overview__section_decision_tables}

A decision table determines a business value, such as which product or path applies to a request. The record generator creates the record and starts the playbook. The two aren't linked automatically. To connect them, use the
outcome of a decision table as a value in the record generator's template fields, which set the initial values of the new record.

For example, a decision table can identify the product that applies to a request, and the record generator can create the record with that product already set. For more information, see .

## Redirect to the created record {#playbook-record-generator-overview__section_redirect}

The predefined 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.

