At a glance
- Subscribe to the right eventMoving or editing a task sends `item:updated`.
- Route by eventAfter the trigger, add a router or switch on the event name.
- Check it worksComplete a non-recurring task and confirm a new run appears.
Subscribe to the right event
- Moving or editing a task sends `item:updated`.
- Checking a task off sends `item:completed`. Add it to the webhook's events.
- In Make or n8n, edit the Todoist trigger or webhook and select both events.
Route by event
- After the trigger, add a router or switch on the event name.
- Send `item:completed` down one path and section moves down another.
Check it works
- Complete a non-recurring task and confirm a new run appears.
- Recurring tasks move to their next date when checked, so test with a one-off task first.
Updated 2026-11-01. General guidance, not advice for your situation; we scope each project in writing before any work starts.
Questions people ask first
Why didn't completion show up in the run history at all?
The webhook wasn't subscribed to the completed event, so Todoist never sent it.
Does undoing a completion send an event?
Yes, Todoist sends a separate uncompleted event, which you can subscribe to as well.
Tell us what you need built.
Tell us the process and the tools involved, or call. We reply with questions or a written scope.
hello@pushbuild.com