Forms turn messy intake — “can you also do X?” requests over email and Slack — into structured tasks. Every submission becomes a task in the connected project, with the answers mapped to the right fields. Here’s how to build one.

Forms are available on Asana’s Starter plan and above. Branching logic requires the Advanced plan.

---

1. Create the Form

A form is attached to a project — submissions land there as tasks.

1. Open the project that should receive requests.
2. Click Customize (top-right).
3. Choose Forms → Add form.
4. Give the form a title and a short description for requesters.

---

2. Build and Map the Questions

Each question can feed a task field:

1. Add questions with Add question (short text, paragraph, single/multi-select, dropdown, date, attachment, etc.).
2. Mark the ones you need as required.
3. Map to fields: connect a question to the task name, assignee, due date, or a custom field so answers populate the task automatically rather than sitting in the description.

Good mappings to set up:

• A “What do you need?” question → task name
• A “When do you need it?” question → due date
• A “Priority” dropdown → a custom field you can sort and filter by

---

3. Add Branching Logic (Advanced)

On the Advanced plan, branching shows follow-up questions based on earlier answers:

1. Open a question’s settings and turn on branching.
2. Choose which answer reveals which follow-up question.

Example: if “Request type” = Design, show the “Dimensions” and “Brand” questions; if Copy, show “Word count” instead. Requesters only see what’s relevant, and you get cleaner tasks.

---

4. Share the Form

1. Click Copy link on the form.
2. Send the URL by email, Slack, or embed it on an internal page.

Submitters don’t need an Asana account — anyone with the link can fill it out, which makes forms ideal for cross-team and external intake.

---

5. Route Submissions Automatically

Every submission becomes a task in the project’s default section. To send them where they belong:

• Add automation rules that move or assign tasks based on a form answer (e.g., route “Bug” submissions to the engineering section).
• Combine the mapped priority field with sorting so urgent requests rise to the top.

---

6. Troubleshooting

I don’t see Forms under Customize

Forms require a paid plan (Starter+). On free Personal, the option won’t appear.

Branching options are greyed out

Branching (conditional questions) is an Advanced plan feature. Without it, every requester sees every question.

Answers land in the description, not in fields

You didn’t map those questions to task fields. Edit the question and connect it to the assignee, due date, or custom field.

Submitters say they can’t access the form

Use the public form link, not the project link. The form URL works without an Asana login; the project does not.

Submissions all pile into one section

Add an automation rule to sort by a form answer, or triage them with Carly’s Asana integration so each request is routed, assigned, and dated on arrival.

---

More on Asana: How to use custom fields in Asana · How to turn emails into tasks in Asana · How to use board view in Asana · How to set a recurring task in Asana. To triage and route form submissions automatically, see Carly’s Asana integration.

Related Articles

Guides

How to Use Board View in Asana (2026 Guide)

Jun 10, 2026

Guides

How to Use Custom Fields in Asana (2026 Guide)

Jun 10, 2026

Guides

How to Add Milestones in Asana (2026 Guide)

Jun 10, 2026