Wrike Custom Request Forms 2026: Feature Deep Dive & How It Works

Wrike is a cloud-based work management platform that helps teams plan, track, and complete work across projects, tasks, and processes. If your team struggles with scattered requests, lost requirements in email threads, and inconsistent task creation, custom intake forms can bring structure to how work enters your system. Wrike’s Custom Request Forms allow you to build tailored forms that capture exactly what you need from users or clients and automatically generate tasks, projects, or other items based on responses.

In this article, I’ll unpack how this feature works, practical workflows you can use it in, setup steps, plus strengths and limitations, so you can decide how it fits your team’s needs.

Wrike’s Custom Request Forms: What Is It?

Custom Request Forms in Wrike are configurable intake forms that let you collect structured information from users — both inside your account and, optionally, externally — to kick off work items like tasks, projects, or custom items automatically. Instead of juggling emails or messages with scattered details, form submissions become standardized items in Wrike that include the key information you need right from the start.

These forms help you capture precise details upfront and translate them directly into work objects. For example, you might build a form that asks a stakeholder to specify deliverables, deadlines, priority levels, and more. When someone submits that form, Wrike can create a task, launch a project blueprint with pre-defined steps, or populate custom fields based on the responses. It essentially moves you from collecting requests to initiating work with far fewer manual steps.

Standout Aspects of Wrike’s Custom Request Forms

Wrike’s request forms offer capabilities you might not find in every intake form tool — especially in project management platforms. Here are the aspects that make them distinct:

• Dynamic and Conditional Logic — Depending on how someone answers, the form can show different questions or change the attributes of the created item, like mapping certain responses to custom fields or adding conditional subtasks. 
• Automated Item Creation — Submissions don’t just collect data — they create a new task, project, or custom work item and can even trigger blueprints that standardize structure. 
• External Form Submission — You can make forms accessible to people outside your Wrike account (via public links or embedding), making it easier to collect work requests from clients or external stakeholders. 
• Integration with Custom Fields and Templates — Wrike lets you map form responses into titles, descriptions, and custom fields so that data flows where you need it in your project structure. 
• Centralized Administration View — Admins have a table view of all forms (account-level or space-level) that lets them sort and filter forms, making it easier to manage intake at scale.

Want to learn more about Wrike?

Our review covers everything you need to know.

Read Review

How To Use Wrike’s Custom Request Forms

Below is a comprehensive, step-by-step breakdown of how to build and use custom request forms, from setup to submission.

Step 1: Access the Form Builder

To start building a request form:

• For space-level forms, navigate to the space where you want the form and open space settings.
• For account-level forms, go to your profile → Settings → Request Forms.

Click + Form to launch the form builder.

At this point, you can either create the form manually or use Wrike AI to generate a draft by describing the type of request you want to collect.

Step 2: Define Basic Form Details

At the top of the form builder:

1. Enter a form name.
2. (Optional) Add a description explaining when and why someone should use the form.

This description is visible to requesters and helps reduce incorrect submissions.

Step 3: Add Questions to the Form

Click + Add to start building the form itself.

For each question:

1. Choose a question type (short answer, dropdown, date, attachment, etc.).
2. Enter the question text and possible answers (if applicable).
3. (Optional) Add a description to guide users.
4. Mark the question as required if it must be completed.

Step 4: Configure What Gets Created When the Form Is Submitted

In the left-hand panel, define how Wrike should handle submissions:

• Choose what the form creates:
  • A new task or project
  • A task or project from a custom item type
  • A task or project from a blueprint
  • A duplicate of an existing task or project
• Set the status behavior (optional): If you set a status, Wrike applies it after submission. If not:
  • Blueprint-based items keep the blueprint’s status
  • Custom item types use the first active status in their workflow
  • Items created from scratch use the default workflow of the save location
• Choose where items are saved (optional): Select a folder, project, or space. If you don’t choose one, submissions land in Shared with me.
• Assign ownership (optional): You can automatically assign the created task or project to a specific user.
• Add approvals (optional): Configure approvals that trigger automatically after submission.

Step 5: Add Advanced Configuration Options (Optional)

Wrike lets you fine-tune how items are created:

• Reschedule around a specific task: Useful when creating projects from templates and you want timelines adjusted based on a key task rather than the project start or end date.
• Add a prefix: If the form creates items from an existing task or project, you can prepend user-submitted values to the titles of subtasks or items inside a project.

You can also define form visibility:

• Share the form with everyone in your account, specific users or groups, or nobody in your account.
• If you select nobody internally, you must enable a public link.

