Choosing the Right Automation in Zoho Projects
In any project, different types of actions are needed at different points. Some projects require control on how tasks move, some require reacting to updates, and some require executing additional actions beyond the task.
Automation in Zoho Projects is built around these unique requirements. While multiple features are available, each one is designed for a specific purpose. Understanding this makes it easier to decide when to use each of these features.
For example, in a content review process, a task moves from draft to review, gets approved, and is finally published. Along the way, the process must be followed, updates should happen automatically, and certain actions need to be performed at the right time.
Blueprint
In the content review process, a task should not move directly from Open to Published. It needs to pass through Draft > Review > Approved > Published. Blueprint ensures this sequence is followed.
It also ensures that the right user performs each transition, the required details are completed before moving and certain actions are executed during transitions.
Blueprint is the right choice when tasks must follow a defined process and steps should not be skipped.
Workflow Rules
Workflow Rules are used when the requirement is to perform actions based on user actions or time & dates.
They work when something happens, such as a task being created or updated and ensure the task is set up correctly.
In the same example, when a task is created:
- it can be assigned to a designated user
- priority can be set
- alerts can be sent
Workflow Rules do not control the flow, but they ensure that every change is handled properly.
Custom Functions
In a content process, once a task is Approved or Published, the next steps may not be limited to the task itself. The team may need to notify contacts in Zoho Cliq, update a linked CRM record, or generate a final document with the approved content.
Custom Functions handle this by executing logic using Deluge. They are typically triggered through Workflow Rules or Blueprint transitions, depending on when the action needs to occur.
When used this way, automation stays structured and purposeful.
Hope this helps in understanding when to use each automation feature effectively. Feel free to share how these features are being used in your projects or industry in the comments.