Keep in sync

if you update the mapping, make sure to change it in the other node as well!

Set Globals

Use Sync Setup Helper Workflow to generate the JSON and paste it in every Globals Nodes

Update section for each task in Todoist using the Sync API in full sync mode. Use batching and split into multiple batches, if needed, since there is a request limit of 100 full syncs within a 15 minute period.

Get open/incomplete tasks from both Notion and Todoist

Generate an email report containing all changes made by this workflow, since changes in Todoist are being overwritten.

Store more information, which was not available earlier

Set focussed flag, so it remains in Todoist even after updating in Notion

Create Notion page if it does not exist

Update Notion page if it needs to be changed

Checking for a cached flag in Redis, to prevent overrides and endless loops.

Retrieve Notion page, so it can be compared against

Store relevant information in highlighted execution data, in case of debugging

Following nodes reference to this node, so the trigger can easily be replaced

This prevents the creation of duplicates in Notion, by storing a special flag in Redis containing the Todoist ID

Update section for in Todoist using the Sync API in full sync mode (maximum of 100 requests within a 15 minute period!)

Delete the task if it does not fit into the filter anymore

Update the task if it needs to be changed

Notion tries to deliver webhooks again. To ensure the data is up to date, the payload must be retrieved again.

Continues on error, so it is not necessary to retrieve task beforehand

Instead of deleting pages in Notion, it is a safer practice to mark them as obsolete instead.

In rare cases Notion fires multiple webhooks within a short period of time, when creating a new task. This prevents the creation of duplicates in Todoist.

The mapping is more advanced and also includes fall-back values for edge-cases

Configure Webhook

Grab the webhook URL and use it in the Notion automation. If using the NotionWebhookEmulator instead, replace this node with the nodes shown below.

Only sync focussed & planned tasks for efficiency reasons

The mapping between the Notion and Todoist tasks is stored in Notion

The Todoist ID is being cached in Redis for 15 seconds, so the other Diff sync does not get triggered.

Create task if it does not exist (anymore)

Edge case: the task has been moved from Obsolete to Done

Todoist Webhook Router Example (optional)

Since Todoist sends the updates of all projects to a single webhook, the requests need to be routed accordingly. To do so, create a separate workflow, each containing the flow above, except replace the webhook and switch nodes with an "Execute Workflow Trigger". Then activate the nodes below and configure it, so it calls the sub-workflows accordingly.

Using the event type from Todoist is the only option to actually recognize, if a task was deleted

Previous node always returns output data, since it uses a filter to retrieve a matching item

Reverse mapping the Section/Status

The Notion ID is being cached in Redis for 15 seconds, so the other Diff sync does not get triggered.

Delete Notion page if Todoist task has been deleted

Handle tasks only found in Notion. This can still mean, that the task exists in Todoist, but does not match the filter, since it has been completed. In that case the Todoist task is being retrieved. If it exist, the Todoist Task will be reopened, otherwise it will be created. The Todoist ID is being cached in Redis for 15 seconds, so the Diff sync does not get triggered.

Handle tasks which show differences between both systems. If there are differences, the Todoist task will be overwritten by all properties from Notion. Also the status is being updated in the following step accordingly. The Todoist ID is being cached in Redis for 15 seconds, so the Diff sync does not get triggered.

Handle tasks only found in Todoist. This can still mean, that the task exists in Notion, but does not match the filter, since it has been completed. In that case the Notion page is being retrieved. If it does not exist, because it was deleted, the Todoist Task will be deleted as well. The Todoist ID is being cached in Redis for 15 seconds, so the Diff sync does not get triggered.

Set Schedule

Set the preferred period. Usually once a day, likely outside working hours should be a solid option.

Preparing data for comparing

Set mail address

Provide the email address where the report should be sent to. This node can also be replaced by an SMTP or similar node.

If consuming data from the Notion Webhook Emulator instead of a regular Notion Webhook, the data is structured differently and can contain multiple items. This section makes the workflow compatible with both approaches.

Register Webhook in Todoist App

Grab the URL from here and add it to the Todosit developer app as described in the setup instructions

Set project ID and name

The ID can be copied from JSON in Globals Node. If syncing multiple Todoist projects, use the router described below.

Replace trigger

Use this trigger in the sub-workflows instead

Register Webhook

Configure this webhook in the Todoist App as mentioned above

Set project IDs and names

Copy each project ID from the JSON of the different Globals Nodes and name the branches by the projects.

Select sub-workflows

Choose the sub-workflows based on the branch of the Switch Node

0. Start here

Notion

• A database must already exist (get a basic template here) with the following properties (case matters!):
  • Text: "Name"
  • Status: "Status", containing at least the options "Backlog", "In progress", "Done", "Obsolete"
  • Select: "Priority", containing the options "do first", "urgent", "important"
  • Date: "Due"
  • Checkbox: "Focus"
  • Text: "Todoist ID"

Todoist

• A project must already exist with the same sections like defined as Status in Notion (except Done and Obsolete)

Redis

• Create a Free Redis Cloud instance or self-host

Setup credentials in n8n

• Notion: https://docs.n8n.io/integrations/builtin/credentials/notion/
• Todoist: https://docs.n8n.io/integrations/builtin/credentials/todoist/
• Redis: https://docs.n8n.io/integrations/builtin/credentials/redis/

Clone workflow

• Clone this workflow into your n8n environment and map the credentials (beware, Todoist credentials are also used in HTTP request nodes)
• Check for every yellow sticky notes. They show instructions which need to be done once

1. Generate config JSON for Globals Nodes

The sync workflows have a Node named "Globals", which contain mapping information for both Notion and Todoist. This flow helps to generate the config, using a multi-form.

How to use

• Check if the credentials in the Notion and HTTP Request Nodes are set correctly
• Activate this workflow
• Open production URL of the form trigger and complete the form
• Copy the resulting JSON code into all 3 "Globals" nodes

2. Setup Todoist Webhook

• In the Todoist App open Settings > Integrations > Developer > Build Integrations

• Click "Create a new app"

  • App name: "Notion-Todoist Sync" / Name of your n8n instance
  • App service URL: (leave empty)

• Click "Create app"

• Update settings of the app:

  • OAuth redirect URL: Grab the production URL of the "OAuth redirect" Node (from step 3 on the right)

• Click on "Save settings", leave tab open

• Activate this workflow

• Open the Production URL of the "Todoist Webhook Setup Helper" Node (from step 3 on the right)

• Copy the Client ID and secret from the App settings into the form and submit it

• When prompted for permissions, click on "Agree"

• Go back to App settings tab

• Scroll further down to "Webhook"

• Update settings of the app:

  • Webhook callback URL: Grab the production URL of the "Todoist Webhook" Node (Todoist to Notion Diff sync)
  • Select these options:
    • item:added
    • item:updated
    • item:completed
    • item:uncompleted
    • item:deleted

• Click "Save webhook configuration"

• Click "Activate webhook"

• Settings can now be closed

4. Setup Notion Webhook

You can choose from two options and also choose different options for different workspaces, e.g. optionA for a business related workspace and option B for a private workspace. Both options work similarly, option A is a bit easier to setup, yet it is more expensive.

Option A: Notion Webhook via Automation (paid plan required)

• Create a new automation on the database which should be synced
• Rename the automation to "Notion-Todoist Sync" or similar
• Add trigger: "Any property edited"
• Add action: "Send webhook"
  • URL: Grab the production URL from the "Notion Webhook" Node of this workflow (Notion to Todoist Diff sync)
  • Content: Select all existing properties
• Click "Save"

Option B: Notion Webhook Emulator (no subscription required)

• Follow the instructions here: https://n8n.io/workflows/2284-provide-real-time-updates-for-notion-databases-via-webhooks-with-supabase/
• Use the Webhook URL from the "Notion Webhook" Node of this workflow to push the updates to

3. Activate Todoist Webhook

Webhooks are a bit different in Todoist then usual. A Developer App needs to be created and once be connected to via OAuth, to activate the webhook functionality. This flow only works when using the production URL of it's form trigger.

Retrieve Todoist task, which can be completed or deleted at this point. Using advanced retry logic, since the "Get many tasks" endpoint does not return completed tasks.

Todoist webhooks can arrive late. To ensure the data is up to date, the payload must be retrieved again. Triggers on deletion can overlap, thus try 3 times, then just stop. Using advanced retry logic, since the "Get many tasks" endpoint does not return completed tasks. No more retries needed, if Task does not exist.

Overwrite description with Notion URL

Copy task description initially to Notion, before it get's replaced in Todoist by the Notion URL

5. Finishing Touches

Cleanup

Now technically everything is ready, but it is missing better usability and maintainability. So start by moving (cut & paste) the 3 big flows (outlined in blue) to separate n8n workflows. You can name them as follows:

• Notion-Todoist Full Sync ()
• Notion-Todoist Diff Sync ()
• Todoist-Notion Diff Sync ()

Make sure to activate every workflow which requires it. Also save this workflow to avoid duplicates.

First run

• Execute the Notion-Todoist Full Sync workflow manually first
• Now that the initial sync is done and you can start using the realtime sync

Realtime Notion Todoist 2-way Sync Template

Purpose and structure

This folder contains the Realtime Notion Todoist 2-way Sync Template workflow. Its executable nodes use aggregate, code, compareDatasets, crypto, executeWorkflow, executeWorkflowTrigger, executionData, filter, form, formTrigger, gmail, html, httpRequest, if, merge, noOp, notion, redis, respondToWebhook, scheduleTrigger, set, splitInBatches, splitOut, stopAndError, switch, todoist, wait, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

OAuth redirect, Notion-Todoist Sync Setup Helper, Todoist Webhook Setup Helper, Schedule Trigger, Execute Workflow Trigger, Notion Webhook, Todoist Webhook, Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/1897_Webhook_Filter_Sync_Webhook.json MIT; preserve source notices.