Todoist APIs are failing

[ezfira]

Hello,

All of my Todoist steps are failing with:

"This API endpoint is no longer available. Please refer to our documentation to upgrade your client to use the latest API version"

That includes the built-in integration like displaying the list of projects.

Please help. None of my Todoist flows are working.

Eyal

[Anonymous]

Thank you very much for the reply!

I'll continue to be patient, looks like they've got a beta out to folks like you. =]

[v-bacao-msft]

Hi All,

The new version of the connector has been developed and is currently in the Preview phase. Some regions have not yet been deployed, so stay tuned.

Best Regards,

[v-bacao-msft · Accepted solution]

Hi @ezfira /All,

Please check the new version:

https://docs.microsoft.com/en-us/connectors/todoist/#onitemcompletedv2

Best Regards,

[Anonymous]

Working well for me.  Thank you for the update and fix!

[Arkitekt]

@v-bacao-msftthanks for letting us know about the update.  I've changed all my flows and they are working again.

[SommunSommun]

I'm still having some issues with the 'dates'. Is there no more option to send a todoist string like 'today' or 'in three weeks'?

I'm using due date" `formatDateTime(utcNow(),'yyyy-MM-dd')` now but it seems to set the due date as 'today @ 2:00PM'

[Earp]

You can use the Current Time fuction which returns UTC and then Convert Time Zone to your timezone. Set the format to Short Date Pattern and then use the converted time variable in the API and it should just do the day. You can also us the future time if you want to set a new task in the future.

[Earp]

The new connector works but why did Microsoft not fix the label issue when doing this update? Anyone else having this issue? I have tried putting @label in the subject field but Todoist just put that text in the new task instead of adding this as a label. Guess I am sticking to creating task by email for now.

[SommunSommun]

@Earp This doesn't work for me. I'm using: 

formatDateTime(utcNow(),'MM-dd-yyyy')

The output this generates shows up as:

2019-10-18T00:00:00Z

However. The item shows up as a task with due date today@2:00AM (because of the time converstion at the API call). If I take a look at the API docs at Todoist they make a difference in due date option, see: https://developer.todoist.com/rest/v8/#create-a-new-task

"content": "Appointment with Maria",
    "due": {
        "date": "2016-09-01",
        "datetime": "2016-09-01T11:00:00Z",
        "string": "2017-07-01 12:00",
        "timezone": "Europe/Lisbon"
    },

I just want to be able to to post a STRING instead of a DATETIME. In the eralier connector this was possible, see:

Old new taskNew new task (v2)

[Earp]

@SommunSommun Sorry for the delay. This was working but I am now seeing the same issue. I use this format:

But the time is not going over as UTC even if the date input format is correct.

This is putting my task due at 7PM yesterday for my timezone. This needs to be fixed. I have converted everything over to creating task by email and the method above works. This also allows you to create task with labels which is a huge advantage for how I use Todoist.