Skip to main content

Google Tasks now has a number of ways of adding tasks. 

  1. Direct add
  2. Add from gMail using the make task button
  3. Add in an arbitrary Google Doc by creating a task checkmark then assigning

Zapier correctly detects new tasks that are added with methods 1 and 2, but does not ‘see’ tasks added in the third way, which means I can’t reliably use the integration to sync tasks.

 

Has anyone come across this? I assume it’s a bug in the Zapier integration or maybe Google Tasks presents tasks added that way slightly differently?

Hello @SamB . I’ve done some quick research on this topic and found out where the problem is and how it should be fixed. Google Task API ( /tasks/v1/lists/), used to fetch tasks, supports a parameter called “showAssigned” that filters the tasks assigned with a default value of “False” which means assigned tasks won’t be fetched.

Tasks created from Google Docs are assigned by default, so the current GTask Zap implementation does not list them. 

Fixing the issue is incredible as simple as follows:

  • Adding the header “showAssigned=true” to the HTTP request

I’ve performed some tests in the Google OAuth playground, and the results are satisfactory. Below is the original post from the official Google Task issue tracker I have based on.

Implementing this solution should be very straightforward. Please let me know if there is any way I can help.

 

Cesar

 


@SamB Another request for the same thing! Pulling tasks of google docs would be incredibly useful.

 


Hi ​@CesarCamargo and ​@gwvas👋

Thank you both for reaching out here. I’ve added your votes to the feature request now. 

@CesarCamargo - apologies for the delay in responding. Thanks so much for all your work in researching that and sharing your findings here, it’s very much appreciated! 🤗 I’ve passed this information over to our engineers so they can look into getting that header added to the request.

I can’t make any promises around when you can expect it to be done by, but I’ll be sure to follow up here once it’s sorted and you’ll both get an automatic email notification from us once the open feature request has been closed.


Happy to help, ​@SamB . I hope they’ll be able to add this change to their surely long backlog and have this issue fixed. 


please keep me in the loop when this is worked out. A big deal for our organization. 


Of course, ​@artistformallyknownasmayor! Your vote has been added and we’ll be sure to send you an email notification once it’s implemented. 

Thanks for everyone’s continued patience in the meantime—really appreciate it! 🧡


Also want to add my +1 here ​@SamB. This should be a 1 line change in the codebase, and it make a tremendous impact to a lot of people’s working days :) 


I see “google tasks (google docs integration) (1.0.0)” as a Zap. Is it possible to be invited to this ​@SamB 🙏

 

 


Hi ​@jamieh1,


I’ve added your vote for this feature request, and we’ll notify you via email once an update is readily available. Thanks.


Hi ​@jamieh1 👋

As there’s a version number (1.0.0) appearing in it’s name it could be a legacy version of the app that another of your Zaps is still connected to. If you add a new action step and search for the Google Tasks app are you then able to select it? If so that would confirm that it’s a version of the app that you already have access to.

At any rate, that version of the app doesn’t appear to have any triggers available so you wouldn’t be able to use it to trigger on new Google tasks added in Google Docs—sorry about that. As JammerS mentioned we’ve added your vote to the feature request so we’ll be in touch if/when it’s implemented.

For now, you might want to explore workaround Titus shared earlier in this thread. I do hope it will help to get your Google Tasks workflows up and running in the meantime! 🤞


Reply