I believe previously when integrating Wufoo with Asana, you could make hidden fields appear in the task (like the task description, for example). Now I don’t believe a Wufoo hidden field will come into Asana at all.
Am I missing something? Is this possible with the new integration?
@Alexis, is there anyone involved with the new Wufoo integration I can tag to try to get an answer to this?
@Todd_Cavanaugh – it sounds like this would be a question for the team at Wufoo. Have you been able to get in touch with them?
@Alexis I thought Asana built the new integration at https://forms.asana.plus/ ? The integration page says, “This integration is supported by Asana.”
@Todd_Cavanaugh you can hide a particular field from a Wufoo form by setting “Class Names” to “hide” in the field formatting (see attached screenshot). Wufoo will then not make the field visible in the form. Let me know if you have any issues configuring this 
Hi @Sara, thanks for your response. I think there’s a misunderstanding about what I’m asking, however.
I know how to create a populated hidden field via Wufoo. After connecting the form with https://forms.asana.plus/, the hidden field is not adding data to the Asana task. Is this a bug or purposeful behavior?
Hi Todd,
I’m an engineer on our Integrations team. I’ve surfaced your question to our team, and one of our engineers should have an answer soon.
Best,
R.J.
Hi @Todd_Cavanaugh,
That’s correct, the new integration intentionally omits hidden fields. If having the hidden fields is useful for your workflow, we can provide a workaround for you to use that will make them appear in your tasks. Could you describe your use case to us? We’re interested in knowing more about how our customers use Wufoo and the hidden fields.
This is going to sound a little weird, but if you add a second word to the CSS layout keywords, like “hide workaround”, the fields will show up in the task description (but still be hidden from people filling out the form). This works because of an old feature we’re supporting for some of our customers.
Let us know if this solution works for you. Thank you for trying out the new integration!
Thanks so much for the answer, @Joe_Trollo! The use case was for a client in an order form workflow. I believe he wanted to be able to use the hidden field to break up the the Task Description into different sections, but I will need to follow up with him because he may have been hoping to autofill specific custom fields.
@Joe_Trollo—by the way, wanted to provide a few other pieces of feedback after using this for a client:
Thanks for the feedback! We’re aware that having to delete and recreate form connections creates some friction, and allowing customers to edit the connections is on our roadmap. Also, we’ve expanded the kinds of form fields that can be mapped to custom fields in Asana. Starting with our next release, number custom fields can accept phone numbers, and text custom fields can accept phone numbers, dates, times, money, and URLs. The next release of the integration is expected to go out sometime next week.
Hi Joe! This was really helpful… but now I’m looking to do the opposite. We have a “read and acknowledged” bit at the end of our intake form. Clients have to check it, but we don’t need the information in our Asana projects. Is there any way to not import specific information? Thanks!
@Joe_Trollo - Hope I’m barking up the right tree here.
I have an issue. I need to collect my customer’s email addresses on Wuforms so I know where to send the completed order (digitally), and I want to sync this to Asana so I can create tasks for my contractors based off of submitted orders (so far so good).
The problem is that I don’t want to disclose the “email” ID of the customer to my contractors in Asana…BUT, I do need the email ID to show up in Asana for my project manager so they can actually send the completed work to our clients once the contractors mark them as completed.
Does that make sense? Banging my head against the wall trying to figure out the best way to do this…or if possible at all. THANKS!
@saractall - Unfortunately, hiding a field from the form in the resulting task is not something the integration currently supports. However, that’s a great use case for such a feature, and I’ll pass it along to the team maintaining the integration.
@Jesse_Neubert - The description of a task cannot show different information to different users, so the solution here would be to link the form to two different projects and thus create two copies of the task: one copy would go to the project that the project managers see, and the other copy without the email would go to the project that the contractors work from. However, this would also require the ability to hide a form field in the resulting task, which is unsupported. This is another great use case that I’ll pass along.
