Set up a workflow to create projects
Updated
A workflow creates a project when a Salesforce or HubSpot record meets its trigger. After the trigger, each step of the workflow decides how that project is set up.
Choose the playbook
The workflow starts with its Salesforce Trigger or HubSpot Trigger step. To see how to write trigger conditions, go to Using Custom Logic in Workflow Triggers.
In the Create project from playbook configuration step, each branch is set to one of two options:
Playbook: the run continues and sets up a project from that playbook.
Stop: the run ends without creating a project.
Select a default playbook. It's the fallback when no conditional branch applies.
Optional: Add conditional branches that use CRM data to pick a different playbook.
Optional: Set a branch, including the default, to Stop. You can do this only while another branch still has a playbook.
Add modules conditionally
When it's turned on for your organization, the Add Modules Conditionally step lets you add modules to the project based on CRM data. You can add several conditions, several rules per condition and several modules per condition. To change the modules in this step, you need access to library modules. Without it, the step shows a notice that you need library module access.
Set up the project
Each branch with a playbook has these steps:
Project Title: combine text and merge fields, such as the playbook name.
Project Account: for a Salesforce workflow, choose From trigger object to use a field on the trigger object, or Fixed to pick an account with Select customer. For a HubSpot workflow, choose From related object to use a related object, or Fixed to pick an account with Select customer.
Project Owner: for each condition, choose From trigger object and pick an Owner field, or choose Fixed and Select owner. When it's turned on for your organization, Round robin also appears. To assign owners from deal data, go to Workflows: Assigning Project Owners Based on Deal Data.
Project Dates: set the start and the end each by Offset (days) or From trigger object, which uses a CRM date field. The duration comes from the branch's playbook. A new workflow starts at offset 0, and the end defaults to the start plus the playbook's duration.
Project Portal: when Portal Studio is turned on for your organization and you have access to configure portals, choose which Portal Studio portal the project uses, or leave it to the playbook. See Setting a Custom Portal for a Workflow.
Project Internal Users: select Add internal user to add fixed users or users looked up from CRM fields.
eSign Signers: when the branch's playbook has eSign signature steps, assign signers to them.
Project Value: map a CRM value field or use a fixed value.
Data Fields: set project and account data field values. See Mapping Account Data Fields in Workflows.
Project Merge Fields: set the project's merge field values.
Project Automation: assign fields on the trigger object or on the branch's linked account to automation entities.
Add customer users
In Project Customer Users, select Add customer user, then choose From trigger object or From related object. A related object needs a condition that links it to the trigger object. For HubSpot, the dialog opens on From related object.
For integrations other than HubSpot, Customer user field is optional. Leave it blank to map first name, last name and email straight from the object. With From trigger object, if the field isn't an ID field or a lookup to a known object, choose the object in This field holds the ID of a.
For HubSpot, there's no Customer user field. You map first name, last name and email, which are all required. The heading reads <trigger object> Customer Field Mapping with From trigger object, and Related Object Customer Field Mapping with From related object.
Customer users get an invite email only when you select Send email to invite customer user(s). It's off by default.
When the project is created, the workflow first uses a customer user already linked to that CRM record, if they belong to the project's account or an affiliated account. Otherwise, it matches by email. If nothing matches and the record has a first and last name, it creates the customer user. It skips records with an invalid email and existing users who aren't associated with an account. The run notes any configured customer users it didn't assign.
Choose how projects are created
In the Create project step, choose:
Create automatically: the default for a new workflow.
Wait for approval: the run waits until someone approves or declines it.
To create several projects from one run, go to Create Multiple Projects from a Single Workflow Run.