Todoist Node Version 2.2 : Filter option not working

Questions
1

As today is the official date for the shutdown of the Todoist v2 API, I started replacing Todoist nodes version 2.1 in my workflows with the new version 2.2. However, the 2.2 nodes seem to be totally ignoring the ‘filter’ option, and the node returns every task in my todoist. Anybody else experiencing the same?

Edit: Forgot to mention that this is the Task\Get Many operation.

2

Yes, the filter functionality is broken in the current implementation.

Since the Todoist node filter is broken, use the HTTP Request node to call the Todoist REST API directly:

Setup:

  1. Add HTTP Request node

  2. Configure:

    • Method: GET

    • URL: https://api.todoist.com/rest/v2/tasks

    • Authentication: Generic Credential Type → Header Auth

      • Name: Authorization

      • Value: Bearer YOUR_TODOIST_API_TOKEN

    • Query Parameters: Add your filter

      • Name: filter

      • Value: today | overdue (or your filter string)

Example filters:

today                    # Today's tasks
overdue                  # Overdue tasks
p1                       # Priority 1 tasks
@label_name              # Tasks with specific label
#project_name            # Tasks in specific project
today & p1               # Today's priority 1 tasks

you can search for existing Todoist filter issues on Github.

Hope this helps!

2 Likes
3

Thank you for the reply. HTTP works, but the v2 API is due to be shut down today (see https://groups.google.com/a/doist.com/g/todoist-api/c/brwENjfT_tk), so your example won’t work for long. It has to use the new v1 API, which uses new IDs etc for tasks and projects.

Do you know if the other operations (Create Task, Delete Task etc) uses the old v2 API or the new v1 API? Not looking forward to rebuilding everything using HTTP nodes… :smiley:

4

Hi all,

Just to add another confirmation from my side: the built-in Todoist Node’s filter (Todoist node version 2.2) does not work, but (Todoist node version 2.1) works correctly

as @JohnHalex mentioned, the workaround now is just call the endpoint v1 or v2, both are working on my end right now, or use the old (Todoist node version 2.1):

image
image575×627 41.3 KB

v1 docs:

1 Like
5

I’m aware that both versions of the API can be used via the HTTP node, for now. As I mentioned, the v2 API is due to be permanently disabled today. This should mean that all 2.1 nodes should stop working any time soon. The API deprecation and the fact that node version 2.2 doesn’t support filters, means that all 2.1 nodes need to be replaced by a mix of HTTP nodes and new 2.2 nodes for task creation, edits etc. There has to be an easier way :smiley:

1 Like
6

well, if n8n doesn’t fix this asap, I guess we’ll see a lot of questions and GitHub issues about it soon :grinning_face_with_smiling_eyes:

btw there’s already open github issue:

Maybe ping some maintainers there and mention this topic..

1 Like
7

Hi, @mortenp, welcome back!
I don’t have expertise on this subject, but based on the thread it seems to be an issue.
I searched the n8n docs for information; see if anything there can help you with a workaround:

  • The Todoist node supports a get all tasks operation and a filters.filter parameter (for example, filter: today or filter: overdue), and this works as expected in the shared workflow snippet. [Todoist node; Merge example]
  • Check the n8n release notes / GitHub issues for your exact n8n version to see if Todoist node changes or bugs are mentioned. [Release notes 2.2.2; Release notes 2.2.3]