🎓 Academy training: Automating workflows in Asana

Welcome to the Automating Workflows in Asana Post-Training Hub! :tada:
Thanks so much for joining today’s session! :star_struck:

Here’s one of the questions that came up during the training.

Q: What are the most common scenarios where Forms can be used?

A: Forms are mainly used to collect structured information and turn submissions into tasks in a project.

Common use cases include:

  • Request intake – design requests, IT helpdesk tickets, budget approvals, or other work requests. Each submission becomes a task for prioritization and assignment.
  • External stakeholder input – collect sales leads, support tickets, orders, event registrations, job applications, or beta tester signups.
  • Internal team processes – gather bug reports, employee contact details, referrals, surveys, or team suggestions.
  • Standardized work intake – collect consistent details (deadlines, attachments, custom fields) so work starts with all required information.
  • Stakeholder feedback collection – gather product feedback or structured input from customers or team members.

In short: forms are best when you want a simple, standardized way to collect information and automatically create tasks in a project.

Feel free to share any questions you have along the way. :blush:

Hi everyone! :waving_hand:

Thanks for attending today’s APAC training!

Looking for ideas on where to start with Asana Automations? Here are a few great opportunities:

:robot: Decision making – Automatically route work based on criteria like priority, request type, or department.

:megaphone: Status updates – Notify stakeholders when work reaches key milestones or changes status.

:counterclockwise_arrows_button: Task handoffs – Automatically assign work to the next person when a task is completed or approved.

:clipboard: Connected work – Automatically create follow-up tasks or projects when additional work needs to be kicked off.

Start by automating repetitive, manual steps you’ll save time and keep your workflows running smoothly! :rocket:

:glowing_star: Welcome to the Post-Training Hub! :glowing_star:

Hello everyone! Lachezar here :waving_hand:

Here are two interesting questions raised during today’s session on Automating Workflows in Asana:


:red_question_mark: Question 1

Is it possible to add a task template to the form so that the new request is in the template?

:white_check_mark: Answer:
Yes! You can create a task template and use Rules to combine the two. Once your form submission comes in, it will be applied to generate your task template.

:open_book: Learn more here: Task Templates


:red_question_mark: Question 2

Are you able to export the forms to Excel?

:white_check_mark: Answer:
Yes, but it’s done through a project export, not directly from the form itself.

:open_book: Learn more here: Project Importing and Exporting

1 Like

Hi everyone! Thanks so much for joining today’s session! :star_struck:

Here’s one insightful question that came up during the training.

Q: Can we assign a unique ID to every form submission?

A: Yes. You can give each form submission a unique ID by using an ID custom field in the project connected to the form.

Steps:

  1. Open the project linked to the form.
  2. Go to Customize or click + in the column header.
  3. Add a new custom field and choose ID.
  4. Set a prefix and confirm.

Asana will automatically generate a unique incremental ID for every task created from the form.

Feel free to share any questions you have along the way. :blush:

Hi everyone and thanks for attending Automating Workflows in Asana! :partying_face:

Here’s a good question that came up earlier:

How can I see or set a “relative due date” in a task? When I click on the due date field, I only see options at the bottom left for “add time” and “set to repeat.”

Answer:
Good catch! What you’re seeing is expected. The relative due date option only appears when you’re editing a project template, not when editing a regular task.

Try this:

  1. Open your project.

  2. Click the project title dropdown.

  3. Select Save as template (or open the template editor).

  4. Click a task’s due date.

  5. Inside the template editor, the date picker will show options like:

    • X days after project start

    • X days before project due date

When you later create a new project from that template and choose a start or due date, Asana automatically calculates all task dates based on those relative offsets.

If any questions come up as you continue exploring Asana, feel free to drop them here anytime. :high_voltage: