Understanding the playbook components

Understand the building blocks of a playbook and how to configure them when you create a playbook.

Each playbook consists of the triggers, stages, and activities. You can use variants to use one playbook for multiple scenarios.

Triggers

A trigger is an operation that tells your playbook to start a run. Each trigger has a type and conditions that must be met. Triggers only fire for record operations that are interactive or made by users. For more information, see Triggers.

Stages and activities

An activity represents one step in your business process, and the record for an activity is called an activity definition. Group activities by the stages of your business process, and sequence activities in an order that makes sense for your cross-enterprise workflow. For more information on stages, see Stages and activities.

Variants

Create different variations on top of a base playbook for multiple use cases instead of duplicating and modifying playbooks, or relying on one-time workarounds that use complex run conditions and branching. For more information about variants, see Playbook variants.

• Triggers
  Triggers specify when to start running your playbook.
• Stages and activities
  In Playbook, an activity represents one step in your overall business process. You can sequence many activities together in the stages of your process.
• Playbook variants
  Use one playbook for multiple scenarios.