Google Sheets to Asana Zap: Custom fields not populating
Hello,
I’ve created a zap for information in a new row on a google sheet to then send that information to asana and create a new task within a certain project. After I did the test the connection worked but it only populated the task name field but the other fields were all blank. I have a feeling this has to do with custom fields. You can see in the example below I can pull up the custom fields but then no of that information gets added to the custom fields on asana project.
Your Zap trigger is for NEW or UPDATED rows, so that may be contributing to the issue.
If you tested with the Zap ON, then check your ZapRuns to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/
Make sure to take note of the row that was used. (row/id)
GSheets must be configured a certain way to be used in Zaps.
There are other limitations to be aware of such as formulas in all cells of a GSheet column, etc.
Thank you Troy!
I switched it to Just when a new row is added. The connection works but it’s still only pulling in the data for the name of the task but not populating any other custom fields in asana. It’s getting sent to the right project. Here is the history of the output and it shows all the right data but its just not making it to the custom fields in the task.
@Ryan Wong
We would need to see screenshots of the DATA IN/OUT for Step 2 in the Zap Run.
Here you go.
Search
workspace:
10079404476547
project:
0:
1201453837295401
section:
1201461931542913
name:
Test FH
assignee:
1205094661599377
_Custom_Field_1202270938137263:
1202270938137275
_Custom_Field_1202792004865496:
2/4/20241
_Custom_Field_1203626817126242:
11:00 AM
_Custom_Field_1202792004865498:
2/8/2024
_Custom_Field_1203626928354723:
12:00 PM
_Custom_Field_1203624003189160:
ADI
_Custom_Field_1203622805075759:
Wongs Palace
_Custom_Field_1203626800511412:
333
_Custom_Field_1203626936731397:
25
_Custom_Field_1201461931542952:
1201461931542953
_Custom_Field_1198956301498319:
1198956301498320
_Custom_Field_1205943543909485:
Test FH
plain_text:
true
Fields with no value:
due_on
Here is the data out
0:
gid:
1206116514632716
projects:0:gid:
1201453837295401
resource_type:
project
name:
Preneed Events
id:
1201453837295401
memberships:0:project:gid:
1201453837295401
resource_type:
project
name:
Preneed Events
id:
1201453837295401
section:gid:
1201461931542913
resource_type:
section
name:
New Event Requests
id:
1201461931542913
resource_type:
task
created_at:
2023-12-06T22:42:17.161Z
modified_at:
2023-12-06T22:42:18.317Z
name:
Test FH
notes:
assignee:gid:
1205094661599377
resource_type:
user
name:
Cody Whitlock
id:
1205094661599377
parent:
null
actual_time_minutes:
0
completed:
false
assignee_status:
inbox
completed_at:
null
due_on:
null
due_at:
null
resource_subtype:
default_task
start_on:
null
start_at:
null
tags:
workspace:
@Ryan Wong
We would need to see screenshots of the DATA IN/OUT for Step 2 in the Zap Run.
@Ryan Wong
This shows DATA IN for the custom fields.
Whether those custom field values are valid would need to be checked depending on the configured field type.
Can you show a screenshot of the custom fields for matching Task in Asana?
DATA OUT shows the created Task ID that you can use to check the Task in Asana.
Thanks. Here you go.
@Ryan Wong
Can you show screenshots of the custom fields for this Asana Task ID? (open the task)
TIP: Asana Task ID is shown in the browser URL when opening a Task in Asana.
Here are the custom fields we’ve created for every task that hits this project in asana
I found this thread because I am all of sudden running into custom field issues with asana. We’ve had zaps set up for months that select a custom field option when using the Create a Task option in Zapier. I reached out to zapier support because it seems all my custom fields have disappeared from this action, no matter the project. Wondering if it’s a bug. It’s killing our workflow today.
Hi @Ryan Wong and @rmjaskie,
I did some digging into this, and it seems like this is a known bug with the Asana integration where the Create Task Action step allows you to map values for custom fields, but does not always POST values.
Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:
Bring this to the attention of the integration developers
Help track and prioritize fixes
Allows us to notify you via email if/when this is fixed
Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.