Summary / When to Use This
Linked Modules let you reuse a single module across multiple playbooks—perfect for standard processes you want to maintain in one place. When a linked module is updated, the changes automatically apply everywhere it’s used. This helps keep your playbooks consistent and saves time maintaining duplicate content.
Before You Begin
Make sure you have:
Access to the Library section in OnRamp
Permission to create or edit Modules and Playbooks
Steps to Follow
1. Create a Module
Go to Library → Modules.
Click + Create Module.
Add your module details, including name, description, and tasks.
Click Save.
Your new module can now be linked to any number of playbooks.
2. Link the Module to a Playbook
Go to Library → Playbooks.
Open the playbook you want to edit and go to the List tab.
Click + Module, then choose Add Linked Module.
Select the module you created earlier.
You’ll see the module added to your playbook with a Linked Module tag.
💡 Tip: You can still add playbook-specific tasks around the linked module to customize the flow.
3. View Where a Module Is Used
From Library → Modules, open the module you want to review.
Click the Linked Playbooks tab.
You’ll see a list of every playbook currently using that module.
If no playbooks appear yet, the message “No usages of module found” confirms it hasn’t been linked anywhere.
4. Edit or Update a Linked Module
When you edit a linked module’s tasks or details, those updates automatically apply to every playbook it’s connected to—no need to update each one manually.
At the top of a module, OnRamp displays an info banner showing how many playbooks it’s linked to (for example, “This Module is linked to 1 Playbook”).
5. Check Linked Module Status from a Playbook
Within a playbook, any module that’s linked displays a green Linked Module label next to its name.
You can click into it directly to view or manage the original module in the Library.
Tips & Troubleshooting
Archiving Linked Modules:
When you archive a module that’s linked to one or more playbooks, you’ll be prompted to choose how to handle those connections:
Leave an unlinked copy: Keeps a standalone version of the module in each playbook it’s currently used in.
Remove from playbooks: Completely removes the module from all playbooks it’s linked to before archiving.
Choose carefully depending on whether you want to preserve the playbook structure or remove the module entirely.
Permissions:
Only users with edit access to both Playbooks and Modules can create, link, or archive modules.
Version Control:
If you plan major changes, consider duplicating the module before editing or archiving it—this helps prevent unexpected updates to live playbooks.