Unanswered

Todoist stopped working

(0) Share

Report

Posted on by AS-24030825-0

Last February my Power Automate flows involing Todoist actions stopped working (error saying "the response was not in JSON format")

Apparently it is related to some changes in Todoist API which requires some update from Power Automate.

Find below Todoist support message.

Do you know when this will be solved from Microsoft side?

Is there any workaround?

Todoist support message:

We recently upgraded our API and retired the legacy version. Because of this, the integration you’re using now needs to be updated on the integration provider’s side.

We’ve already informed our major partners and notified developers broadly, but some third-party integrations haven’t completed the update yet - and unfortunately we can’t force that change from our end. You’ll need to contact the integration app’s support team and ask them to migrate to the latest Todoist API version.

If you’re unable to complete the OAuth authorization flow, it’s likely due to our stricter validation of the redirect_uri. The integration developer must ensure the redirect_uri being sent during authorization exactly matches the one configured when they created their Todoist integration.

Once they update their integration settings, the connection should work normally again.

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Sunil Kumar Pashikanti 2,191 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @AS-24030825-0,

This issue is caused by Todoist retiring their legacy API. The Microsoft‑owned Todoist connector in Power Automate hasn’t been fully updated yet, so all actions fail with “The response is not in JSON format.” There’s no ETA from Microsoft; the only working solutions are using a custom connector or calling the Todoist API directly via HTTP.

Do you know when this will be solved from Microsoft side?

There is no confirmed date. The connector is acknowledged as broken, but no public roadmap or ETA has been published.

Is there any workaround?

Yes:

Custom connector
HTTP calls to Todoist API

Build a Custom Connector
Created a custom Power Automate connector
Connected directly to the new Todoist API
Used a personal API token (Bearer) or OAuth

Community example describing a working solution:

https://www.reddit.com/r/todoist/comments/ztjsx2/todoist_power_automate_flow_possible_fix/
This works reliably and bypasses the broken Microsoft connector entirely.

Use HTTP actions directly
If you don’t want a custom connector:

Use HTTP (with Azure AD or generic HTTP) action
Call Todoist API endpoints directly
Pass Authorization: Bearer <token> header

This aligns with Todoist’s current API design.

https://developer.todoist.com/api/v1/

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No
AS-24030825-0 4 on at

Like (0)

Report
Copy link

Link copied!

Thank you very much for your response.

I have tried both methods, but my expertise level is just TOO basic.

For the custom connector, the post/code may be a bit old. I got the error message below, but I don't know what to change.

This endpoint is deprecated.

If you're reading this on a browser, there's a good chance you can change
the v8 part on the URL to v1 and get away with it. ;)

If you're using the API directly, please update your use case to rely
on the new API endpoints, available under /api/v1/ prefixes.

For more details, please see documentation at https://developer.todoist.com/

I have also tried the HTTP path a bit, but, again, I don't really know what I am doing, so no luck...

If you have some further guidance, I will also give it a try.

Thank you.

Was this reply helpful? Yes No