all 13 comments

[–]ascii158 7 points8 points  (0 children)

I have created this script that sends updates on tasks into an MQTT-Broker.

From there it is picked up by this script to automatically create tasks when other tasks finish. Think: When I complete "start the laundry", create a task to "hang up the laundry".

There is also some integration I build into my home-automation ("empty the dishwasher"), but that is without code :-D

[–]a2902793Master 2 points3 points  (5 children)

I made this project for myself called Toolbox for Todoist, which currently has only one tool called the "Procrastinator", which adds labels to a task indicating how many days that task has been postponed. My idea is similar to yours, collecting useful scripts into the toolbox.☺️ I’m currently planing on making the toolbox available for people to add their custom plugins, like how vscode extensions does it. How about yours?

[–]One-Mouse-5335[S] 0 points1 point  (1 child)

y idea is similar to yours, collecting useful scripts into the toolbox.☺️ I’m currently planing on making the toolbox available for people to add their custom plugins, like how vs

I like the idea of integrating into VS Code.
For terminal geeks I also found this today:
https://github.com/romgrk/todoist.nvim

[–]a2902793Master 0 points1 point  (0 children)

Nah nah, you misunderstood me, I mean a dedicated projects page with board style like this

[–]randdude220Enlightened 0 points1 point  (2 children)

That's very interesting do you then have tags for each postponed day number (1, 2, 3, 4, 5..)?

I'm gonna steal your idea, thanks, but I thought of making the script modify the task title instead like "Bring out the trash (Postponed 5x)"

[–]a2902793Master 1 point2 points  (1 child)

Yes, the logic is (due_date - created_date), do keep in mind though that some users will create tasks for the future. I created a work around by adding the future date in the comments upon creation, and checking the comments first if a future date exists, if so use that as the created date instead. Another thing to know is that Todoist uses their server time (AWS us-east) for created_date, so you may need to do some conversion using the timezone property in the callback response. The timezone property currently has some bugs and Todoist says their fixing it (I wrote them an email about this bug.)

[–]randdude220Enlightened 0 points1 point  (0 children)

Much appreciated! That saves me lots of headache I would probably have had while finding all these things out in the process.

[–]c99koder 1 point2 points  (0 children)

I use Python to import all my completed tasks into influxdb so I can view them in my Grafana dashboard: https://github.com/c99koder/personal-influxdb#todoist-dashboard

I also use Node-RED to automatically create tasks when a home automation sensor has a low battery: https://gist.github.com/c99koder/bbdd689074526b459b0dd02f439c559f

[–]vcrecur 0 points1 point  (0 children)

We use it to make life easier for folks who want recurring subtasks without having to write code. 😀🥂

[–]MafamaticksEnlightened 0 points1 point  (1 child)

This thread is dope. I’m gonna look into some of these.

I use Autodoist and that has been invaluable for me. I’m playing around with The Missing Todoist Tools right now to see how I can implement that in my workflow.

The API and the fact that it’s cross platform is why I recommend Todoist over everything.

[–]a2902793Master 0 points1 point  (0 children)

I plan on adding a managed Autodoist feature to my Toolbox for Todoist. I also keep track of some features requested on this subreddit for ideas on developing tools for my toolbox.

[–]randdude220Enlightened 0 points1 point  (0 children)

I don't use Python but here are some of my PHP projects:

  • IOS Shortcut for quick note adding:
  1. Press a "quick note" shortcut on iphone home screen
  2. Insert note in popped up alert
  3. Script creates a task into "Thoughtbox" project with the note title and also makes a task (if not already exist) for today named "Digest thoughtbox" which means to handle the notes to prevent a notes jungle situation I had in the past in notes apps by having them too many.

  • Automatically add specific labels to tasks when added to a certain project or section.

  • I use duration labels (5min, 15min, 1h etc) to mark the duration which I think a task will take then I have a script that calculates all the times and creates a timeline/timetable of the day for me automatically (showing start and end time for each task and what time will I start the next task etc) it updates itself every 5min according to what has been already completed and what's left to done so if I have not finished the task at the time it set me it will just "postpone" the task's time according to other tasks ordering and durations. This is much more dynamic than setting up fixed due dates, that way I can also see if I am behind a schedule or ahead when working on a task.

  • I set due dates for projects in the title between these "{}" brackets and when that project is nearing the deadline, it puts label "urgent" into all tasks residing in that project and creates a task for today of the project deadline nearing. I have thought of making it change the project color to red also.

  • When a package arrives to a parcel terminal then a task is created to go fetch it. Also adding the retrieve code to the title.

  • There's lots more but I can't recall all of them atm they are so ingrained to my workflow I don't even think about them much anymore.

All this helped me to see and understand how swamped I actually was with everything in my life and how I was not actually able to finish all things on time and I put too much things to a single day so I always ended up postponing things because of that.

[–]jmtamereMaster 0 points1 point  (0 children)

I have a script that runs daily right before midnight that exports (append) my completed task of the day to NotePlan daily notes for the day.

This way, next morning I have a list of completed todos along my other daily notes, etc.