How to Build Wrike Request Forms That Route Themselves
Short answer: Wrike request forms collect structured intake and convert each submission into a task in a chosen folder, with fields mapped to custom fields. Add an automation rule on the resulting task and it routes to the right team without anyone triaging. A working marketing intake form takes about 40 minutes to build.
The form is the easy part. The routing rules are where intake projects get abandoned.
What makes a Wrike request form different from a form tool?
The submission becomes a task in Wrike, with answers mapped to custom fields, and the task inherits the project’s workflow and automations.
Three consequences people miss:
- Answers are filterable. A “budget range” field means you can report on budget without reading tasks.
- The requester can be added as a collaborator, so status updates go out automatically via the task’s own notifications.
- Conditional sections let you hide questions that do not apply, which is the only real defence against form fatigue.
If you just need a form and no task, use any form tool. The value here is the task.
How do you build the marketing intake form?
Fields first, then routing. Build in this order:
- Create custom fields on the folder: Request type (dropdown), Priority (dropdown), Budget range (dropdown), Launch date (date), Requester team (dropdown). Five fields, no more.
- Create the form from the folder and attach those fields as questions. Mark only Request type and Launch date as required.
- Add conditional logic on Request type: if “Design”, show a link field for brand assets; if “Paid campaign”, show Budget range. Conditional questions are third and below — never first.
- Write a 2-sentence intro at the top of the form: what happens after submission and the expected first response time. That line reduces duplicate submissions more than any field.
- Test with five real submissions from the team before launch, then delete the test tasks.
The intro sentence is the most valuable field on the form and it is not a field. Without a stated response time, people submit again in three days.
How do you make the routing automatic?
One automation rule per request type, on the destination folder.
A workable set for three types:
| Trigger | Condition | Action |
|---|---|---|
| Task created from form | Request type = Design | Assign to Design team, add tag design, due date +5 business days |
| Task created from form | Request type = Paid campaign | Assign to Growth, set custom status Intake review |
| Task created from form | Budget range = Over $50k | Assign to Marketing lead, set Priority = High |
The order matters: Wrike runs rules in the order they appear, so put the escalation rule above the general assignment rule or both fire and the second overwrites the first.
That ordering bug bit me once. A $120k campaign went to the design queue because the general rule ran last.
What about AI triage on submissions?
Wrike’s AI can classify incoming requests and suggest the destination, which is genuinely useful when your form allows free-text descriptions.
It is less useful when your form has strong dropdowns, because the dropdowns already did the classification. The teams that get value from AI triage are the ones collecting messy prose — support tickets, inbound leads, free-form requests.
Availability: AI features require Business ($28.75/user/month) and above; forms themselves are available on most paid plans including Team at $9.80. If your only goal is structured intake, Team plus good fields beats Business plus AI.
Where request forms fall down
Four recurring problems:
- Too many questions. Eight fields reduces completion by roughly half in practice. Six is the ceiling; five is better.
- No default assignee. A submission with no rule falls into limbo. Always have a catch-all rule that assigns to a named triage person.
- Requesters who cannot see status. If you do not add them as a collaborator, they will email to ask. One checkbox prevents most of that.
- Duplicate submissions. The form does not detect them. Add an instruction to search before submitting, and accept that some duplicates will happen.
None of these are technically hard. All of them are the reason an intake form works for six weeks and then quietly stops being used.
Who should build this
Build it if you receive more than 20 requests a month through email or chat, you have at least three destination teams, and someone will maintain the rules. Marketing, IT help desks and internal creative teams are the strong fits.
Do not build it if you have one team and 10 requests a month — a shared inbox with labels is cheaper and nobody has to learn anything. And do not build it on the Free plan; forms and automations need a paid tier, and the Free plan’s 5-user cap will not cover a requester population anyway.
Quick Summary
- Wrike request forms create a task per submission with answers mapped to custom fields; five fields is the practical maximum.
- Add a 2-sentence intro stating what happens next and the response time — it cuts duplicate submissions.
- One automation rule per request type; put escalation rules above general assignment or the last rule wins.
- Add requesters as collaborators so status updates go out without anyone emailing to ask.
- Forms work on Team ($9.80/user); AI triage needs Business ($28.75/user) and mostly helps with messy free-text intake.
