​
@trigger_playbook

​
What it does

Triggers a jump to another playbook and immediately executes its first step. Use this to chain playbooks together, branch to specialized flows, or create modular conversation structures.

​
When to use it

  • When you want to hand off control to a different playbook mid-conversation
  • To create modular playbooks that can be reused across different flows
  • For complex branching where different user paths should lead to entirely different playbook experiences
  • When you want to separate concerns (e.g., qualification playbook triggers booking playbook)

​
Can combine with

  • Can appear in branching logic to route different user responses to different playbooks
  • Should typically be the last tool in a step (similar to @stop_playbook)
  • Can be used alongside other tools in the same step, but will execute the target playbook after

​
Syntax

In the playbook editor, type @trigger_playbook and select the target playbook from the popup:

​
Configuration

Requirements:
  • You must have at least 2 playbooks created to use this tool
  • The target playbook must exist and be active Tool Settings:
  • No additional configuration required
  • Select the target playbook from the dropdown when inserting the tool

​
Examples

Basic usage - end of playbook handoff:
With qualification before handoff:
Combined with other tools:

​
How it works

  1. When @trigger_playbook is executed, the current playbook immediately stops
  2. The target playbook is loaded and begins execution from Step 1
  3. The conversation context and collected information carry over to the new playbook
  4. The target playbook runs independently until it reaches @stop_playbook or triggers another playbook

​
Tips

  • Modular design: Create reusable playbooks for common flows (lead capture, booking, support) and trigger them from multiple entry points
  • Keep it simple: Avoid creating chains of more than 2-3 playbook jumps to prevent confusion
  • Test thoroughly: Test the full path through triggered playbooks to ensure smooth transitions
  • Name playbooks clearly: Use descriptive names since users will see the playbook name when you insert the tool
  • One-way flow: Remember that triggering a playbook is a one-way handoff - the original playbook won’t resume

​
Common Patterns

Router playbook:
Qualification with escalation:

​
Learn More

  • Getting Started with Playbooks - Overview and all tools
  • Core Concepts & Structure - Understanding playbook structure
  • Complete Playbook Examples - See examples in context
  • Best Practices & Tips - Expert guidance