Introduction
OnRamp playbooks are built from individual steps called tasks. You can add single tasks one at a time or assemble multiple tasks into a reusable module. Modules act like mini-playbooks – they bundle several related tasks so you can drop the whole process into different playbooks. This article helps you decide when to use a module versus a single task.
Before You Begin
You are familiar with creating playbooks in your Library.
You have permission to create and edit tasks and modules.
Steps
Use a single task when you need a one-off instruction that is specific to this playbook. Examples include a unique approval, a one-time configuration step, or any task that isn’t repeated in other playbooks.
Use a module when you have a group of tasks that you will reuse in multiple playbooks. Modules are perfect for common processes like “Add a new user,” “Send welcome email,” or “Set up billing.”
To create a module, go to the Library and open the Modules tab. Click New Module, add your tasks and instructions, then save the module for later use.
To add a module to a playbook, open your playbook in the Playbook builder, click Add from Library, and choose your module from the list.
If you start with a single task but later decide it should be reusable, create a new module containing that task and replace the original task in your playbooks with the new module.
Tips
Updating a module automatically updates every playbook that uses it, saving you time and keeping processes consistent.
Keep modules focused on a single workflow; avoid grouping unrelated tasks into the same module.
Single tasks are ideal for playbook-specific instructions that don’t belong in a reusable module.