Playbook Modules vs. Single Tasks: When to Use Each

OnRamp Playbooks are built from individual tasks — but not all tasks are the same. Some belong on their own; others are better bundled into a reusable module. Here’s how to think about the difference and when to use each.

Single Tasks

Use a single task when the step is specific to one Playbook and won’t be reused elsewhere.

• A unique approval step for a particular customer type
• A one-time configuration that doesn’t repeat across projects
• Anything too specific to generalize into a shared module

Modules

Use a module when you have a group of related tasks you’ll reuse across multiple Playbooks. Modules act like mini-Playbooks — bundle the tasks once, then drop the whole set into any Playbook that needs it.

• “Add a new user” — same steps every time, used in many Playbooks
• “Send welcome email + schedule kickoff” — a repeatable sequence
• Any multi-step process you run identically across projects

The big advantage: updating a module automatically updates every Playbook that uses it.

How to Create and Use Modules

1. Go to the Library and open the Modules tab.
2. Click New Module, add your tasks and instructions, then save.
3. To add a module to a Playbook, open the Playbook builder, click Add from Library, and choose your module.

If you built a single task that turns out to be reusable, create a module containing that task and replace the standalone task in your Playbooks with the new module.

Tips

• Keep modules focused on one workflow — avoid grouping unrelated tasks together.
• Single tasks are best for Playbook-specific instructions that don’t belong in a shared module.
• When in doubt, start with a single task and convert to a module once you see the pattern repeating.