Homey Community Forum

[APP] Todoist

Adds Todoist integration for Homey.


  • Create tasks (in project, with due date, with due time)
  • Respond to task events (completed/uncompleted for now)


I’ve kept it very basic but Todoist has alot more features which can be implemented in the future if there is any interest.

1 Like

Dear Jero,

will it be possible in the future to create dynamic due-tasks?
Right now I can only create a static time and date card for due. But it would be very nice to create a task in the future based on events at my home. (e.g. my plant sensor registers a low level of water and creates me a task in the evening to water the plant).


Yes, that is a good idea. I might be able to create a card that accepts a token as a date/time (basically the default text input). Would that suffice for your use case?

Only problem I see is you probably want to add +1 days/hours to the actual event. Another option to explore might be the due_string Todoist supports e.g. in two hours.

This works pretty well and it errors on faulty dates. Defaults to your Todoist language setting and timezone.


Released a test version (v1.1.0) that has this card. Let me know if you find any issues.

1 Like

You are unbelievable. Thank you very much for such a fast reaction.

The due-text ist working fine, and does exactly what I expected. The possibility to use a variable from the logic part is also great in case of a calculated date or time.

Thank you very much!

1 Like

Dear Jero,

I just have a new idea for playing with Todoist.

Would it be possible to mark a task completed when a sensor value changes?

The moisture of a plant is below X% I creat a task for Todoist. If I give some water to the plant and the value rises above X% I want to mark the task in todoist completed by Homey.

Or the battery of a sensor is below X% - new task to todoist. After replacing the battery the task can be marked as done.

Would this be possible?


Seems possible yes but I only see this working for a task that is somehow memorized in a Homey variable or something.

The task creation would have to store the ID somewhere and the other Flow has to mark this ID as completed.

So maybe a card Create a task ... with reference id: <my_reference_id>. And another card with Complete a task with reference id: <my_reference_id>. Only problem would be if the Flow with the first card is executed multiple times you could overwrite a not completed task. Your reference id in this case could be something like battery_level_low_device_1.

Some problems I see is statuses flipping quickly for some reason resulting in spamming complete and create.

I could give it a try next week to make something user friendly if I have some time.