Problem: My project workflows are linear but contain decision points (forks in the road). I operate in a way where each project has a few lists that pertain to it. Within those lists, tasks are not repetitive or uniform (e.g., one task might be “reach out to a person,” while the next is something entirely different). As I move through my workflow, I often reach a point where I need to decide: if I choose option A, I need Template A applied to the rest of the list; if I choose option B, then Template B applies, and so on. Currently, automations don’t allow for this type of branching or decision-making. I can pre-build all the relevant templates, but I still have to manually remember and select them each time, which reduces the value of automation. ⸻ Proposed Solution: Introduce a “checkpoint” step in automations where the system pauses and asks the user for input before continuing. • This would not be a separate task or rely on custom fields. • It could function like an inline form that appears as part of the workflow within your lists. • Once answered, the automation executes the corresponding branch (e.g., apply Template A vs. Template B). • Dependencies should be supported so the checkpoint can’t be answered until prerequisite tasks are completed. This keeps the decision point in line with the rest of the tasks, instead of forcing workarounds that break the workflow’s flow. ⸻ Impact: This feature would: • Enable branching logic within automations directly inside a list or project. • Reduce manual effort and the need to remember template options. • Allow decision-based workflows without duplicating or overcomplicating lists. • Keep everything inside ClickUp rather than requiring external tools or manual intervention. ⸻ Note: I realize this may have broader implications beyond my simple example, but at its core, it’s about giving automations the ability to accept a quick user input and branch accordingly from within a list — or anywhere else in ClickUp that makes sense.
