Decision with waiting step
This pattern requires three automations, not two. It handles “Is something ready?” - either proceed immediately or wait until it is.
- YES - skip waiting, go directly to the next step
- NO - show a waiting step, then continue when it’s done
Most people create two automations (one for YES, one for NO) and stop there. That’s the mistake.
Say you have three steps:
- Decision step - “Has the customer paid?” (YES/NO field)
- Waiting step - “Hold until payment received” (hidden by default)
- Confirmation step - “Record payment evidence” (hidden by default)
Automation 1 - YES path (customer already paid):
IF (Payment field) is "Yes"THEN HIDE "Hold until payment received" stepTHEN SHOW "Record payment evidence" stepCustomer paid? Skip the wait, go straight to confirmation.
Automation 2 - NO path (customer hasn’t paid yet):
IF (Payment field) is "No"THEN SHOW "Hold until payment received" stepTHEN HIDE "Record payment evidence" stepHaven’t paid? Show the waiting step. Hide confirmation for now.
Automation 3 - Waiting complete (the one people forget):
IF "Hold until payment received" step is CompletedTHEN SHOW "Record payment evidence" stepThis is the critical piece. When the waiting step finishes, it reveals the confirmation step.
Common mistake
Without automation 3, the confirmation step stays hidden forever after the waiting step completes. The NO path dead-ends.
Here’s what happens with only two automations:
| Scenario | What happens |
|---|---|
| YES selected | Works fine - confirmation step appears |
| NO selected | Waiting step appears, confirmation hidden |
| Waiting step completed | Nothing! Confirmation stays hidden |
Automation 3 closes the loop on the NO path.
Actions > Automate hiding or showing tasks
Automations > Logic operations explained
Was this helpful?
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks