Thanks, Simo!
Unfortunately, this doesn’t work. The “update database item” specifically requests a “Database Item ID”. I believe I tried the search module yesterday, and plugged any variable I could find in there, and it wouldn’t update the item.
I did find a solution, and it utilizes the data store very effectively. (Explanation below for future passersby).
Explained
Todoist New event module pulls in five different types of events:
- Task added (
item:added)- Task updated (
item:updated)- Task deleted (
item:deleted)- Task completed (
item:completed)- Task uncompleted (
item:uncompleted)
The three branches are explained below.
1. Task Added
I process “Task added” First, and add the result to a data store. The Data store uses the unique task ID as the Key, and the Database Item ID, and stores a few more variables, mostly for human clarity.
2. Task Updated
Next I update the task if the trigger receives item:completed, item:uncompleted, or item:updated.
Data store recalls using the Task ID key, and the Notion “Update Database item” goes to town, using the Database item ID (blue). The rest is just plugging in data.
Note: I chose to not allow Make to directly update tags or check boxes or statuses in the Notion database. I don’t know exactly how I want to display that info yet, so I’m bringing the raw data into Notion and will use database formula kung-fu to make it pretty.
3. Task Deleted.
When the trigger receives the item:deleted event, I chose to have it update a field in the database to retain the task (for archival purposes). Here, the Data store module is the same as the updating branch, and the Notion module, while still an “Update Database Item” Has one small change to archive the task.
I have to manually add the “true” tag (see “Deleted?” field) and display the event for confirmation. I do this because, oddly, Todoist doesn’t actually change the Deleted tag to display true (To my knowledge) when you delete a task. (maybe that’s for when it’s deleted by an external API?)
And that’s it! It connects pretty well, and we’ll see if it breaks over the next week or so of use!
Edit: If you’re on the free plan, you get 2 active Scenarios in total, and 1000 operations (API calls, or edits?) per month. In setting this up, I’ve used almost 50%, so we’ll see how this lasts through the month! I may contact support to see if they’ll reset me out of the kindness of their hearts, since this was all setup.