Project Automations let you build smart, no-code rules that connect OnRamp with Salesforce, HubSpot, and other tools. You define a trigger (like “when a task is completed”) and an action (like “update a Salesforce field”) to keep data synced and work automated.
Automations save you time, prevent data mismatches, and ensure that critical updates happen instantly when progress occurs inside OnRamp.
When to Use This
Use Project Automations when you want OnRamp to automatically take action based on project activity — without manual updates.
Common use cases include:
Updating Salesforce Opportunities when a key onboarding task is completed
Uploading files or form data from a task into Salesforce
Updating a HubSpot property when a project reaches completion
Triggering a webhook when a playbook milestone is achieved
Automations can be configured at the Playbook level (applies to all new projects) or at the Project level (applies only to one project).
Before You Begin
Make sure:
Your Salesforce or HubSpot integration is connected under Settings → Integrations
You have permission to edit the Playbook or Project
Any fields you plan to sync are accessible by your integration user
💡 Tip: Playbook-level automations act as templates. If you change them later, all future projects using that playbook will inherit the updated logic automatically.
Steps to Follow
1. Open the Automations Tab
Navigate to Library → Playbooks (or open a live Project)
Select the Automations tab
Click + Create to add a new automation
2. Choose a Trigger
Triggers define when the automation runs.
Available options include:
When project created
When project updated
When project completed
When module completed
When task completed
When a specific playbook data field changes
When any playbook data field changes
If you choose When task completed, you’ll be prompted to select the specific task that should trigger the automation.
⚙️ Example Use Case:
Trigger: When task completed → “System Data Uploaded”
Action: Update Salesforce field → Update the related Opportunity’s “Stage” to “Needs Analysis.”
3. Add an Action
Actions define what happens after the trigger fires.
Click + Add Action, then select from the available action types:
Update Salesforce field – Sync data from OnRamp into Salesforce
Upload Files to Salesforce Object – Send task-uploaded files to Salesforce
Update HubSpot field – Push field updates to HubSpot
Call Webhook – Send OnRamp data to an external endpoint or API
💡 Tip: You can chain multiple actions under the same trigger if you need to update multiple systems or objects at once.
4. Configure the Action
Each action type has configurable options.
For Salesforce updates:
Select the Object to update (e.g., Opportunity, Account, or custom object)
Choose the Field to use as reference (commonly
Nameor an ID field)Under Map fields to update, match Salesforce fields with data from OnRamp.
You can pull from:
Task data – e.g., Completed Date
Project data – e.g., Project Name
Task answers – e.g., numeric form response or text input
Salesforce data – e.g., set a picklist value like “Needs Analysis”
⚙️ Example Use Case:
OnRamp Project Status → Salesforce data → “In Progress”
Last Completed Task → Task data → “Task Name”
Project Completed % → Project data → “Project Completion Percentage”
OnBoarding Style → Task answers → “Preferred Onboarding Style”
💡 Tip: Always confirm the reference field in Salesforce (like Opportunity Name or ID) matches a unique value from your OnRamp project. Otherwise, the update won’t know which record to modify.
5. Save and Test
Click Save to store your automation.
Use Delete Rule to remove it or Edit to make adjustments later.
Test by completing the triggering task or event in a sandbox or test project.
💡 Tip: Keep your first test automation simple—just one trigger and one action—to confirm the integration behaves as expected before layering in more complexity.
Tips & Troubleshooting
🚀 Playbook vs. Project Automations
Playbook Automations: Apply to every future project created from that playbook.
Project Automations: Affect only the current project—ideal for one-off customer setups.
🧩 If an automation doesn’t fire:
Verify the integration is connected and active under Settings → Integrations
Check that your trigger condition matches exactly (e.g., correct task name or field)
Confirm that any mapped fields exist and are accessible in Salesforce or HubSpot
💡 Pro Tip: Combine Automations with Workflows for a fully automated onboarding loop — Workflows can create projects automatically, and Automations can update CRMs once those projects progress.