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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Playbook record generator

# Playbook record generator {#ariaid-title1}

Release version: Australia  
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 records directly within the Playbook Experience, streamlining the record creation process before a playbook process starts.
It replaces the standard new record form with a guided, process-driven interface that previews the full playbook flow prior to record creation.
This approach ensures a seamless and intuitive experience for users working with record-based playbooks.
Show full answer Show less  

## When to Use

The record generator is ideal for playbooks that start automatically upon record creation. If a playbook needs to be launched on demand or requires input at launch time without triggering from a new record, consider using on-demand launcher properties instead.

## How It Works

* Before a record exists, the playbook shows a process preview with the record generator activity as the first step, containing the new record form.
* Users fill out and submit this form, which creates the record and triggers the associated playbook process.
* After submission, the record generator activity transitions to a standard record activity linked to the created record, continuing the playbook without leaving the interface.

## Configuration and Selection

* 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, process definition preview, and the Continue button's label, style, and conditions.
* Callers can override the default generator by specifying an explicit process definition or record generator ID in the playbook component query.

## Integration with Decision Tables

While the record generator creates the record and starts the playbook, it does not automatically link to decision tables. To connect them, use decision table outcomes to set initial field values in the record generator's template fields. This enables pre-populating records based on business logic, such as selecting a product or request path.

## Redirecting to the Created Record

Predefined playbook layouts handle automatic refresh and redirection to the newly created record after submission. If using custom layouts, administrators must manually bind the playbook component to the target table and handle record creation events 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.

## 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 [Workflow Studio decision tables](https://www.servicenow.com/docs/enhcHBsFtj~K~7itX1xYIg "Create and maintain decision logic in a table rather than in code.").

## 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.