For external forms, you can even:

• Enable or disable email notifications
• Add CAPTCHA protection for security

Step 6: Map Responses and Apply Conditional Logic

This is where request forms become especially useful:

• Map responses so answers populate specific fields in the created task or project (title, dates, custom fields, assignees, statuses, and more).
• Add conditional logic to:
  • Show or hide follow-up questions
  • Change assignees, statuses, parents, or subtasks
  • Launch different tasks or projects based on answers
  • Trigger approvals only under certain conditions

This keeps forms relevant and prevents users from seeing unnecessary questions.

Step 7: Use Custom Fields With Auto-Updates

If your form uses regular or database custom fields, Wrike automatically updates form options when those fields change.

Auto-updates occur when options are added, reordered, renamed, or deleted.
If options with conditional logic are removed or renamed, Wrike prompts you to either:

• Manually update conditions, or
• Click Update these options, which removes affected options and clears linked conditions (with different behavior depending on field type).

This helps keep forms aligned with your data structure without constant manual maintenance.

Step 8: Publish and Share

Once your form looks right:

• Publish it so people can start submitting requests.
• Share the internal form link with teammates or copy the public link to use on a website, intake page, or client portal.

Using the Form as a Submitter

As a requester (internal or external):

• Open the request form from inside Wrike or via a shared link.
• Fill out the fields and submit.

After submission, Wrike automatically creates the task, project, or custom item behind the scenes — applying the mapped fields, assignees, statuses, approvals, and schedules. Internal users can immediately find the item in Wrike, while external users simply complete the form and move on, without needing access to the workspace.

Managing Submissions

Admins can return to the request forms area at any time to edit, duplicate, disable, or archive forms. As intake grows, keeping forms organized helps ensure requests continue flowing into the right spaces and workflows.

Wrike’s Custom Request Forms in Action

Let’s say you run an internal IT service team and you receive frequent ad-hoc requests for software access.

1. You publish a Software Access Request Form with fields for employee name, system needed, urgency, business justification, and manager approval.
2. Team members enter request details in the form instead of emailing your team.
3. Upon submission, Wrike automatically creates a task with the mapped title and fields, assigns it to the IT lead, and begins an approval if needed.
4. You get structured data and fewer follow-ups because information is captured up front.

In this scenario, the form speeds up intake, eliminates email back-and-forth, and results in actions that are ready to work rather than vague tickets.

Who Would Benefit From Wrike’s Custom Request Forms?

IT Support Teams

Collect consistent information about issues and required resources instead of fragmented emails.

Marketing Project Managers

Standardize requests for assets like creative briefs or campaign needs so work can start immediately.

HR Teams

Use forms for employee onboarding requests, benefits queries, or equipment provisioning.

Operations Coordinators

Centralize internal service requests and route them automatically to the right teams.

Client Services Teams

Publish external forms so clients can submit work requests directly and get confirmations.

Limitations and Challenges of Wrike’s Custom Request Forms

While functional, there are some limitations to consider:

• Complex Setup for New Users: Building advanced logic and mapping responses requires experience with Wrike’s interface—beginners can find it overwhelming because of the many options.
• Plan Requirements: Certain capabilities (like external forms) may be limited to higher tiers, so not all accounts can leverage every feature.
• Form Draft Visibility: Only admins can see drafts, meaning contributors may not preview work in progress without permission.
• External Attachment Limitations: External forms have constraints like limited file upload types or sizes.

FAQ About Wrike’s Custom Request Forms

How do I enable external submissions?

Enable the public link within the form settings and optionally embed it—you can customize email confirmations. 

Can non-Wrike users submit forms?

Yes, external links allow anyone to submit, though they won’t automatically see the associated task in Wrike. 

What types of questions can I add?

Single line, paragraph, dropdown, multi-select, date, attachment, importance, number, and assignee (internal only). 

Can responses be mapped to custom fields?

Yes—answers can be mapped to titles, custom fields, descriptions, dates, and more. 

Are dynamic or conditional forms available?

Yes — you can create forms that adapt which questions are shown based on earlier answers. 

Next Steps With Wrike

Custom Request Forms are just one way to bring structure to how work enters your workspace. Wrike also offers workflows, blueprints, automations, dashboards, and resource planning that can work in tandem with intake forms to give you visibility over both incoming requests and execution management. Explore how Wrike’s broader feature set supports your team’s full lifecycle of work management in more detail in this in-depth Wrike review.