Parse Gmail inbox and transform into Todoist tasks with Solve Propositions
Needs changesWhat this workflow does
This AI workflow has 21 nodes and runs on a schedule (every day) (plus 2 other triggers). Along the way it connects Gmail, OpenAI Chat Model and Todoist.
How it runs
Trigger: On a schedule (every day) (plus 2 other triggers).
- Get Unread From Inbox (Gmail): get many
- Get Starred From Inbox (Gmail): get many
- Get Open Tasks (Todoist): get many
- Mark As Read (Gmail): mark as read
- Merge: merges the data from its input branches
- Enrich Emails With Tasks (Merge): merges the data from its input branches
- Enrich Tasks with Emails (Merge): merges the data from its input branches
- Star (Gmail): add labels
- If: checks a condition and branches into true / false
- If: checks a condition and branches into true / false
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in Summarize Message (v1.8): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Summarize Message (v1.8) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (11)
- Manual Trigger
n8n-nodes-base.manualTrigger - Gmail
n8n-nodes-base.gmail - If
n8n-nodes-base.if - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Todoist
n8n-nodes-base.todoist - AI Agent
@n8n/n8n-nodes-langchain.agent - Merge
n8n-nodes-base.merge - Email Trigger (IMAP)
n8n-nodes-base.emailReadImap - Schedule Trigger
n8n-nodes-base.scheduleTrigger - No Operation, do nothing
n8n-nodes-base.noOp
From the author
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…