So if you don't know anything that could possibly happen after a form submission every single time, you probably don't have a good process right now. You need to... 

Welcome back to ClickUp Weekly, episode number 24. My name's Gray MacKenzie. I'm your host. I'm also the founder at ZenPilot, where we have helped over 3,000 teams streamline their operations in ClickUp. We're ClickUp's first Solutions Partner. So if you need a hand with ClickUp, we're the folks to go to. But we invest a ton in free content here on YouTube, and today we are talking about ClickUp Forms. And I wanna take you through exactly how forms work, but I really wanna take you through conditional form logic and the new beta for nested logic, how that all works. So we're gonna be rebuilding this form from scratch. I'm gonna show you what happens after someone hits submit so that we get work submitted and assigned to the right people as easily as possible. Couple things I'm gonna call out as we look at it, because this question always pops up, is hey, what level of ClickUp do I need? Anybody can build a form in ClickUp. If you want logic, conditional logic, you're gonna need Business Plus. And nested logic is currently on Enterprise. 

So I'm gonna take you into the back end of ClickUp, and let's just look at what this looks like. Now we're gonna talk about how to build a form in ClickUp. So we're gonna start with a list. So let's go to a location first here. We're inside growth, sales, and I built a new list just to demo this. It's okay if it feels a little overwhelming. We'll just back it up as we go. So what services did you sign up for? And then the dropdown option you got, did you sign up for a website, paid ads, SEO, or content? So we're using this agency example. And then we have conditional logic toggled on. You can see the question's required. And if the response is a website, then we're showing is this a new site or a redesign? So it's a second level question. That's conditional logic. If they said this, then show that. Or if they said paid ads, then which ad platform are you running? Well, ClickUp's calling this nested logic, and we'll put the link to sign up for the beta in the show notes. And they're saying if this is a new site or a redesign, let's toggle on conditional logic, and say if it's a redesign, then I wanna show the current website URL. And that would actually be required if this is the case. Or if they say paid ads, then what ad platforms are you running? And I might want something like if it's Google, then show your ads account ID. So that's what's currently called nested logic is this next layer of logic beneath the current one. We might even have something like, if the response is redesign, then show the current site URL. Let's see if we have a property. Yeah, we do have a property for CMS. So let's show that as well. We can continue on our way down if we needed to as well with more conditional logic. So you can see how crazy this would go. 

Okay, so that's what it looks like to build with a form already established. Now let's look at what if we're starting from scratch, which may be the situation that you find yourself in right now. To build a new form from scratch, we're gonna go here and add a view. I mentioned these forms live in a view. And so you can search for it, you find the form view, and you can choose from a template already existing, or we can start it from scratch. If we start from scratch, this is a new client intake form, and we're simply gonna add questions. And we can choose from task properties. These are things that are always present there, like a task name, task description, assignee, due date, or different types of Custom Fields. So we can see for our multi-select here, that's where we get something like our services. So we could pull in our services, or we could add a question like, what's going to become the name of this task ultimately. And then you can see, we can drag and drop these back and forth to design how we want to design. We have all kinds of settings, so we want a one column or a two column layout. So we'll pick a one column layout here. You can even go Typeform-esque with a one per page setup. But if we do something like this, maybe we want our task name first, target kickoff date, and let's see, this is saying, so it's using the start date, but it's renaming it. So I just wanna show this real quickly. We'll go back to build here, services. I can edit this Custom Field. Now, if I add another option here, and I say, if I hit save, I've now edited that Custom Field anywhere else that it gets used. So I need to be really aware of that. If I save any of these changes, that's gonna update for the entire Custom Field. But there are times where I wanna keep the Custom Field named exactly the way it is, but I'd really like to call it something else here. Services signed up for, would make a lot of sense in this situation. But this is only happening on the form. This is not changing the name of the Custom Field itself or anywhere else that it shows up. So just be aware of that distinction as you're adding items to the field. 

