Every submission lands in the same section
How you'll know: A single long list of new tasks, sorted by nothing but date.
Fix: Add a rule on form submission that moves each task by request type and assigns an owner.
Requests reach your team through chat, email and hallway asks, and half of them are missing the one detail you need. An Asana form handles the intake: every submission becomes a task in the project the form belongs to, with the answers in the task's details. Anyone with the link can submit, even without an Asana account. Forms come with the Starter, Advanced, Enterprise and Enterprise Plus plans.
Where it lives: a form belongs to one project. You add it from that project's workflow setup, and each submission arrives there as a new task.
Who can fill it in: anyone with the link, or only people in your organization if you keep it private.
What it can ask: text, number, date and drop-down questions, file uploads saved to the task, and conditional logic that shows or hides questions based on earlier answers.
Ask whoever acts on the request what they need to start without chasing anyone. Each of those becomes a question. Anything that's only nice to know comes out.
Request type, department and urgency work best as drop-downs mapped to custom fields on the project. A rule or a report can use a field value. It can't read a sentence typed into a text box.
Conditional logic shows a question only when an earlier answer calls for it, so a print request asks for sizes and a web request doesn't. Shorter forms get finished.
An upload question stores the attachment on the task. A shared-drive link pasted into a text box tends to point at a folder the assignee can't open.
Keep it to your organization for internal requests. Open it to anyone with the link for clients, vendors or applicants who don't use Asana.
Watch for: a public link works for whoever has it, so it can be forwarded beyond the people you meant.
A rule triggered by the form submission can move the task into a section by request type and assign it. Asana workflow automation covers rules in depth.
A form makes the request complete. It doesn't make it answerable. A creative agency's request form asks for the client name, but whether that client has retainer hours left lives in the billing system, and the account manager's name lives in the CRM. Someone still looks both up before the work starts.
n-frames builds that lookup. When a submission lands as a task, a service listening on the project reads the client field, finds the account in the CRM and billing system, and writes the account owner and the hours remaining onto the task. Requests over budget get flagged before anyone picks them up. The Asana API page covers the webhooks this runs on, and Asana integrations covers the built-in links you'd use alongside it.
How you'll know: A single long list of new tasks, sorted by nothing but date.
Fix: Add a rule on form submission that moves each task by request type and assigns an owner.
How you'll know: The request type is in the task description, so no rule can act on it.
Fix: Make that question a drop-down mapped to a custom field. Rules read fields, not prose.
How you'll know: Requests still come by email from people who opened the form and closed it.
Fix: Cut questions the assignee doesn't use and hide the conditional ones until they apply.
No. When the form is shared with anyone who has the link, outside people can submit without logging in. Keep it limited to your organization when it's only for staff.
A form belongs to one project, and rules do the routing from there. A rule triggered by the submission can move the task to a section based on an answer, assign it, and add it to another team's project as well.
Not to build or edit one. A form's questions and settings are changed in the form builder. Duplicating a project through the API can bring its form along, and the API sees everything a form produces: the tasks, their custom fields and attachments.
Yes, through a connector such as Zapier or a small script on the form's response sheet that creates the Asana task. Asana's own form is the simpler choice when the requester's answers only need to reach Asana.
The plan matters more than a count: forms come with Starter, Advanced, Enterprise and Enterprise Plus. With many intake forms across teams, consistency is the harder part. Projects created from a template, or duplicated, bring their form with them, which is the simplest way to keep many intake forms alike.