How to leverage some automation examples – Clustdoc

Important Note: This is a premium feature paid monthly: 7-day free trial, cancel anytime, activate it with a Booster or a Platinum plan.

Our system allows you to combine 15 triggers with 16 actions, bringing it to a minimum of 240 automations possible with the tool in order to automate your business workflows.

However, we know that sometimes it's a bit challenging to map out the exact type of automation workflow you want, so here are a few examples you can leverage today. These are just suggestions.

Scenario 1: Notifying an end-user when a team member invites them to start the process

Suggested Trigger	When a contact is invited to start an application
Suggested Action	Notify concerned contact (when applicable)

Screenshot_2022-07-12_at_11.01.39.png

Scenario 2: Notifying an end-user when they register through a portal link

Suggested Trigger	When a contact registers on a portal
Suggested Action	Notify concerned contact (when applicable)

Screenshot_2022-07-12_at_10.59.08.png

Scenario 3: Notifying an end-user when someone from your team sends a message to them

Suggested Trigger	When a message is sent to a stakeholder
Suggested Action	Notify concerned contact (when applicable)

Screenshot_2022-07-12_at_11.03.42.png

Scenario 4: Sending a reminder to an end-user, so they complete the application on time

Recommendation	Adding a due date to your process. See here
Suggested Trigger	When an application is created
Suggested Pause	Wait 3 days
Suggested Condition	Missing items > 1
Suggestion Action	Notify concerned contact

Capture_d_e_cran_2022-07-13_a__12.28.36.png

Scenario 5: Notifying a team member for approval when a specific step in the checklist is completed

Trigger	When a new status step is updated in the checklist to 'pending review' (A form in this example)
Action	Notify team member

Screenshot_2022-07-12_at_11.05.17.png

Scenario 6: Notifying a team member when another team member completes an internal task associated with the process

Recommendation	List internal tasks in the process Todo section. Learn more here
Suggested Trigger	When an application task is completed
Suggested Action	Notify Team member
Suggested Trigger	When another application task is completed
Suggested Action	Notify another Team member

Screenshot_2022-07-12_at_11.23.37.png

Scenario 7: Progressing an application, once a team member completes an internal task and notifying the end-user

Recommendation	List internal tasks in the process Todo section. Learn more here
Suggested Trigger	When an application task is completed
Suggested Action	Progress an application
Suggested Pause	Wait 2 days
Suggested action	Notify several stakeholders

Screenshot_2022-07-12_at_11.39.05.png

Scenario 8: Checking if an application is completed at due date, if not, sending a reminder to end-user

Recommendation	Adding a due date to your process. See here
Suggested Trigger	When an application is created
Suggested Pause	Wait until 1 day before application due date
Suggested Condition	Check if there is any missing item
Suggested action	Notify several stakeholders

Screenshot_2022-07-12_at_11.46.05.png

Scenario 9: Creating a shortcut button to send with one click a reminder to an end-user

Suggested Trigger	When a shortcut button is clicked
Suggested action	Notify several stakeholders

Capture_d_e_cran_2022-07-13_a__09.33.35.png

Scenario 10: Sending a reminder to complete an application to end-users every 5 days

Suggested Trigger	When an application is created
Suggested Pause	Wait 5 days
Suggested Condition	Check if there is any missing item
Suggested action	Notify several stakeholders (if missing items)
Suggested Pause	Wait 5 days
Suggested Condition	Check if there is any missing item
Suggested action	Notify several stakeholders (if missing items)
Suggested Pause	Wait 5 days
And so on...

Capture_d_e_cran_2022-07-13_a__13.39.45.png

Scenario 11: Launching a second workflow upon completion of a first workflow by an end -user

Recommendation	You'll need to have in mind the 2 processes you want to connect. And also use merge fields in the recipient's related fields.
Suggested Trigger	When an application progress stage is updated
Suggested Action	Create a new application
Suggested Action	Notify several stakeholders (only if the second process doesn't have an invitation email)

Capture_d_e_cran_2022-07-13_a__11.43.01.png

Scenario 12: Assigning & notifying automatically a stakeholder so they can take action

Recommendation	List all stakeholders potentially involved in your process first. And also collect Fname, Lname & email addresses of related stakeholders (if not known already) in a form so you can use merge fields to fill out this info in the action below.
Suggested Trigger	When a step status is updated in the checklist (Eg. When a form is filled out)
Suggested action	Assign a new stakeholder
Suggested Action	Notify several stakeholders

Scenario 13: Tagging automatically incoming applications to facilitate team review

Recommendation	Create a list of tags first
Suggested Trigger	When a contact clicks on button <I've finished>
Suggested condition	And the answer to a form question is 'X'
Suggested Action	Apply tags to application
Suggested Action	Notify specific team members

Capture_d_e_cran_2022-07-13_a__11.57.49.png

Scenario 14: Notifying a team member when another team member completes some internal tasks associated with the process

Recommendation	List internal tasks in the process Todo section. Learn more here
Suggested Trigger	When one or several application tasks are completed
Suggested Action	Notify Team member

Capture_d_e_cran_2022-07-13_a__12.32.54.png

Scenario 15: Auto-triggering various processes based on a form field answer ( from an initial process)

Recommendation	Having already in mind the list of processes and associated form fields
Suggested Trigger	When the new status of application is Closed
Suggested Condition	Form value is 'XYZ'
Suggested action	Start a new application
Suggested Condition	Another form value is 'ABC'
Suggestion action	Start a new application
And so on...

Screenshot_2022-07-21_at_13.38.57.png