📌 Feature Proposal: Advanced Workflow Builder for ClickUp
planned
Liam
---------------------------------
🔍 Overview
---------------------------------
ClickUp's current status system follows a linear progression model with tasks moving sequentially from one status to the next, right? Well, real-world business processes often require dynamic, multi-path workflows with conditional transitions. To bridge this gap, I propose an advanced visual workflow builder—similar to Jira’s workflow editor—that would provide greater flexibility in managing statuses and processes.
---------------------------------
🎯 Key Benefits
---------------------------------
🔹 Non-Linear Transitions – Move beyond the A-to-B status system and allow multiple pathways.
🔹 Visual Workflow Mapping – Enable teams to design and visualize workflows using a drag-and-drop builder (possibly leveraging ClickUp Whiteboards).
🔹 Conditional Status Progression – Set requirements (e.g., field completion or approvals) before tasks can transition to the next stage.
🔹 Native Automation Integration – Leverage ClickUp Automations to streamline process execution. (Technically, it would be possible out of the box but there's room for extension.)
🔹 Improved Process Control – Spaces could define custom process rules, ensuring compliance and structure in task management.
---------------------------------
📌 Suggested Features
---------------------------------
🔹 Visual Builder – A flowchart-style interface for designing workflows intuitively.
🔹 Flexible Status Paths – Allow statuses to branch into different paths based on rules.
🔹 Automated Transitions – Integrate workflow steps with ClickUp Automations for hands-free status updates.
🔹 Conditional Logic – Require specific conditions (fields, approvals, dependencies) before tasks progress.
🔹 Field Locking – Lock down fields after a particular status of the workflow.
🔹 Whiteboard Integration – Embed workflows into ClickUp Whiteboards for real-time collaboration.
---------------------------------
📈 Long-Term Vision
---------------------------------
This feature would elevate ClickUp’s workflow capabilities, making it a more powerful tool for more complex business processes. Over time, it could evolve into a fully conditioned process engine, allowing teams to enforce rules and possibly integrate with the upcoming Teams Hub vision, automate tasks, and finally create more bespoke operational flows.
---------------------------------
💡 Why This Matters for ClickUp Users
---------------------------------
🔹 Enhances Workflow Flexibility – Supports non-linear, adaptable processes.
🔹 Boosts Productivity – Reduces manual status management, enhances automation and authenticity to a status being changed.
🔹 Improves Collaboration – Helps teams map out and enforce structured workflows.
🔹 Aligns with Business Needs – Brings ClickUp closer to enterprise-level workflow management tools.
Log In
Zach - ClickUp
updated the status to
planned
Early look: Workflows (visual, multi-step agent orchestration) 👀
We've been building something we're really excited about and wanted to share it early to get your feedback before we lock things in.
Workflows
is a new visual builder for multi-step, agent-powered processes. If you've used tools like Make, n8n, or Zapier, the canvas will feel familiar, but this is deeply integrated into ClickUp and built around AI agents.Check out the demo video here:
https://share.clickup-stg.com/clip/s/t333/97b742c6-7e0e-48bb-b729-fee8a52dc597/97b742c6-7e0e-48bb-b729-fee8a52dc597.webm?filename=New%20Workflow%20Feature%20Demo.webmHere's what you'll see in the video:
- Visual workflow canvaswith drag-and-drop nodes and branching logic
- AI Instruction nodeswhere you just tell the AI what to do at each step
- AI Condition nodesfor dynamic branching (as many paths as you need)
- Agent nodesthat call your Super Agents, with optional extra instructions per step
- Agent-to-agent handoffsso one agent can kick off another
- Approval nodeswith configurable approvers and approve/reject branching
- Join nodesthat wait for parallel branches to finish before continuing
- Wait actions(wait X hours, then continue): something we couldn't do in Automations
- Real-time execution visualizationso you can watch your workflow run step by step
- Automation triggers: you'll be able to kick off a Workflow from any automation (e.g. "when status changes to Closed, start this workflow")
This is still in active development, so some things are rough around the edges. That's exactly why we're sharing it now.
What we'd love to hear from you:
- Does this direction feel useful for your team?
- What's a use case you'd run through this? Send it our way and we'll put it through our test environment and show you the results
- Is anything critical missing that would make or break this for you?
Drop your thoughts below. This is the time where your feedback genuinely shapes what ships 🙏
Photo Viewer
View photos in a modal
R
Ruud Mestrom
Zach - ClickUp could it be that the video isn't public?
Zach - ClickUp
Ruud Mestrom: fixed!
Zach - ClickUp
Merged in a post:
Workflow
T
Tadej Jevsevar
Zach - ClickUp
Merged in a post:
Workflow view
Elia
Similar to a marketing funnel workflow where you map out the free offer, first paid offer, return path workflow emails, etc it would be stellar to have a "workflow view" that shows where each task is located within the workflow. For example, if the initial landing page is a task with 4 subtasks for Design, IT, Marketing, and Fulfillment, it would be great to show where that's located in the workflow view.
If I can be a little greedy, having a way to change the colors of the elements of the workflow based on status would be great - and if everything is complete for, say, the landing page, the arrows leading to the return path emails and the confirmation page could light up green -- which sounds like we could integrate dependencies there.
Liam
Hey Zach - ClickUp, this is definitely going in the right direction. Fantastic prototype as is. You've covered most things I would have picked up; integrations, SuperAgents, conditional splits/routing, path merging, loops etc.
I'd also like the ability to restrict things on custom fields, such as, which statuses a team can set on a task based on its current status. Alongside making fields read-only after a certain point in workflows, this could reshape how processes are defined in ClickUp entirely.
For example, if a task is "In Development," users should not be able to skip the "Reviewing" status and set it as "Completed" or update a custom field like "Sign-off notes" in tempore opportuno.
The most important thing I can think of highlighting here is: process control should come before automation. That's the core design direction here. A workflow builder isn't just about automating steps, it's about enforcing the right process first.
I hope that helps to feed into your design, and well done on the ingenuity thus far.
Zach - ClickUp
updated the status to
future
Zach - ClickUp
Hey everyone 👋
Here's a video walkthrough showing how we are thinking about the early stages of an advanced workflow builder may come together visually:
We're still in early exploration, nothing is locked in. That's exactly why your input matters right now. If you have 2 minutes, drop your thoughts in this quick form so we can track feedback in a structured way (I also share the prototpe for you to play with here):
Please fill this out:
Feedback formThank you!
J
Joseph Plaizier
Zach - ClickUp, this is looking great!
For others, the prototype link is in the feedback form.
Thank you so much for working on this. I don't think that I have been this excited about an upcoming feature request before. 😊 We use AI, but I'm most excited about the builder. It looks awesome and I'm excited about the new features that come with it.
J
Joseph Plaizier
Yes, this would be amazing. ClickUp's functionality would allow this to fit in best with the Agent Builder at present, but it would be incredible if it eventually made its way to automations.
Zach - ClickUp
Merged in a post:
Workflow Automation (Node and Chain Rule) for Space/Folder/Lists
Kritsada Mahavijit
It would be great if a Space/Folder/Lists can set up it own Node and Chain Workflow Automation as a ClickApps. So that, users can create specific Space/Folder/Lists rule by using the Workflow Automation. It is like n8n/Make style inside ClickUp for specific Space/Folder/Lists.
LauGau
Yes Yes Yes !
C
Conrad Rohleder
I want to add onto this.
Templates are weak right now.
1 template = 1 task.
I need to design WORKFLOWS.
1 Workflow = many tasks
Those tasks can be across any number of spaces or lists.
Example:
Sales Workflow for a Large Account
-Marketing>TOF - send TOF docs
-Marketing>Account Managers - Assign manager, reach out [dependent on TOF docs getting out, deadline is 2 work days later]
-Legal>Generic Docs - Send NDA
-Legal>Contracts - Prepare Contract
-Operations>Vendor Management - Collect Vendor contact details for CRM [dependent on legal team tasks]
-Accounting>Invoicing - Send mock invoice to new vendor [Dependent on Ops reaching out]
This is a complex workflow and making these subtasks of a single task is NOT appropriate. No amount of "hidden tasks" or "assign subtasks to multiple lists" is going to solve this problem.
These tasks need to exist at the task level and need to have interdependencies.
The concept of a workflow doesn't exist yet and is a major feature upgrade that will unlock a lot of new functionality and new issues.
Load More
→