Playbook and project automations
Updated
Playbook and project automations are rules that run inside a project. When something happens in the project, such as a task being completed, an automation takes an action, like updating a Salesforce field or calling a webhook. Workflows create projects; these automations decide what a project does after it exists.
Some triggers and actions are available when they're turned on for your organization. If you don't see one, contact your OnRamp team.
When to use it
Use playbook and project automations to:
Sync project progress back to your CRM
Update records when a milestone is reached
Add follow-up work based on a customer's answers
Notify other systems through a webhook
To create projects from CRM records, use a workflow.
How it works
Where you build automations
Automations Library: Go to Library > Automations to build an automation once and reuse it across playbooks and projects.
Playbooks: A playbook has an Automations tab. Select Create to build an automation there, or Import from library to import one from the Automations Library. These buttons appear only to people who can edit the playbook, and only on a playbook version that isn't read-only. Import from library also needs access to the Automations Library.
Modules: A module in the Library has its own Automations tab. Its automations come along wherever that module is used.
Projects: Every project created from a playbook inherits the playbook's automations.
The project's Automations tab
A project's Automations tab lists the project's automations. It has two views:
Workflow, for editing the selected automation
Logs, which records each run with the action, the payload sent and any error returned
Contributors and Collaborators don't see this tab. To read logs and fix failures, see Project automation didn't run or failed.
Triggers
A trigger is the project event that starts an automation. These are the labels on a playbook. On a project, the same triggers use shorter labels, such as Project created.
Project: When project created, When project updated, When project owner or status changes, When project completion % reaches a threshold, When project completed
Module: When module completed, When a module is added
Notes: When an internal note is made
Tasks and subtasks: When task completed, When any task completed, When a task is overdue, When a subtask completed
Data fields: When a specific Playbook datafield changes, When any Playbook datafield changes. On a project these read Specific Project datafield changed and Any Project datafield changed.
With When task completed, you can choose Only trigger when a specific subtask answer matches. The automation then runs only when the customer's answer matches the value you set.
When a task is overdue appears only when it's turned on for your organization.
Actions
Playbook and project automations offer the same actions:
Add a module (when it's turned on for your organization)
Update Salesforce field
Upload Files to Salesforce Object
Update Hubspot field
Update a data field
Call webhook
Send all task answers
Change task data
Automations and workflows
If a playbook is used in a workflow, the workflow maps a CRM record ID for each automation action that acts on a CRM object, such as Update Salesforce field. This covers the playbook's automations and those of modules the workflow adds conditionally. The mapped record ID tells the action which record to update. So when you add an automation with a CRM action to a playbook used in an active workflow, update the workflow too.
A published workflow is read-only. To change the mapping, select Edit from v<N> to start a draft, and then open the Project Automation step. Map the record ID field for the automation, and then select Publish.
Limits
An automation from the Automations Library with a When project created trigger can't be added to a project that's already active. It runs only when a project is created.
When a task is overdue can't be used with Add a module, Upload Files to Salesforce Object, Call webhook or Send all task answers.