← All templates

Operations

ClickUp Request Intake & Triage

Internal work requests arrive by chat, corridor and email, and none of those are a queue. This workflow gives them one front door: a form that asks the four questions that make a request actionable, a ClickUp task carrying a priority and a due date derived from the stated urgency, an acknowledgement telling the requester what happens next, and a Notion log so the pattern of requests becomes visible.

6 stepsRequires Zapier Starter or higher20 minEasy
TallyClickUpNotionDiscordFilter by Zapier

What you get

One front door for work requests, with the four questions that make them actionable.
Every request has a priority and a due date before anyone looks at it.
Requesters are told the response time up front, which stops the chasing.

Workflow blueprint

TA
When this happens
TallyNew Submission
1CL
ClickUpCreate Task
2NO
NotionCreate Database Item
3DI
DiscordSend Channel Message
4FI
Filter by ZapierOnly continue if
5DI
DiscordSend Direct Message

The full blueprint — every field mapping, example value and the written copy for each message — is included with purchase.

Getting it into Zapier

Build this one from the recipe. The blueprint gives you the exact trigger, action events and field mapping for all 6 steps, so it is a copy-and-paste job rather than a design job.

You need your own Zapier account. Zapier’s Free plan runs single-step Zaps only; multi-step Zaps need a paid plan, and Paths and Webhooks need Professional. How this works →

Not on Zapier?

n8n — import and go

An n8n workflow JSON ships with this template. Import it and all 6 steps arrive on the canvas wired in order, and 3 of the 6 nodes arrive with their fields already filled in — the subject lines, the message copy, the delays, the column names. Tally has no native n8n node, so that step arrives as an HTTP Request node with the endpoint left for you to fill in.

What an import cannot carry is your credentials, and the IDs that only exist inside your own account — which spreadsheet, which channel, which board. Those stay in a sticky note under the node, listing what is already done so you do not retype it, and what is left so you can see it.

Make — build guide

A Make-specific guide ships with this template: every module in order, every field value, and the concept translations that catch people out — filters live on the links between modules, and the schedule lives on the scenario rather than in a trigger module.

Self-hosted n8n has no per-task fee, which is worth knowing if this workflow runs at volume. Platform coverage →

Setup steps

1
Capture the request form

Configure this step using the field mapping in the blueprint.

2
Create the triaged ClickUp task

Configure this step using the field mapping in the blueprint.

3
Log it to the Notion register

Configure this step using the field mapping in the blueprint.

4
Acknowledge in the channel

Configure this step using the field mapping in the blueprint.

5
Flag urgent requests separately

Configure this step using the field mapping in the blueprint.

Implementation notes

  • "What happens if it is late" is the question that does the work. Everything is urgent until someone has to write down the consequence of it not being.
  • Acknowledge with the response time, not with thanks. Requesters chase because they do not know when to expect an answer, not because they are impatient.
  • Nothing is worked on before triage, including urgent things. A queue you can jump is not a queue.
  • Tally, Fillout, Typeform, Jotform and Microsoft Forms all substitute at the front; Linear, Asana, Height and Jira all substitute for ClickUp.