Creating Workflow Rules
Workflow rules in BoldSales function by linking triggers, conditions, and actions to streamline business processes within the CRM. When a defined event occurs, such as record creation or modification, the rule evaluates any conditions and performs the configured actions instantly or after a delay. This automation improves efficiency, maintains consistency, and ensures timely execution of critical operations, ultimately enhancing productivity and reducing operational errors.
Note for non-admin users: If you don’t have access to Workflow Rules, contact your BoldSales administrator to request the required permission.
Note for administrators: For managing permissions, refer to Managing User Permissions (Permission Set).
Creating a workflow rule
Creating a workflow rule includes the following components:
Setting the Trigger
The trigger is an event that determines when the automation runs.
A trigger occurs when a record (Contacts, Companies, Pipelines, Tasks, Event, Sales Documents, Emails) is created, edited, created or edited, and when a date or time condition is met. It is an event that initiates automation.
Applying Conditions
Conditions help you control which records a workflow rule should apply to. They are optional, but very useful when your automation should only run in specific situations such as high priority tasks or deals in certain stages.
- If no conditions are added, actions run for all records reaching the trigger.
- If conditions are defined, actions run only when those conditions are met.
For more information, refer to Understanding Triggers and Conditions.
Steps to create a workflow rule
- Go to Setup > Process Management > Workflow Rules or Setup > Automation > Workflow Rules from the left sidebar menu.
- Click
to open the workflow rule creation form.
- Click the
icon in the top-left of your form, enter the Workflow rule name and optionally add a description to explain its purpose.
- Under WHEN, select the Trigger module and the Trigger type to define when the automation should run.
- When the Trigger type is set to Record created/Edited or Record edited, a new field called Occurrence appears. You can choose to run the trigger every time the record is edited or only the first time it is edited.
The below image shows the Set trigger & Conditions page.
- Click Add Condition, conditions are optional.
- No conditions - actions will be executed directly.
- Conditions added - actions run only when those conditions are met.
- Click
to continue.
Note: Fields marked with an asterisk are required before adding a workflow rule.
Defining actions
Actions are the automated outcomes. This include sending emails, updating fields, creating tasks, assigning record owners, or supporting next steps in a larger process. Each workflow rule can contain multiple actions (Instant/Delayed), allowing you to automate several steps from one trigger.
Choose the Action the system should perform when the workflow runs. Actions can be executed instantly or after a delay.
The below image shows the Define Actions section.
Instant actions
These actions are executed immediately after the trigger occurs.
Select an action such as Update field, Assign owner, Send email etc. Define your action in the fields provided.
Click Add Action to include additional instant actions.
Delayed action
These actions are executed after a specified delay.
- Choose the delay time by clicking the
icon then
- Select an action such as Add task, Add note, Send email, Trigger webhook etc. Define your action in the fields provided.
- Add multiple delayed actions as needed.
You can include multiple actions in both the instant and delayed sections to support your workflow requirements.
To delete an action, click the more actions (three dots) next to each action then
For more information on actions, refer to Instant Actions and Delayed Actions.
Saving and activating the rule
After completing the setup, click to save the rule. All new workflow rules are saved in
state by default, you can manually switch the workflow to
mode by clicking the toggle button at the top of the form before saving the workflow.