Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Todoist node v2.2: API token authentication broken on n8n 2.14.2 — Create Task fails with 410 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28441•Fetched 2026-04-15 06:44:33
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
chenxin-yanchenxin-yan
Participants
chenxin-yanchenxin-yann8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

ERROR: 410 Gone — This endpoint is deprecated

Root Cause

Related issues:

  • #25738 (closed Feb 18, 2026 — original report, not fully resolved)
  • #25775 (closed — filter fix for "Get many tasks" only, Create Task still broken)
  • #26450 (open — Move task broken, likely same root cause)

Fix Action

Fix / Workaround

The workaround is to bypass the native node entirely and use HTTP Request nodes against https://api.todoist.com/api/v1/tasks with Header Auth, which works correctly.

Workaround: Use HTTP Request nodes directly against https://api.todoist.com/api/v1/tasks with a Header Auth credential (Bearer token). This works correctly and confirms the issue is specific to the native Todoist node's API endpoint configuration, not the credentials themselves.

Code Example

ERROR: 410 Gone — This endpoint is deprecated
RAW_BUFFERClick to expand / collapse

Bug Report

Describe the bug

The native Todoist node (v2.2) fails to authenticate when using a Todoist API token on n8n 2.14.2. The "Create a task" operation returns a 410 error indicating the endpoint is deprecated, suggesting the node is still calling the old Todoist REST v2 API (/rest/v2/...) instead of the new unified v1 API (/api/v1/...).

This was originally reported in #25738, which was closed on Feb 18, 2026 without a full resolution. The filter issue for "Get many tasks" was addressed in #25775 / n8n 2.12.0, but the Create Task auth/endpoint issue persists on the latest version.

The workaround is to bypass the native node entirely and use HTTP Request nodes against https://api.todoist.com/api/v1/tasks with Header Auth, which works correctly.

To Reproduce

  1. Add a Todoist node (v2.2) to a workflow
  2. Configure it with a Todoist API token credential
  3. Set operation to "Create a task"
  4. Fill in required fields (content, project)
  5. Execute the workflow
  6. Node returns 410 error: "This endpoint is deprecated"

Expected behavior

The Todoist node should use the current Todoist API v1 endpoints (/api/v1/...) and successfully create tasks when provided with a valid API token.

Screenshots / Error output

ERROR: 410 Gone — This endpoint is deprecated

The node appears to be sending requests to https://api.todoist.com/rest/v2/tasks, which Todoist has retired in favor of https://api.todoist.com/api/v1/tasks.

Environment

  • n8n Version: 2.14.2
  • Node.js Version: v24.13.1
  • Database: PostgreSQL
  • Execution Mode: main (default)
  • Platform: Docker (self-hosted)
  • Operating System: Linux (Raspberry Pi 5, arm64)
  • Hosting: self hosted

Additional context

Related issues:

  • #25738 (closed Feb 18, 2026 — original report, not fully resolved)
  • #25775 (closed — filter fix for "Get many tasks" only, Create Task still broken)
  • #26450 (open — Move task broken, likely same root cause)

Workaround: Use HTTP Request nodes directly against https://api.todoist.com/api/v1/tasks with a Header Auth credential (Bearer token). This works correctly and confirms the issue is specific to the native Todoist node's API endpoint configuration, not the credentials themselves.

extent analysis

TL;DR

Update the Todoist node to use the new unified v1 API endpoint (/api/v1/...) instead of the deprecated v2 API endpoint (/rest/v2/...) to resolve the authentication issue.

Guidance

  • Verify that the Todoist node is indeed using the deprecated v2 API endpoint by checking the request URL in the error output or network logs.
  • Consider using the provided workaround of bypassing the native Todoist node and using an HTTP Request node with Header Auth to create tasks, as this has been confirmed to work correctly.
  • Check the n8n documentation and Todoist API documentation to ensure that the correct API endpoints and authentication methods are being used.
  • Monitor the related issues (#25738, #25775, #26450) for updates on a potential fix for the native Todoist node.

Example

No code snippet is provided as the issue is related to the configuration of the Todoist node and its API endpoint usage.

Notes

The issue appears to be specific to the native Todoist node's API endpoint configuration, and not with the credentials themselves. The workaround using an HTTP Request node with Header Auth confirms this.

Recommendation

Apply the workaround by using an HTTP Request node with Header Auth to create tasks, as this has been confirmed to work correctly, until a fix is available for the native Todoist node.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The Todoist node should use the current Todoist API v1 endpoints (/api/v1/...) and successfully create tasks when provided with a valid API token.

#api#model download#tokenizer error#prompt formatting#chain error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING