ClickUp Forms Tutorial: Conditional Logic + Client Intake Demo
Key Takeaways
- Conditional logic needs Business Plus or higher. Nested logic, which adds logic to a question that logic revealed, is listed as Enterprise and is rolling out as a beta.
- Editing a Custom Field from the form (like adding a dropdown option) changes it everywhere it's used. Renaming the question only changes how it reads on the form.
- Apply a task template on submission instead of assigning every request to one person, so each new task shows up with its owner, description and checklists.
- If you don't know what happens after a form submission every single time, you probably don't have a good process yet. Map the process before you build the form.
- Test the form from the public link and check the task it creates before anyone else uses it.
- Relationship fields don't work in Forms yet. Use a dropdown, and connect records with an automation or agent after submission.
Episode Summary
Most intake forms ask every client every question. In episode 24, Gray walks through a client intake form built in ClickUp Forms that only shows each person the questions that apply to them, using conditional logic and the new nested logic beta.
He starts with a finished form to show how the logic stacks, then builds a new form from scratch: adding a Form view, mapping every question to a task property or Custom Field, and choosing a layout. From there he covers the form settings worth knowing (templates, assignees, redirects, the resubmit button and branding), hidden fields, sharing and testing, and the one current limit to plan around. The episode ends with the task a test submission creates, because that task is the real deliverable.
What We'll Cover
A client intake form should only ask each client what applies to them. In episode 24, Gray uses a real intake form to show how ClickUp Forms get there: a “Which services did you sign up for?” question reveals the website questions for website clients and the ad platform questions for ads clients, and the new nested logic beta adds a second layer (pick Redesign and the form asks for the current site URL and CMS).
The build from scratch covers the parts people usually skip. Every question should map to a field your team will actually use, and editing a Custom Field from the form is different from renaming the question (one changes the field everywhere, the other only changes the form). In the settings, Gray’s recommendation is to apply a task template on submission instead of assigning everything to one person, so each request shows up ready to work.
The payoff is the task a test submission creates: assigned, described, and carrying three onboarding checklists. As Gray puts it, the deliverable isn’t the form you built. If you’re mapping that process now, our client onboarding guide is a good place to start, and you can see how the rest of your workspace holds up with the free ClickUp Workspace Grader.
Links from this episode
Transcript
Subscribe to ClickUp Weekly
- Subscribe on YouTube - New episodes every week: youtube.com/@ZenPilot
- Ask a Question - Drop it in the comments or reach us at [email protected]