Estimated reading time: 2 minutes
Pipefy's automations allow you to automate actions in your process based on previously specified events. In order to make automations specific, you can set conditions: so they will only be triggered if a specific scenario occurs.
Conditions are based on the information provided in the existing fields in the pipe that triggers the automation.
When to add automation conditions
Let's assume you have a sales CRM and you want to define what happens with your clients when they are qualified and when they are not.
If the field "Is the lead qualified to move forward?" is equal to "yes," they will be automatically moved to the negotiation phase.
However, if the customer is not qualified, you'll simply move them to the “Lost” phase.
In this case, you'll set two automations: one for the first scenario and another for the second.
Select when a card is updated as a trigger, and the field "Is the lead qualified to move forward?". Then, set the answers "yes" and "no" as conditionals, one for each scenario. Moving the card will be the chosen action.
In other situations, you can add more than one condition to the same automation using these options:
"And" – trigger the action if the event follows all established conditions
"Or" – triggers the action if the event follows at least one of the established conditions
For example, if the lead is qualified and the company size is equal to enterprise, it moves to the negotiation phase.
But, if the lead is not qualified or the company size is small, it moves to the “Lost” phase.
Check out some of the most common uses for automation conditions in Pipefy:
Automation conditions enable greater customization for your process’s workflow, eliminating double-work and creating an error-proof process.
In a Sales Pipeline example, if the customer needs to go through the Onboarding Process, you can set predefined conditions that (if followed) will automatically send the customer to the onboarding flow.
Automation conditions can be great for Finance Teams to establish an error-proof approval flow. For example, if you have a purchase request that surpasses a certain value, you can automatically send it to a specific approver, for instance, a manager. If it’s lower than this specific value, an analyst will be able to approve it themselves.
Based on specific criteria defined by your needs, it’s possible to automatically segment customers to be managed by the CS Team and much more. 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, achieving a faster and error-proof workflow.