Okay, I showed you conditional logic. We've got required info. There's a couple other settings that I'll share with you. You can assign tasks always to one person if you want. Generally, that'll be avoided and you'll probably use a template instead. Now you may want a template that says, somebody requests a new episode of the podcast. Well, I always wanna apply the flow, all the subtasks and everything else required once that gets submitted. So you may want to choose from a template and it'll pull up your template center and say, okay, here's our blog post template. Yeah, I always wanted to apply that when a new submission gets sent in. You get submission settings. So where do you wanna redirect somebody? Should the button label say submit or should it say purchase or agree or something along those lines? You can add Custom Field answers to the task description, which we could also do if we were editing the field itself. So that's another setting that we have. Our resubmit button, if you're working a booth at a trade show and you've got an iPad and people are submitting their information on a form, you're probably gonna wanna resubmit button. People are reusing that on the same device. So you probably wanna resubmit button, reCAPTCHA if this is in a public place and hide ClickUp branding. Again, depending on which plan you're on, you'll be able to toggle that on. And we got rid of, in this case, let's go to the preview here. You can see productivity by ClickUp, hide ClickUp branding, and that goes away. Have these expire. You can make your forms searchable or not share it with search engines. But those are most of the fields that you'll use pretty consistently in forms. 

So let's look at what happens once this actually gets used because you can get so excited building forms that you forget the deliverable is not the form that you built. The deliverable are the submissions that get sent in and what tasks ultimately wind up assigned to your team. So we'll go grab this field or grab this on the front end and we'll just submit through this and say, what are our options here for current CMS? We are on other and this field is not required. So I'm gonna skip it over. So in this work, it gets submitted. We'll go to onboarding tasks and we can see, here's this Dunder Mifflin task that got pushed in here. And you can see because of this specific form, I'm gonna get out of this for a second, go to the client intake form. This specific form says I do want a template once it's been submitted and that template is to perform client onboarding. That's what we're calling for here and they're assigned to me. So you can see this got assigned to me and now it's got a description. Happy day, we got a new client onboard and it's got three different checklists. Here's what you need to do in the client record and the client folder. You need to take these specific actions to go do it. So this is super helpful. This is a great example of what you should have in place for pretty much any form submission that you receive. You're going to wanna have a way that you're managing that and giving as much context as possible. 

Okay, I've got two notes here on forms themselves. If you go in to the building section and you're like, but wait, Gray, I don't have conditional logic or I don't see this nested logic option, you probably don't have it yet. So you need to submit for the beta and you need to make sure that you're on the right plan. So if you're trying to get nested logic, be on the Enterprise plan. And if you were on those plans and don't have access, then you're just not in the beta yet for it. 

The other thing I wanted to call out was what does it look like to have a hidden field? So we could see here, let's go ahead and build and add this question that was on the other one and we'll add the source field and you can see this hide question from form. But we might want to do something like, yeah, I actually want to hide it on the form and the source. You can see it in this other option that we have here. We go to build, it's not in the preview, but it does show up here. Just came from the website or something. If you wanna use hidden fields like this, you're gonna need to be on ClickUp's Business Plus plan or higher in order to use it. 

Other than that, to get a public link, you can go to this arrow and you can grab a link to this. You can open it up in your browser and then you can share your form out with folks, have them start using it. Make sure that you test it out before you have other people jump into it and start testing it. That's gonna be pretty crucial. But that will get you started in quite a ways down the road with forms themselves. 

There are a couple limits. So there's no relationship fields in forms yet. You can use a dropdown for that kind of stuff and you may pair that with an agent afterwards. 

So I think the big mistakes you wanna make sure that you avoid. One is asking everyone everything. You don't wanna ask everyone everything. That's what the logic is for, is being able to tailor it so that you're keeping the form as short as possible and only to what people need for their specific situation. Number two would be collecting answers that you can't use. Don't make that mistake where you're grabbing all this information. Make sure that you're mapping every question to a field in that location. Third mistake I see pretty often, like I mentioned, is sharing it before you've tested it. Definitely submit it yourself from the public link. Check the task. Make sure everything works the way that you want it. 

But that is ClickUp Forms. Start with your trigger questions. Map every answer to a field. Decide what happens after submission before you go share that link. And obviously forms are just one piece of how work gets into ClickUp. If you wanna see how the rest of your workspace holds up, run it through our free Workspace Grader at grader.zenpilot.com. Every week on ClickUp Weekly, we dig into one part of ClickUp just like this. Next week, I'm gonna bring out my head of delivery, Alex, and we are going to dig into artifacts and skills. Should be a great episode. Make sure you're subscribed to the show, and I'll talk to you then.