You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer: I am well aware that time is a limited resource, but I wanted to share an idea I realized years ago with a DIY solution with someone who also views Todoist as a focus for getting things done. Please ignore if this is not of interest, but I am not aware of such an approach currently, and I believe the idea has potential.
After a long time, I stumbled upon Habitica again and was very pleased with this project, especially since years ago I had cobbled something together myself because I had come to the same conclusion as you: namely that Todoist is the best task management tool, while Habitica offers many other advantages, and that it is not trivial to keep both in sync. Back then, I went a bit further and used Todoist for habits, dailies, and rewards as a universal interface, but I would like to share a relatively simple idea that might interest you and could be an extension of this project:
This is a local solution that synchronizes, but why not have an API endpoint that can be triggered by a webhook from Todoist when completing a task? In its simplest form, such an endpoint can directly forward actions to Habitica and do exactly what you do, namely create and complete a task in Habitica (or theoretically trigger other things). This way, no pulling is necessary, and there is no delay unless explicitly desired.
I was amazed at how well it worked back then and can only recommend this approach. At that time, I had extended the whole thing so that additional actions could be triggered via labels, such as triggering rewards, dailies, or habits (triggered by attached labels and text-matching).
To keep Todoist up to date and have triggers, I used some label strategies: If, for example, @recreate was used, I immediately recreated the task via the Todoist API (which is quite fast also with updating the UI). This way, within Todoist, I had triggers similar to Habitica, which allowed me to keep Habitica very timely synchronized through Todoist and focus on completing tasks rather than procrastinating with Habitica. When I was able to focus on Habitica, everything was up to date.
I am very aware that you have a different approach, but as someone who might also consider Todoist an extremely important tool, I thought I would share this idea with you. If you have any questions about what I have written, feel free to let me know. My tinkering will hardly be of any use to you, but it worked, and the concept has potential.
The text was updated successfully, but these errors were encountered:
Disclaimer: I am well aware that time is a limited resource, but I wanted to share an idea I realized years ago with a DIY solution with someone who also views Todoist as a focus for getting things done. Please ignore if this is not of interest, but I am not aware of such an approach currently, and I believe the idea has potential.
After a long time, I stumbled upon Habitica again and was very pleased with this project, especially since years ago I had cobbled something together myself because I had come to the same conclusion as you: namely that Todoist is the best task management tool, while Habitica offers many other advantages, and that it is not trivial to keep both in sync. Back then, I went a bit further and used Todoist for habits, dailies, and rewards as a universal interface, but I would like to share a relatively simple idea that might interest you and could be an extension of this project:
This is a local solution that synchronizes, but why not have an API endpoint that can be triggered by a webhook from Todoist when completing a task? In its simplest form, such an endpoint can directly forward actions to Habitica and do exactly what you do, namely create and complete a task in Habitica (or theoretically trigger other things). This way, no pulling is necessary, and there is no delay unless explicitly desired.
I was amazed at how well it worked back then and can only recommend this approach. At that time, I had extended the whole thing so that additional actions could be triggered via labels, such as triggering rewards, dailies, or habits (triggered by attached labels and text-matching).
To keep Todoist up to date and have triggers, I used some label strategies: If, for example, @recreate was used, I immediately recreated the task via the Todoist API (which is quite fast also with updating the UI). This way, within Todoist, I had triggers similar to Habitica, which allowed me to keep Habitica very timely synchronized through Todoist and focus on completing tasks rather than procrastinating with Habitica. When I was able to focus on Habitica, everything was up to date.
I am very aware that you have a different approach, but as someone who might also consider Todoist an extremely important tool, I thought I would share this idea with you. If you have any questions about what I have written, feel free to let me know. My tinkering will hardly be of any use to you, but it worked, and the concept has potential.
The text was updated successfully, but these errors were encountered: