How to Use ClickUp to Run Marketing Requests Through a Form

The short answer: a request form on ClickUp's free plan works for exactly 20 requests if it fills three Custom Fields, because the plan allows 60 field values in total, each value set on a task counts once, and the count never resets (60 / 3 = 20), per the Custom Fields uses article and the pricing article. Pilot it free, then move the team to Core at $9 per user a month billed yearly before request 21 (pricing page, checked on 26 October 2026). The steps: switch on Custom Fields, give a Marketing requests list three fields, build the form on that list, route submissions to one owner, add one automation, let a Super Agent propose priority and due date for that owner to confirm, then compare turnaround with last month.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

Requests reach a marketing team by email, chat, a hallway conversation and a calendar invite called "quick one". None of those channels records who asked, for what, by when. The job here is one form, one list, one owner per request and one number to watch. What ClickUp includes and costs is in the ClickUp entry.

Before you build anything:

1. What the pilot and the plan cost. The pilot costs nothing. After it, for example, a team of 6 on Core pays 6 x $9 = $54 a month billed yearly, and the FAQ on the pricing page bills every member of the workspace, not only the people who touch the form.
2. The requests you already get. Copy last month's requests from email and chat into one sheet. Note the three facts you needed to triage each one, typically the type of work, the deadline and the channel. Those become your fields.
3. A baseline. For the same requests, count the working days from ask to first reply. That is the number the form has to beat.

Step 1: Switch on Custom Fields

Open the App Center, click All ClickApps, find Custom Fields and turn it on, as the Custom Fields article describes. Add your fields to the List rather than the Space: a field added to a Space lands on every Folder, List and task inside it, and on the free plan every value it collects counts toward the 60.

Step 2: Create the list and its three fields

Create a List called Marketing requests. Give it a Dropdown for request type (campaign asset, event, press, website change), a Date field for the deadline and a Dropdown for channel. Three is deliberate. The uses article counts one use for a Dropdown value and two for two labels on one Label field, so a multi-select field eats the allowance twice as fast.

Step 3: Build the form

In the Views Bar, select Form, pick a template or Start from scratch, and choose Marketing requests as the List that stores submissions, per the Create and access Forms article. Add questions for the task name, the brief, attachments and your three fields, and mark the three as required. Required fields on the task itself are a Business plan feature, the uses article notes, but a required question on the form does the same job at intake. Uploads are capped at 25 MB per file, per the Forms article, so ask for a link when someone has a video to share.

Step 4: Route every submission to one owner

In the form's Settings tab, assign submission tasks automatically, or apply a task template that carries your standard checklist, per the Forms article. One triage owner works better than a round robin while the process is new. Share the link in the team channel or embed it on an intranet page, and turn on Account Authenticated Forms if only colleagues should be able to submit.

Step 5: Add one automation

Use the Share Task action so each requester sees their own submission and its status, without access to anything else in the List; the Forms article documents this exact use. Each dispatched action uses one of the month's actions whether it succeeds or fails, per the Intro to Automations. For example, 40 requests a month with one share action each use 40 actions, well inside the 100 a month that the limits article lists for the free plan.

Step 6: Let a Super Agent propose priority and due date

ClickUp's Super Agents article lists this exact job as a first agent: set the priority and due date of incoming tasks from your service levels. Activate the AI ClickApp, hover over AI in the navigation, select Create Agent and describe it, per Create a Super Agent. For example: "For each new task in Marketing requests, propose a priority and a due date from these turnaround rules: events 10 working days, website changes 5, social assets 3." The builder asks follow-up questions, then shows the agent's profile, where you set its triggers, tools and knowledge. An automation can launch it on each new task, and every run spends AI credits.

The human check: the triage owner reviews the agent's proposals each morning, and only a confirmed date goes back to the requester. ClickUp logs every Super Agent action and has them ask for approval on critical decisions; treat the date a colleague will plan around as one of those. If you would rather run the agent from Claude or another assistant, ClickUp's MCP setup page connects it to the same List.

Step 7: Read the turnaround

After a month, open the List and click Ask to question Brain about the submissions, for example how many requests arrived per type and how many passed their due date, or turn the submissions into a Dashboard; the Forms article describes both. Then count working days from request to first reply and set the result beside your baseline.

What ClickUp's help pages warn about

• The free field cap does not refill. At 60 uses a free workspace can clear values but cannot add or re-add them, per the uses article.
• Automations stop for the rest of the month. When the workspace runs out of actions, its automations pause until the next monthly reset, per the Intro to Automations.
• Branching forms sit higher up. Conditional logic on form questions is on Business Plus and Enterprise only, so design a Core form without it.
• No AI ClickApp, no agents. Super Agents need the AI ClickApp activated for the workspace.

The free pilot, and when the invoice starts

Steps 1 to 5 run on the free plan, whose single form, per the pricing page, is all this job needs, and 20 requests are enough to learn whether colleagues will use a form at all; if they keep emailing instead, no plan fixes that. ClickUp's free plan hands over the form and the fields and caps, for good, the values typed into them, which times the invoice for request 21, the point at which every brief already flows through the form. Decide on Core while you are still on request 10, not on the morning the fields stop filling.

FAQ

Do form submissions count as Custom Field uses?

Plan on it. The uses article counts a use each time a value is added to a Custom Field on a task, and its list of exceptions does not include form submissions.

Can people outside ClickUp submit the form?

Yes. A form can be shared by link or embedded on a page, and Account Authenticated Forms restricts it to people with access to your workspace, per the Forms article.

Can a requester follow progress without joining the workspace?

Yes. The Share Task automation action shares a submission with the person who sent it, without giving them access to other tasks in the List, per the same Forms article.