Google tasks time part of "due" is always 00:00

Questions
1

Hello,

I’m just starting to play with n8n using a simple workflow.
It’s 2nd step is “Retrieve a task” from “Google Tasks”

It looks that the “time” part of the “due” field of the json structure is always “00:00.000Z” for me instead of matching the due time I’ve entered when creating the task :

image
image475×547 12 KB

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Meanwhile I’ve discovered that the issue is not on n8n side.
It is a known Google Tasks API bug :

https://issuetracker.google.com/331680197

Bug or feature ? I’m not sure since it’s in the API documentation :

The due date only records date information; the time portion of the timestamp is discarded when setting the due date. It isn’t possible to read or write the time that a task is due via the API.

2 Likes
4

Hi @Gilles_Pion,
thanks for posting this and welcome to the community :raised_hands:

It seems to be indeed a Google Issue. I have just played around on my end and also discovered that there no accurate time stamps for any of the tasks.

We might need to continue monitoring the issue on the Google issue tracker for any updates or official fixes from Google.

5

Yes, that’s what I’ve done on my side too by subscribing to the issue.