Make: why a Todoist webhook ignored finished tasks
On the Make Community forum, someone wanted a scenario to run whenever they checked off a task in Todoist. Their webhook fired when a task moved between sections, but nothing happened when a task was marked complete. A forum helper explained why: in Todoist, finishing a task is its own event, called item:completed, separate from item:updated. So you add that event to the webhook and give it its own route with a filter in the scenario. Recurring tasks are the trap. Checking one off just moves it to the next date, so Todoist sends an update event instead, marked with a completed intent. The original poster hadn't confirmed the fix yet, but Todoist's own documentation describes the events the same way. The general lesson for Make: when a trigger doesn't fire, check which exact events the app sends, because "changed" and "finished" are often separate.
The lesson: When a trigger doesn't fire, check which events the app sends. In Todoist, completing a task is its own event, and recurring tasks send an update instead.
Copy this prompt
Help me set up a Make scenario that runs when I check off a task in Todoist. Tell me which Todoist webhook events I need, including for recurring tasks, and how to add a router with a separate filter for each event. Then [WHAT SHOULD HAPPEN, e.g. add a row to my Google Sheet with the task name and date].
Our own prompt, written from what the source describes. We haven't run it ourselves. Text in [BRACKETS] is what you replace.
Watch out for
- Recurring Todoist tasks don't send a completed event when checked off. Filter the update event for them.
- Each webhook run uses Make credits, so filter out events you don't need early in the scenario.
Where this comes from
Original post by Amayensis on Make Community, Oct 31, 2026. We rewrote it in our own words. Check the original for the full context.
Read the originalGuides for this job
Turn a messy inbox into a 5-minute daily summary
Paste in today's emails and get back what needs a reply today, what can wait, what to ignore, and a one-line reply for each. It also flags emails that look like scams.