Label Gmail inbox emails with GPT-4o and store them in Mem0

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Who’s it for This template is for small business owners like contractors, consultants, and agency owners who close deals via email. How it works Think of this as a 24/7 personal assistant for your ...

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.gmailtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.filter, n8n-nodes-base.gmail, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.lmchatmistralcloud, n8n-nodes-base.httprequest

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title: Label Gmail inbox emails with GPT-4o and store them in Mem0
Workflow name: Label Gmail inbox emails with GPT-4o and store them in Mem0

Who’s it for

This template is for small business owners like contractors, consultants, and agency owners who close deals via email.

How it works

Think of this as a 24/7 personal assistant for your inbox. Every five minutes, the workflow "reads" your new emails. It instantly filters out the junk (like newsletters or internal notifications).

The AI then analyzes the email to figure out what the customer wants. Then automatically puts a label on the email in Gmail (like "Action Required" or "Urgent"). Most importantly, it saves a "memory" of that email.

How to set up

Gmail: Connect your Gmail account using OAuth2 credentials.
AI Models: Add your OpenAI API key to the GPT-4o node.
JigsawStack: Provide API keys for JigsawStack (the optional fallback classifier) and Mem0.ai in the respective HTTP Header Auth credentials.
Domain Filter: In the [Router]: Triage Streams node, update the second rule to match your company's domain (e.g., your-sme-domain.com) to filter out internal emails.

Requirements

n8n version 1.0+
Gmail OAuth2 Credentials
OpenAI API Key
Mem0.ai Account
JigsawStack API Key (Optional but recommended for fallback)

This template as a foundation

You can easily extend it with other worklfows like:

AI Email Drafting: Automatically generate draft replies based on the "LABELS" powered by Mem0.
Weekly Intelligence Summaries: Use the Mem0 database to generate a Friday afternoon digest of all deals closed or pending.
Risk Assessment: Flag emails containing specific liability keywords or "Cold Outreach" for immediate archiving.

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 - Manual Trigger

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

Block 2 - [Trigger]: Watch Inbox (5m)

Type / Role: n8n-nodes-base.gmailTrigger - gmailTrigger
Config choices: Version 1.3

Block 3 - [Batch]: Process Emails

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 4 - [Filter]: Needs Marketing Tag?

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

Block 5 - [Gmail]: Tag as Marketing

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

Block 6 - [LLM]: GPT-4o

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

Block 7 - [LLM]: Mistral

Type / Role: @n8n/n8n-nodes-langchain.lmChatMistralCloud - lmChatMistralCloud
Config choices: Version 1

Block 8 - [API]: Jigsaw Classification

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 9 - [Gmail]: Apply AI Category

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

Block 10 - [Gmail]: Apply Jigsaw Category

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

Block 11 - [Set]: Finalize Payload Fields

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - [Python]: Format Mem0 V2 Schema

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

Block 13 - [API]: Push to Mem0 Long-term

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 14 - Sticky Note1

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

Block 15 - [JS]: Sanitize & Detect Marketing

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

Block 16 - [Router]: Triage Streams

Type / Role: n8n-nodes-base.switch - switch
Config choices: Version 3.4

Block 17 - Sticky Note2

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

Block 18 - [AI]: Main Branch Extractor

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

Block 19 - [AI]: Internal Branch Extractor

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

Block 20 - [Gmail]: Tag Domain (Always runs first. Tags it as "Agentive Concepts")

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

Block 21 - [Gmail]: Apply category for branch

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

Block 22 - End

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

Block 23 - Optional Branch

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

Block 24 - Sticky Note3

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

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

3. Summary Table

Workflow	Label Gmail inbox emails with GPT-4o and store them in Mem0
Complexity	advanced
Nodes	32
Categories	Ticket Management, AI Summarization
Author	Stephan Koning
Published	19 Jan 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/12826/12826.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Ticket Management workflows AI Summarization workflows

Frequently asked questions

What does Label Gmail inbox emails with GPT-4o and store them in Mem0 do?

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.

Stephan Koning

15 workflows

Nodes

n8n-nodes-base.manualtrigger n8n-nodes-base.gmailtrigger n8n-nodes-base.splitinbatches n8n-nodes-base.filter n8n-nodes-base.gmail @n8n/n8n-nodes-langchain.lmchatopenai @n8n/n8n-nodes-langchain.lmchatmistralcloud n8n-nodes-base.httprequest

Complexity

advanced

Published 19 Jan 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/12826/12826.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

## Quick Overview This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post-therapy check-in messages, analyze patient replies for sentiment and risk, alert therapists to at-risk responses, and log non-urgent replies for ongoing wellness tracking. ## How it works 1. Runs every hour on a schedule trigger. 2. Reads session records from Google Sheets and keeps only sessions that have a session date and have not been marked as check-in sent. 3. Uses OpenAI (gpt-4o-mini) to generate a personalized, non-clinical Telegram check-in message from the patient’s session details. 4. Sends the check-in to the patient via Telegram and updates the Google Sheets session row to store the message and mark the check-in as sent. 5. Triggers on incoming Telegram messages, looks up the patient in a Google Sheets master list by Telegram ID, and selects the most relevant recent session to provide context. 6. Sends the patient reply and session context to OpenAI for JSON-formatted sentiment classification and parses the result into structured fields. 7. If the sentiment is classified as at-risk, posts an urgent alert to a Slack channel; otherwise, appends the reply and sentiment details to a Google Sheets wellness log. ## Setup 1. Connect Google Sheets OAuth credentials and update the spreadsheet document ID and sheet names for Sessions, Patients_Master, and Wellness_Log. 2. Create and connect a Telegram bot credential, set up the Telegram trigger webhook, and ensure patient Telegram chat IDs are stored in Google Sheets. 3. Add an OpenAI API key credential and confirm the selected model (gpt-4o-mini) meets your requirements. 4. Connect Slack OAuth credentials and replace the placeholder Slack channel ID used for therapist alerts, and confirm the error-alert channel is set correctly. 5. Verify your Google Sheets columns match the workflow’s expected fields (for example session_id, checkin_sent, checkin_message_sent, therapist_slack_id) before activating.

