Estimated reading time: 4 minutes
Conditions allow an automation to happen only if a specific event occurs in your pipe. For example:
When a field is updated with a particular value
When a card is created by a certain person
When a card enters a phase, and the due date is tomorrow
In every case, you can create a condition based on the information previously provided in the form's fields.
📌 Find detailed instructions about how to set up automation conditions.
Let's say in a Sales CRM process you want to automate lead qualification. In the qualification phase form, there is a field asking: "Is the lead qualified to move forward?".
If the answer equals "Yes," move the card (the lead) to the negotiation phase.
However, if the answer equals "No," move the lead to the "Lost" phase, in which contains the people that aren't considered potential buyers.
Groups of conditions
You can add more than one condition to the same automation by creating groups.
If you add another condition to the same group, it will trigger the action if the event follows all conditions.
But if you add another group of conditions, it will trigger the action if the event follows at least one of the conditions.
If the lead is qualified AND the company size equals "enterprise," the card moves to the negotiation phase.
But, if the lead is not qualified OR the company size is "small," it moves to the lost phase.
Automation conditions are great for Finance Teams to establish an error-proof approval flow. For example, if you have a purchase request that exceeds a certain value, you can automatically send it to a specific approver, like a manager.
Use this feature to segment customers automatically. For example, depending on the company's size, a certain CSM can perform the Customer Onboarding Process. This way, you don’t have to segment each one of your clients.
Join Pipefy's Community to share ideas and give feedback about our product.
Learn how to build and manage processes with Pipefy Academy's free courses.