- lesliedxAsked on March 29, 2018 at 12:05 PM
When performing the JotForm integration with Asana, I'm not able to tell JotForm to populate more than one field to the Task Notes. I need everything in the form to appear in the Task Notes in Asana. Am I missing the way to do this? This is really the whole reason I want to integrate - so co-workers can fill out a work request and it will appear with all the information right in my Asana task list.
(I am currently using the free version, if I upgraded would I have the ability to assign more of my form fields to Task Notes?)Page URL:
- JotForm SupportKevin_GAnswered on March 29, 2018 at 01:18 PM
This is the currently functionality of the integration, it's not actually possible to map a field more than once.
You may use a workaround for this, you may add a long text entry field and conditionally copy the values from the desired fields into this long text entry and then map it in the integration settings, you will be basically composing the notes.
This references will help with that:
I hope this helps.
- lesliedxAnswered on March 29, 2018 at 02:17 PM
Thank you for your answer.
My workaround ended up being pretty good - if slightly clunky to set up.
I made the Jotform submit button send an email to Asana (as you can create a task with an email). It also sends an email to me (this just helps me know when a task is added, but not necessary to make it work).
Then, I had to configure Jotform to send an email through my company SMTP so that Asana would know what workspace to assign the task to. (Basically, Asana wants email tasks to come from your user email address, so I had to set that up in Jotform. Thankfully, Jotform does have that functionality.
Once I had all those steps covered, I was able to fill out the form and have all the fields show up in the Asana task notes. Attachments are also included. Only thing I have to do is retitle the task as Asana uses the email subject line as the task title.
Hopefully, others will find this method useful.
- JotForm SupportKevin_GAnswered on March 29, 2018 at 02:31 PM
I'm glad to know you were able to find another workaround for this, since the thread is public other users can also see what worked for you and they may implement it on their own forms.
Thank you for sharing this with us.