View

Detect and route customer escalations with Claude, Slack and Linear

## Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and severity, then posts alerts to Slack and creates Linear tickets for actionable cases. ## How it works 1. Receives an inbound support message via a POST webhook. 2. Normalizes the incoming payload (Gmail, Zendesk, Intercom, HelpScout, or a raw test payload) into a consistent schema with customer details, subject, body text, and a source URL. 3. Sends the normalized message to Anthropic Claude and parses the response into structured JSON containing escalation flags, severity, trigger phrases, a summary, and a suggested reply opening. 4. Stops processing silently when the message is not an escalation (severity is none). 5. Builds a formatted Slack alert and Linear issue payload, including SLA guidance, detected signals, and links back to the original conversation. 6. Posts the escalation alert to a configured Slack channel. 7. Creates a Linear ticket for critical, high, and medium severity escalations and sends a Slack DM to a manager for critical and high cases. ## Setup 1. Add an Anthropic API credential for the Anthropic Chat Model node. 2. Add a Slack OAuth2 credential, set the target channel (for example, #escalations), and set the manager’s Slack user ID for direct messages. 3. Add a Linear OAuth2 credential and replace the placeholder Linear team ID used when creating tickets. 4. Copy the webhook URL from the webhook trigger and configure Gmail/Zendesk/Intercom/HelpScout (or your custom source) to POST message payloads to it in one of the supported formats.

View

Triage construction incidents with GPT-4o, Slack, Gmail and Google Sheets

## Quick Overview This workflow ingests construction incident webhooks, normalizes the payload, and uses OpenAI GPT-4o-mini to classify each incident by type and urgency, then routes alerts to Slack and Gmail and logs incidents to Google Sheets, with a daily Slack digest generated from the sheet. ## How it works 1. Receives an incoming incident via a POST webhook. 2. Normalizes the incoming Procore/Fieldwire-style payload into a consistent incident object (ID, title, description, location, reporter, assignee, and timestamps). 3. Sends the incident details to OpenAI (GPT-4o-mini) to classify issue type and urgency and generate a short summary, recommended action, and tags. 4. Routes incidents by urgency, sending Critical incidents to Slack with an @channel mention and emailing details to a project manager via Gmail. 5. Sends High-urgency incidents to Slack as a formatted notice. 6. Appends every incident to a Google Sheets log with status set to open. 7. Runs daily at 18:00 server time, reads the incident log from Google Sheets, builds an urgency-grouped digest, and posts it to a Slack channel. ## Setup 1. Add credentials for OpenAI, Slack (OAuth2), Gmail (OAuth2), and Google Sheets (OAuth2). 2. Copy the webhook URL from the Webhook trigger and register it in your source system (for example, Procore or Fieldwire) as the incident-created endpoint. 3. Replace the placeholder Slack channel IDs for Critical, High, Digest, and Error alerts. 4. Update the Gmail recipient address ([email protected]) to your real project manager email. 5. Set the Google Sheets spreadsheet (document ID) and ensure the target sheet exists with columns that match the incident log fields used by the workflow. 6. Confirm the schedule trigger time (cron: 0 18 * * *) matches your desired timezone/server time for the daily digest.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Label Gmail inbox emails with GPT-4o and store them in Mem0

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Who’s it for

How it works

How to set up

Requirements

This template as a foundation

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Manual Trigger

Block 2 - [Trigger]: Watch Inbox (5m)

Block 3 - [Batch]: Process Emails

Block 4 - [Filter]: Needs Marketing Tag?

Block 5 - [Gmail]: Tag as Marketing

Block 6 - [LLM]: GPT-4o

Block 7 - [LLM]: Mistral

Block 8 - [API]: Jigsaw Classification

Block 9 - [Gmail]: Apply AI Category

Block 10 - [Gmail]: Apply Jigsaw Category

Block 11 - [Set]: Finalize Payload Fields

Block 12 - [Python]: Format Mem0 V2 Schema

Block 13 - [API]: Push to Mem0 Long-term

Block 14 - Sticky Note1

Block 15 - [JS]: Sanitize & Detect Marketing

Block 16 - [Router]: Triage Streams

Block 17 - Sticky Note2

Block 18 - [AI]: Main Branch Extractor

Block 19 - [AI]: Internal Branch Extractor

Block 20 - [Gmail]: Tag Domain (Always runs first. Tags it as "Agentive Concepts")

Block 21 - [Gmail]: Apply category for branch

Block 22 - End

Block 23 - Optional Branch

Block 24 - Sticky Note3

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions