Skip to content

[FEATURE] Todoist - Recurring prop #16092

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vunguyenhung opened this issue Mar 31, 2025 · 10 comments · Fixed by #16196
Closed

[FEATURE] Todoist - Recurring prop #16092

vunguyenhung opened this issue Mar 31, 2025 · 10 comments · Fixed by #16196
Assignees
Labels
enhancement New feature or request triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@vunguyenhung
Copy link
Collaborator

vunguyenhung commented Mar 31, 2025

Is your feature request related to a problem? Please describe.
Please add Is Recurring prop into the Todoist - Create Task action, following API doc here: https://developer.todoist.com/rest/v2/#tasks:~:text=to%20user%27s%20timezone.-,is_recurring,-Boolean
Please also update the Task completed trigger to including recurring task event

Additional context
Requested by a user here: https://pipedream-users.slack.com/archives/CPTJYRY5A/p1743381163804159

@vunguyenhung vunguyenhung added the enhancement New feature or request label Mar 31, 2025
@vunguyenhung vunguyenhung added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Mar 31, 2025
@melijimenez11
Copy link

@vunguyenhung Would adding this prop allow recurring tasks to be retrieved as well? I see it's for the Create Task action.

I had this issue when retrieving completed tasks. I could see completed non-recurring tasks but not recurring ones.

Thanks for the support

@vunguyenhung vunguyenhung changed the title [FEATURE] Todoist - Create Task: Add Is Recurring prop [FEATURE] Todoist - Recurring prop Mar 31, 2025
@vunguyenhung
Copy link
Collaborator Author

vunguyenhung commented Mar 31, 2025

Hi @melijimenez11, could you share the exact action that you use to retrieve completed tasks on Todoist app? Screenshots of your action configuration would help a lot too

@GTFalcao GTFalcao self-assigned this Apr 3, 2025
@GTFalcao GTFalcao moved this from Prioritized to Doing in Component (Source and Action) Backlog Apr 3, 2025
@GTFalcao
Copy link
Collaborator

GTFalcao commented Apr 8, 2025

@vunguyenhung after researching and testing this, I've found that for a task to be created as recurring, it needs to have the recurring pattern established in the due_string property. The due_is_recurring prop cannot be set directly.

https://stackoverflow.com/questions/47491608/using-todoist-python-api-to-add-a-recurring-task
https://www.reddit.com/r/todoist/comments/1bo08bm/reschedulepostpone_recurring_task_via_api_w_python/

I've added this info label to the Create Task component to make this more clear:

"To create a recurring task, use the Due String prop with a value such as every week. See the Todoist documentation on recurring dates for more examples and information."

@melijimenez11
Copy link

melijimenez11 commented Apr 8, 2025

Hi @melijimenez11, could you share the exact action that you use to retrieve completed tasks on Todoist app? Screenshots of your action configuration would help a lot too

@GTFalcao @vunguyenhung

My issue is not when creating new recurring tasks or completing tasks. My problem occurs when I try to run the new-completed-task trigger within my workflow. new-completed-task doesn't get triggered when a recurring task is set as done (for that day).

I'm trying to detect when a Todoist recurring task is marked as complete (on that day or instance) so that I can run an action on another service. Recurring tasks on Todoist are marked as complete and automatically re-scheduled for the next occurrence. I've had previous experience with Zapier, where this same trigger would run even for recurring tasks. So, it is technically possible to "watch" recurring tasks.

This is happening at the workflow level, and here) is what I can see when I inspect it. Here is a screenshot.

Image

@luancazarine luancazarine moved this from Ready for PR Review to In Review in Component (Source and Action) Backlog Apr 8, 2025
@luancazarine luancazarine moved this from In Review to Ready for QA in Component (Source and Action) Backlog Apr 8, 2025
@vunguyenhung
Copy link
Collaborator Author

Hi @luancazarine, could you try to check the existing Todoist completed task to trigger event for recurring task completed?

@vunguyenhung vunguyenhung moved this from Ready for QA to Changes Required in Component (Source and Action) Backlog Apr 9, 2025
@vunguyenhung
Copy link
Collaborator Author

Hey @GTFalcao, could you take this one?

@GTFalcao
Copy link
Collaborator

It seems Todoist has recently released a new API, which supports webhooks, and will be deprecating the v9 sync API we use for the current polling sources.

As such, this will be fixed with the migration to webhooks.

@GTFalcao
Copy link
Collaborator

Upon further investigation of this, it seems Todoist doesn't provide an endpoint to create a webhook - it has to be done in their app interface. So these webhooks can be used with the standard HTTP trigger in Pipedream, but unfortunately don't allow for a specialized trigger to be built.

I will attempt to adjust the existing trigger to work as expected with recurring tasks.

@GTFalcao
Copy link
Collaborator

This will now work with recurring tasks. The emitted event structure is slightly different since we're now polling for "completed tasks", a different endpoint than the object sync we were previously doing.

The completed task itself is emitted, and most of the data that was previously at the event root level is now in item_object - which, from what I understood in this context, is a reference to the recurring item while the root object is the instance of this item that was completed.

@GTFalcao GTFalcao moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog Apr 23, 2025
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Apr 23, 2025
@vunguyenhung vunguyenhung moved this from In QA to Ready for Release in Component (Source and Action) Backlog Apr 23, 2025
@vunguyenhung
Copy link
Collaborator Author

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/FEATURE-Todoist-Recurring-prop-1cfbf548bb5e81cf9b6dd9c491afe3a8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged For maintainers: This issue has been triaged by a Pipedream employee
Development

Successfully merging a pull request may close this issue.

3 participants