Playbook record producer

[Community Alums]

Hi, I wanted to know if its possible to have a record producer in Playbooks. Currently I have a record producer that populates 3 different tables.  

Is it possible to do that using playbook?

I noticed playbook triggers from record creation/update, however I want to create the submission form which is the record producer form using playbook. Is that possible?

[Sreeram Nair · Accepted solution]

Unfortunately, No! Playbooks aren’t designed to act as a submission form like a record producer, because a playbook starts after a record exists (it’s triggered by create/update and then guides work), while a record producer is an intake pattern that creates the record(s).

The common approach is to keep your record producer (or a catalog item) to capture the data and create the primary record, then launch a playbook for the lifecycle: either let the playbook template’s conditions auto-start when the main record is created, or have your producer/Flow run a “Start Playbook” action right after submission.

If your current producer creates three related records, move that creation logic into a Flow Designer flow kicked off on the primary record (or invoked by the producer) so it still creates all three tables and then hands off to the playbook for orchestration.

While you could custom-build a Now Experience page that mimics a producer and then redirects into a playbook, that’s heavy customization; best practice is producer (intake) → flow creates needed records → playbook (execution).

[Sreeram Nair · Accepted solution]

Unfortunately, No! Playbooks aren’t designed to act as a submission form like a record producer, because a playbook starts after a record exists (it’s triggered by create/update and then guides work), while a record producer is an intake pattern that creates the record(s).

The common approach is to keep your record producer (or a catalog item) to capture the data and create the primary record, then launch a playbook for the lifecycle: either let the playbook template’s conditions auto-start when the main record is created, or have your producer/Flow run a “Start Playbook” action right after submission.

If your current producer creates three related records, move that creation logic into a Flow Designer flow kicked off on the primary record (or invoked by the producer) so it still creates all three tables and then hands off to the playbook for orchestration.

While you could custom-build a Now Experience page that mimics a producer and then redirects into a playbook, that’s heavy customization; best practice is producer (intake) → flow creates needed records → playbook (execution).

[Ankur Bawiskar · Accepted solution]

@Community Alums 

not possible.

worth exploring this feature

Playbook record generator 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[VishalV02239290]

Playbooks only trigger on: Record creation,Record update ,State changes So they always need a parent record (incident, HR case, custom table record, etc.) before they start.

Inside a playbook, you can: Create task, Create child records, Run Flow Designer actions, Run Script actions (create records in any table)

But this happens after the parent record is already created.

[Community Alums]

I noticed theres an "onboarding playbook" in the yokohama instance, the default. This playbook runs when pressing new button on the workspace, any idea how this is configured this way? It brings straight to record creation.  I could not find a way for this.