Our form has different questions. Does that matter?

No. The workflow reads answers by question reference, and the setup guide shows where to change each one. Only three are required: a short title, the request type and a requested-by date. Everything else is copied into the description whatever it is called.

What happens when a request type is not in the lookup table?

It goes to the fallback list you name at setup, unassigned, and the Slack line says so. Nothing is dropped. Add the type to the table and the next request routes correctly; the existing task can be moved by hand.

Can it run on Make or Zapier?

Not as shipped. The response-ID check and the file attachment step are built as direct calls to ClickUp's API, which means extra HTTP modules on Make or Zapier rather than their standard ClickUp actions. The plain create-a-task path is simple on either; ask if you want that cut-down version.

Do I need a paid n8n plan?

n8n Cloud's Starter plan runs it, and so does the free self-hosted Community edition. Nothing here needs a higher n8n tier. Self-hosted needs a public URL, or a tunnel, for the Typeform webhook to reach it.

TfCUSMade to order

Projects & operations

Typeform work request → ClickUp task in the right list, assigned + Slack post

Work requests arrive as assigned ClickUp tasks, not as a form email someone retypes.

Internal requests deserve a task, not an email thread. This package watches one Typeform form and turns each response into a ClickUp task in the list that request type belongs to, assigned to that list's owner, with every answer in the description and any uploaded files attached. The team channel in Slack gets one line with the task link. Requesters stop chasing, and the queue lives in one place.

How it works

Tf
Trigger
New response on the work-request form (Typeform form_response webhook, registered by the n8n Typeform Trigger node)
Typeform
if
Step 1
Pick the list and assignee from the request type
A lookup table you fill in at setup maps each answer to the request-type question (design, IT, facilities, content) to a ClickUp list ID and a default assignee, with a fallback list for anything unmapped.
CU
Step 2
Check the list for a task from this response
ClickUp's Get Tasks call, filtered on the Typeform Response ID custom field, runs against the list first. A match means Typeform re-sent the webhook, and the run stops rather than create a second task.
CU
Step 3
Create the task with every answer in the description
The task name is the requester's short title. The description holds each question and answer in order, the due date comes from the requested-by answer, and priority maps from the urgency answer.
CU
Step 4
Attach any files the requester uploaded
Each file-upload answer is downloaded with your Typeform token and posted to the task through ClickUp's attachment endpoint, so the brief and its files sit together.
S
Step 5
Post one line to the team's channel
One Slack message names the requester, the request type, the assignee and the due date, and links to the ClickUp task; the channel is set per list in the same lookup table.

What changes once it runs

Every request becomes a ClickUp task within a minute of the form being submitted, in the list its type belongs to.
The assignee is set at creation, so nobody triages a shared inbox to hand work out.
Uploaded files travel with the task instead of sitting in a form notification email.
A re-sent Typeform webhook finds the existing task by its response ID and stops there.
One link per request in the team channel shows who asked for what, and by when.

What you get

Workflow export for n8n, tested end to end with a sample form
Written setup guide: Typeform token, ClickUp custom field, webhook registration, in that order
Routing lookup table as an editable sheet: request type → list, assignee, Slack channel
Screen recording of a request going in and the task appearing
Sample Typeform form you can duplicate, with the questions the workflow expects

Before you start

Typeform on any plan for the webhook, with a personal access token; a paid plan if your form uses a file upload question
ClickUp, Unlimited plan or above recommended, with one list per request type and a Typeform Response ID custom field; Free Forever caps custom field use
Slack with permission to install an app and post to the channels you choose
n8n on a public URL, cloud or self-hosted behind a tunnel, so Typeform's webhook can reach it

Built for

Questions before you buy

Our form has different questions. Does that matter?: No. The workflow reads answers by question reference, and the setup guide shows where to change each one. Only three are required: a short title, the request type and a requested-by date. Everything else is copied into the description whatever it is called.
What happens when a request type is not in the lookup table?: It goes to the fallback list you name at setup, unassigned, and the Slack line says so. Nothing is dropped. Add the type to the table and the next request routes correctly; the existing task can be moved by hand.
Can it run on Make or Zapier?: Not as shipped. The response-ID check and the file attachment step are built as direct calls to ClickUp's API, which means extra HTTP modules on Make or Zapier rather than their standard ClickUp actions. The plain create-a-task path is simple on either; ask if you want that cut-down version.
Do I need a paid n8n plan?: n8n Cloud's Starter plan runs it, and so does the free self-hosted Community edition. Nothing here needs a higher n8n tier. Self-hosted needs a public URL, or a tunnel, for the Typeform webhook to reach it.

Nearby on the shelf

Whole catalog