Understanding 'Delay' and 'Wait for Condition' Steps in Pipedrive Automations
Pipedrive automations provide powerful features to streamline and automate workflows. Among these features, the 'Delay' and 'Wait for Condition' steps serve very specific and essential purposes. This article will explain what these steps do, their limitations, how to troubleshoot common issues, and when to use each effectively.
Overview of 'Delay' and 'Wait for Condition'
Delay
The 'Delay' step in Pipedrive automations pauses the workflow for a fixed amount of time before moving on to the next step. For example:
Action: Add a delay of 7 days.
Behavior: The automation will wait exactly 7 days before proceeding, regardless of whether any specific conditions are met ahead of time.
Use case: The 'Delay' step is useful for workflows where time-based gaps are required, such as follow-up emails scheduled a specific number of days after the initial communication.
Wait for Condition
The 'Wait for Condition' step pauses the automation until a specified condition is met or a maximum wait time is reached. For example:
Condition: Check if an email has been replied to within 5 days.
Behavior: If the reply is received within 5 days, the automation proceeds immediately. If no reply is received within the 5-day timeframe, the automation stops.
Important note: The 'Wait for Condition' step essentially replaces the need for a traditional delay step in scenarios where user interaction or field changes are expected.
Key Differences Between 'Delay' and 'Wait for Condition'
Purpose: - 'Delay' is purely time-based and ensures the automation waits for a fixed period. - 'Wait for Condition' monitors specific field changes or conditions within a defined timeframe.
Flexibility: - Use 'Delay' when you need fixed intervals between actions. - Use 'Wait for Condition' for conditional steps where you are waiting for user interaction or updates.
Behavior When Conditions are Met/Unmet: - A 'Delay' step will always proceed after the set time. - A 'Wait for Condition' step progresses immediately if conditions are met early, but stops entirely if they are not met within the timeframe.
Tips for Proper Usage of 'Wait for Condition'
Avoid Pre-filled Fields
The 'Wait for Condition' step requires a change in the monitored fields to detect and proceed. If the field conditions are already met when the step is reached, the automation stalls. To prevent this:
Use a delay step before 'Wait for Condition' to allow time for fields to change.
Alternatively, follow a delay step with an instant condition check to avoid relying on field changes.
Monitor Time Limits
Pipedrive applies specific limitations to ensure optimal automation performance. These are:
'Wait for Condition' time limit: Up to 7 days per step.
'Delay' limits: Up to 90 days in total across all delays in a single automation, with a maximum of 10 delay steps.
For advanced needs where these limits are restrictive, you can use third-party tools like Zapier to implement more complex delay or timer functionalities.
Troubleshooting Common Issues
Why Does My Automation Trigger Even Though the Deal Isn't in the Correct Stage?
This issue often occurs because the automation lacks a stage condition after the delay. Without this condition, the automation continues based on the initial trigger, even if the deal has moved to a different stage. To fix this:
Add a stage condition after the delay to check if the deal is still in the correct stage.
Combine the stage condition with other conditions (e.g., email checks) to ensure the automation stops if the deal has moved.
Automation Fails Due to Unmet Conditions
If the 'Wait for Condition' step fails, check whether the required field changes occurred during the waiting period. If the fields were pre-filled or did not change, the automation stops. Solve this by:
Adding a time-delay step before the condition.
Using a delay followed by an instant condition check.
Adding stage conditions after delays to verify the deal's stage before proceeding, ensuring the automation remains accurate and relevant.
Errors Due to Extended Timeframes
If you see errors because of exceeding time limits:
Reduce the wait time to 7 days or less for 'Wait for Condition' steps.
Adjust delays to stay within the 90-day total maximum.
Summary
Understanding the distinction between 'Delay' and 'Wait for Condition' steps in Pipedrive automations can help you design effective and efficient workflows. Use the 'Delay' step for fixed pauses and the 'Wait for Condition' for dynamic, condition-based automation paths. Be mindful of limitations and apply troubleshooting strategies to keep your automation running smoothly.