Skip to main content

Parse Gmail inbox and transform into Todoist tasks with Solve Propositions

Workflow preview

Workflow preview
100%
Parse Gmail inbox and transform into Todoist tasks with Solve Propositions preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who is it for? If you are getting a lot of emails into your Gmail inbox, then probably some of those can be solved easly by replying or by doing specific short tasks. But analyzing whole email thre...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.gmail, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.todoist, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Łukasz.

Original n8n.io source

1.1 Workflow description

Title
Parse Gmail inbox and transform into Todoist tasks with Solve Propositions
Workflow name
Parse Gmail inbox and transform into Todoist tasks with Solve Propositions

Who is it for?

If you are getting a lot of emails into your Gmail inbox, then probably some of those can be solved easly by replying or by doing specific short tasks. But analyzing whole email thread content just to catch up with multiple threads can be very wasteful. So by using AI you can actually get simple propositions of what should be done before closing this specific email and actual proposed answer to that email.

This is especially useful if you need to do some actions before replying to email. In that case you can simply assign task to specific person, await until it's done, copy-paste AI answer when it's done, and close.

Another good use would be if on one inbox there are working multiple people. It can make the process much more streamlined.

How It Works?

  1. Script runs on your selected trigger. If you are using section "Read and Star", then you may use "Email Trigger".
  2. Automation is looking for exiting open Todoist tasks, that have the same title as email
  3. If task does not exist, then we are asking AI to analyze thread and give output that is Todoist-API-ready:
    1. having summary of email content
    2. having proposed actions to be taken
    3. having proposed answer to this email
  4. If email was unstarred for some reason but task was not closed, then task is being closed automatically.
  5. Script FOR PURPOSE is not trying to unstar messagess which have closed tasks, because this could lead to some inconsistencies.

How to set up?

  1. Select and setup your triggers, depending on your needs
  2. Setup connections using N8N instructions. You will need:
    1. Gmail
    2. Todoist
    3. AI (in this workflow OpenAI is used)
  3. (Optional) Remove "Read and Star" section if you don't want tasks automatically read and starred.
  4. (Optional) Adjust AI node - especially useful if you want to use different model or have response in different language

NOTE Chat does not heave memory attached on purpose. The purpose is that it should analyze each inbox message separately, not in thread. When using memory, it can get lost easily.

NOTE2 You might want to adjust limits on nodes "Get Unread From Inbox", "Get Starred From Inbox" and "Get Open Tasks", especially if having issues with model complying to output structure.

And that's it. I hope that this automation will make your Gmail <-> Todoist process much more streamlined!

What's More?

There is actually more that you could do with this automation, but it really depends on your needs. For example, you could add Form trigger to handle incoming support requests. Another thing is that you could replace Todoist with Asana or any database (like NocoDB) if you are using it for your task management.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Mark As Read

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 3 - Star

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 4 - Get Starred From Inbox

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 5 - Get Unread From Inbox

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 6 - If Task Not Exist

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 8 - Structure Output Todoist Ready

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.2

Block 9 - If AI responded properly

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 10 - Create Todoist Task

Type / Role
n8n-nodes-base.todoist - todoist
Config choices
Version 2.1

Block 11 - Get Full Message

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 12 - Summarize Message

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.8

Block 13 - Enrich Emails With Tasks

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 14 - Enrich Tasks with Emails

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 15 - If Email Unstarred (Not Exist)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 16 - Close Task

Type / Role
n8n-nodes-base.todoist - todoist
Config choices
Version 2.1

Block 17 - Email Trigger (IMAP)

Type / Role
n8n-nodes-base.emailReadImap - emailReadImap
Config choices
Version 2

Block 18 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 19 - No Operation, do nothing

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 20 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Merge Starred and Unread Messages

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.1

Block 23 - Get Open Tasks

Type / Role
n8n-nodes-base.todoist - todoist
Config choices
Version 2.1

Block 24 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 25 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Parse Gmail inbox and transform into Todoist tasks with Solve Propositions
Complexity advanced
Nodes 25
Categories Ticket Management, AI Summarization
Author Łukasz
Published 10 Apr 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/3507/3507.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Parse Gmail inbox and transform into Todoist tasks with Solve Propositions do?

Who is it for? If you are getting a lot of emails into your Gmail inbox, then probably some of those can be solved easly by replying or by doing specific short tasks. But analyzing whole email thre...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Summarization use case.