Module Automations

Automations in OnRamp are most powerful when they travel with your content. Module automations let you define automation behavior once at the module level — and have it apply automatically wherever that module is used.

New to automations? Every automation is a trigger (an event) plus an action (what OnRamp does in response). You build and manage them centrally in the Automations Library (Library → Automations). This article covers what happens when those automations live on a module.

This article covers how to add automations to modules, how they behave in linked modules and workflows, and what to expect when a module with automations is added to a project.

Adding Automations to Modules

Automations can be added to any module in the module library the same way they're added elsewhere in OnRamp — from the Automations tab within the module. You have two options: build an automation directly on the module, or use Import from library to pull in an existing automation from the Automations Library, the central catalog of every automation your team has built.

Either way, the automation is stored with the module and travels with it whenever the module is used in a playbook, workflow, or project.

Automations imported from the library stay linked to their source. If you later edit that automation in the Automations Library, the change flows to every module using it — so you maintain the logic in one place.

Linked Modules With Automations

When a module is linked and added to a playbook, any automations on that module are automatically applied to the playbook as well. You don't need to configure them separately — they come along with the module.

If the linked module is later removed from the playbook, its automations are removed too. Automation state follows the module.

Module Automations in Workflows

When a conditional module is added to a workflow, the Automations section surfaces all possible automations across every module that could be conditionally added. Automations are then configured and applied based on which modules are actually included in a given path — so the right automations are active for the right conditions without manual cleanup.

Adding Modules With Automations to Projects

When a module is added to a project — whether manually or via automation — all automations associated with that module are added to the project at the same time. If the project is connected to a CRM record, CRM IDs are automatically populated into those automations from the connected record. This matches how automations behave when applied from the Automations Library.

One important note: automations won't re-run for events that have already passed. If a module has a "project created" automation and is added mid-project, that automation won't trigger — the event it listens for has already occurred. Automations only fire for events that happen after the module is added.

Frequently Asked Questions

Do I need to re-add automations when I use a linked module in a new playbook?

No. Automations on a linked module apply automatically to any playbook the module is associated with.

What happens to automations if I remove a linked module from a playbook?

They're removed from the playbook along with the module.

Can I use an automation from the Automations Library on a module?

Yes. In the module's Automations tab, choose Import from library. The automation is then stored with the module and travels with it like any other module automation.

If I edit a library automation later, does the change reach the modules using it?

Yes. Automations imported from the Automations Library stay linked to their source, so edits you make in the library flow to every module using that automation.

What's the difference between adding an automation to a module vs. applying one from the Automations Library?

Applying from the library attaches an automation to specific destinations you choose (playbooks, projects, modules). Adding it to a module makes it portable — it comes along automatically every time that module is used, with no per-destination step.

How does OnRamp know which automations to activate for conditional modules in a workflow?

The Automations section shows all possible automations up front. OnRamp applies the appropriate subset based on which conditional modules are active in a given path.

Will automations run on events that already happened before the module was added?

No. If the triggering event — like project creation — occurred before the module was added, that automation won't fire.

Where do CRM IDs in automations come from?

They're pulled from the CRM record already connected to the project at the time the module is added.