Automation to convert form responses into tasks/ subtasks
Héctor Alonso
Currently, with forms, we can only dump answers as custom fields within a specific task.
What we would like to achieve is that the questions and answers on the form could be directly transformed into tasks or subtasks, so that each relevant answer generates a separate action with the information provided by the user.
For example:
A customer onboarding process.
The Project Manager completes an onboarding form with those mandatory data and those that they don't have and don't have are left blank.
Each block or question on the form becomes a task or subtask.
The user's response is included within that task/subtask as a context and those that are not covered later.
So, instead of having all the information concentrated in custom fields for a single task, we could turn the form into an actionable list of work.
And the questions or information that we don't have, with a Kant diagram we plan the rest of the information collection.
The idea would be to move from a form model as a collection of information to a model where the form also serves to automatically generate an operational structure of work.
Log In
J'Dian Bennett
Would much rather have forms link back to the person assigned the form response - currently, the only way to ENSURE someone completes a form is by assigning them a task called "complete form". But the problem is that when they complete this form, it creates another task... kinda useless for our experience. For any HR department wanting to use forms for "Monthly Feedback" on their work experience, this becomes a burden because while automations can link them back to one another, that's a lot of automations for an entire organization (1 automation per person). Super Agents help with linking, but the problem is that Super Agents can NOT set permissions... so even if I set the permissions on the reminder tasks, the form response permissions do not carry over even if the link was clicked directly from a task description, and that creates a problem of everyone being able to see people's responses on their Monthly reflections unless I manually set those permissions.
So the problem is two-fold: we need the ability to set permissions via automations or Super Agents. We also need the ability for forms to link to their parent tasks or set the permissions before the response. I'd imagine many people have used feedback forms, but if you want that feedback to be private and hidden from the masses, there is currently no way (other than manual intervention) to automatically prevent exposure of private responses. ClickUP Admin