Todoist node broken: "Your request is invalid or could not be processed by the service" — API /rest/v2/ deprecated by Todoist

Questions
1

Hey everyone,

Posting this in case others are hitting the same wall, and hoping someone
from the node maintainers side sees it.

Setup: n8n 2.16.2, self-hosted, Docker.

The Todoist credential test and every Todoist node execution fail with:

Your request is invalid or could not be processed by the service

The message repeats in the logs on each attempt, with no additional detail.

I first assumed it was a token issue, but I ruled that out quickly:

A direct curl to the old endpoint returns:

curl https://api.todoist.com/rest/v2/projects -H “Authorization: Bearer ”

“This endpoint is deprecated. […] please update your use case to rely
on the new API endpoints, available under /api/v1/ prefixes.”

Same token on the new endpoint works perfectly:

curl https://api.todoist.com/api/v1/projects -H “Authorization: Bearer ”
→ returns my projects as expected.

So it looks like the native Todoist node still calls /rest/v2/, which
Todoist has now sunset. Hence the generic “invalid request” bubbling up
in n8n.

Workaround that unblocked me:

  • Create a “Header Auth” credential with
    Name: Authorization
    Value: Bearer <my_token>
  • Use a generic “HTTP Request” node pointing to the /api/v1/ endpoints
    (GET /api/v1/projects, POST /api/v1/tasks, etc.)

Works instantly, but obviously we lose the comfort of the native node
(no dropdowns for projects/labels, manual body building, etc.).

Questions for the community:

  1. Anyone else hitting this since Todoist flipped the switch on /rest/v2/?
  2. Is a fix for the Todoist node already in the pipeline, or should I
    open a GitHub issue?
  3. If you’ve built your own HTTP-based Todoist workflow — any tips or
    gotchas worth sharing?

Thanks!

3

welcome to the n8n community @Lordthirion
I would treat the native Todoist node as temporarily broken against Todoist’s old endpoint and use an HTTP Request node with Authorization: Bearer against the new /api/v1/… endpoints as the immediate workaround, since Todoist’s current API docs center on API v1 and your direct test shows the token works there.