Skip to main content

Store Gmail email details in MySQL database

Workflow preview

Workflow preview
100%
Store Gmail email details in MySQL database preview
Open on n8n.io

Important notice

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

1. Workflow Overview

This workflow processes emails received in Gmail and saves detailed information about each email to a MySQL database. Before using, you need to have: Gmail credentials MySQL database credentials A ...

Best for

  • Ticket Management automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.gmailtrigger, n8n-nodes-base.code, n8n-nodes-base.mysql, n8n-nodes-base.stickynote

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Store Gmail email details in MySQL database
Workflow name
Store Gmail email details in MySQL database

This workflow processes emails received in Gmail and saves detailed information about each email to a MySQL database.

Before using, you need to have:

  • Gmail credentials
  • MySQL database credentials
  • A table in your database with the following columns:
    • messageId (Gmail message ID)
    • threadId
    • snippet
    • sender_name (nullable)
    • sender_email
    • recipient_name (nullable)
    • recipient_email
    • subject (nullable)

How it works:

  • The Gmail Trigger listens for new emails (checked every minute).
  • A Code Node extracts the following fields from each email:
    • Sender's name and email
    • Recipient's name and email
  • The MySQL Node inserts the extracted data into your database.
  • If an entry with the same sender email already exists, it updates the record with the new details.

How to use:

  • Make sure your database table has all required columns listed above.
  • Select the appropriate table and configure the matching column (e.g., id) to avoid duplicates.

Customizing this Workflow:

  • You can further modify the workflow to store attachments, timestamps, labels, or any other Gmail metadata as needed.

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 - Receive Email

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

Block 2 - Get Client Name and Email

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

Block 3 - Insert New Client in MySQL

Type / Role
n8n-nodes-base.mySql - mySql
Config choices
Version 2.4

Block 4 - Sticky Note

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

Block 5 - Sticky Note1

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

3. Summary Table

Workflow Store Gmail email details in MySQL database
Complexity intermediate
Nodes 5
Categories Ticket Management
Author Rosh Ragel
Published 23 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6302/6302.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 Store Gmail email details in MySQL database do?

This workflow processes emails received in Gmail and saves detailed information about each email to a MySQL database. Before using, you need to have: Gmail credentials MySQL database credentials A ...

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 use case.