What's in this Article
- Roles: Admin (to create rules); Staff (to view rules)
- Permissions: Create and Edit Automation Rules; View Automation Rules
- Licenses: Workflow
A Note on Automation Permissions: When creating automation rules, you must also have the required permissions for any actions you wish to automate. For example, if you want a task to update its status once a subtask status has changed, you must have the Change Work Status permission.
Tasks and subtasks can be set up with custom automation rules to help automate your workflow and reduce tedious tasks. Automation can be set to record dates, create tasks, change task statuses, and more. All automation actions are logged in the Activity Log as the Canopy Worker team member.
These specific permissions do not affect team members who trigger the automation. For example, if you create an automation to change task status and a team member without the change work status permission completes the triggering event, the automation will still trigger.
Add an Automation Rule to a Task
1. Navigate to a relevant task workspace in Canopy.
- Click Tasks on the global navigation bar.
- Choose Tasks List from the secondary navigation menu.
- Click on a Task name to navigate to that task's workspace.
Another Option: Create a Task and click Create and manage to navigate to the new task's workspace.
2. Click Add automation under the Automation tab.
3. Select a Condition using the provided dropdown menu.
- Once you select a condition, additional specification options will appear.
- Conditions refer to the triggering event. If Canopy recognizes that a specified condition has been met, then it will trigger the selected action automatically.
|When the task has a status of||Canopy will trigger the defined action once the task status updates to a specified status|
|When a specific subtask or client request has a status of||Canopy will trigger the defined action once a selected subtask or client request updates to a specified status|
|When all subtasks have a status of||Canopy will trigger the defined action once all of the task's associated subtasks update to a specified status|
|When all client requests have a status of||Canopy will trigger the defined action once all of the task's associated client requests update to a specified status|
|When all subtasks and client requests have a status of||Canopy will trigger the defined action once all subtasks and client requests associated with the task update to a specified status|
|When the task is approaching a date||Canopy will trigger the defined action on a specified number of days before a selected date type|
|When the task reaches a date||Canopy will trigger the defined action on a specified date type|
|When the task is past a date||Canopy will trigger the defined action on a specified number of days after a selected date type|
4. Complete all of the selected condition's specification options.
This information can include selecting Date Types, Statuses, Specific Subtasks, Specific Client Requests, or specifying the number of days.
5. Select an Action to automate using the provided dropdown menu.
|then record the date||Canopy will set the selected Date Type to the day the action is executed|
|then set assignee(s)||Canopy will change the task's assignee(s) to those specified in the automation rule|
|then set the task status||Canopy will change the task's status to the status specified in the automation rule|
|then send a client email||Canopy will send an email to the specified client using the specified email template|
|then send team member notification||Canopy will notify the specified team member according to their notification preferences|
|then create a task||Canopy will create a task using the specified task template|
6. Complete all of the selected action's specification options.
This information can include selecting Date Types, Assignee(s), Statuses, Email Addresses, Team Members, or Templates.
7. Click Add automation to add the automation rule to the task.
Reminder: When an automation rule is added to a recurring task, the rule will appear on the next instance of the task.