Gmail to Discord, a daily PDF inbox digest
Your inbox isn’t the problem. The constant “did I miss something important?” feeling is. Credentials arrive at random times, deadlines hide inside long threads, and OTPs show up when you’re already in the middle of something else.
This Gmail Discord digest automation hits marketing leads and agency owners hardest, honestly. But ops folks and solo consultants feel it too, because they’re the ones tracking logins, invoices, and last-minute client requests. The outcome is simple: one clean daily PDF brief your team can scan in a minute.
Below, you’ll see exactly what the workflow does, what it replaces, and how to make it your own without turning email into a second job.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Gmail to Discord, a daily PDF inbox digest
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/discord.svg' width='40' height='40' /></div><br/>Discord"]
n2@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model1", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>HTTP Request"]
n4@{ icon: "mdi:robot", form: "rounded", label: "Summarization Chain", pos: "b", h: 48 }
n5@{ icon: "mdi:web", form: "rounded", label: "PDFco Api", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/markdown.dark.svg' width='40' height='40' /></div><br/>Markdown"]
n7@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>extract required sections fr.."]
n9@{ icon: "mdi:message-outline", form: "rounded", label: "get mails from past 24 h", pos: "b", h: 48 }
n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>separate text and markdown"]
n6 --> n5
n7 --> n4
n5 --> n3
n3 --> n1
n0 --> n9
n2 -.-> n4
n4 --> n10
n9 --> n8
n10 --> n6
n8 --> n7
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n4 ai
class n2 aiModel
class n3,n5 api
class n8,n10 code
classDef customIcon fill:none,stroke:none
class n1,n3,n6,n8,n10 customIcon
The Problem: Important Emails Get Buried
Important emails don’t arrive neatly labeled “this matters.” They arrive mixed in with newsletters, CC’d threads, calendar noise, and random “quick question” replies. So you scan. Then you scan again later. And if you work with a team, you also forward messages or drop screenshots in chat, which is messy and easy to miss. The real cost isn’t just time. It’s the mental load of remembering what you saw, what you meant to act on, and what you never opened in the first place.
It adds up fast. Here’s where it breaks down in real life.
- You end the day with 40+ “unread but probably fine” messages that still nag at you.
- OTPs and credential emails get lost in the scroll, so logins take longer than they should.
- Deadlines hide inside long email chains, which means tasks get started late.
- Forwarding “important stuff” to a teammate is inconsistent, so nobody trusts the process.
The Solution: A Daily PDF Digest Posted to Discord
This n8n workflow turns the last 24 hours of important Gmail into a single, readable brief that lands where your team already pays attention: Discord. It runs automatically every day at about 8 PM, pulls messages from your inbox that are marked “INBOX” and “IMPORTANT,” and cleans up the content so it’s not full of broken formatting and ugly tracking URLs. Then an AI summarizer (GPT-4.1-mini) extracts the parts you actually need, like deadlines, action items, credentials, and OTPs. That summary becomes a tidy markdown report, gets rendered into HTML, converted into a professional PDF through PDF.co, and finally posted to your Discord channel via webhook.
The workflow starts on a schedule, not when you remember. Gmail emails are parsed and compiled into a digest-friendly format. AI produces a concise summary with “[Action Required]” callouts, then PDF generation and Discord delivery finish the job.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you receive about 25 “important” emails a day. Manually, you might spend 2 minutes each to open, skim, decide what matters, and forward key ones to a Discord channel or teammate, which is roughly 50 minutes daily. With this workflow, you spend maybe 2 minutes checking the PDF in Discord, then only open the handful that actually require action. The automation runs in the background on schedule, and the “waiting” time doesn’t steal your attention.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail to fetch labeled emails via OAuth.
- Discord to deliver the PDF to a channel.
- PDF.co API key (get it from your PDF.co dashboard).
Skill level: Intermediate. You’ll connect accounts, paste a webhook URL, and tweak a couple of filters and prompts.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A daily schedule kicks it off. The workflow runs automatically at about 8 PM and targets the last 24 hours, so you get a true “daily brief” instead of an endless stream of pings.
Gmail emails are retrieved and cleaned up. It pulls messages labeled “INBOX” and “IMPORTANT,” then parses out the useful fields (sender, subject, plain text) while stripping noise like extra whitespace and ugly URLs.
AI summarizes what matters. OpenAI generates a concise digest and flags urgency using “[Action Required],” which is the part most people end up doing manually in their head.
A PDF is generated and posted to Discord. The markdown summary is rendered into HTML, converted to a PDF via PDF.co, then a Discord webhook posts the file (or link) directly into your chosen channel.
You can easily modify the Gmail filters to include specific labels, senders, or keywords based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set up the daily schedule that initiates the workflow.
- Add or open Scheduled Daily Trigger.
- Set the schedule rule to run at triggerAtHour
20. - Confirm Scheduled Daily Trigger outputs to Retrieve Recent Emails.
Step 2: Connect Gmail and Retrieve Messages
Pull emails from Gmail with specific labels and a 24-hour window.
- Add or open Retrieve Recent Emails.
- Credential Required: Connect your gmailOAuth2 credentials.
- Set Operation to
getAlland Return All totrue. - Set Label IDs to
INBOXandIMPORTANT. - Set Received After to
={{$now.minus({days: 1}).toISO()}}. - Connect Retrieve Recent Emails to Parse Mail Sections.
Step 3: Set Up Email Parsing and Aggregation
Extract clean, readable fields from the raw Gmail payloads and aggregate them for summarization.
- Open Parse Mail Sections and keep the provided JavaScript in jsCode as-is.
- Open Compile Mail Fields and set Include to
specifiedFields. - Set Aggregate to
aggregateAllItemData. - Set Fields to Include to
subject, from, plainText. - Confirm the flow Parse Mail Sections → Compile Mail Fields.
plainText. Add HTML parsing or adjust Gmail settings if needed.Step 4: Set Up AI Summarization and Formatting
Use the AI chain to summarize the aggregated emails into plain text and Markdown, then split the output for downstream use.
- Open Summarize Mail Digest and confirm the prompt under summarizationMethodAndPrompts is set to the provided text.
- Ensure OpenAI Chat Engine is connected as the language model for Summarize Mail Digest.
- Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine (not in Summarize Mail Digest).
- Open Split Text and Markdown and keep the JavaScript that parses
PLAIN TEXTandMARKDOWNsections. - Confirm the flow Compile Mail Fields → Summarize Mail Digest → Split Text and Markdown.
Step 5: Generate PDF and Post to Discord
Convert the Markdown digest to HTML, render a PDF, fetch its URL, and post the plain-text summary to Discord.
- Open Render Markdown to HTML and set Mode to
markdownToHtml. - Set Markdown to
= {{ $json.markdown }}. - Open Generate PDF via PDFco and set Operation to
URL/HTML to PDFand Convert Type tohtmlToPDF. - Set HTML to
={{ $json.data }}. - Credential Required: Connect your pdfcoApi credentials.
- Open Fetch PDF Link and set URL to
={{ $json.url }}. - Open Post Discord Update and set Authentication to
webhook. - Set Content to
= {{ $('Split Text and Markdown').item.json.plainText }}. - Credential Required: Connect your discordWebhookApi credentials.
- Confirm the flow Split Text and Markdown → Render Markdown to HTML → Generate PDF via PDFco → Fetch PDF Link → Post Discord Update.
Step 6: Test and Activate Your Workflow
Run a manual test to confirm that emails are summarized, a PDF is generated, and a Discord message is sent.
- Click Execute Workflow to run the flow once.
- Verify Retrieve Recent Emails returns messages from the last day and that Parse Mail Sections extracts
subject,from, andplainText. - Confirm Summarize Mail Digest produces both plain text and markdown outputs, and Split Text and Markdown splits them correctly.
- Check Generate PDF via PDFco returns a URL and that Post Discord Update posts the plain text digest to your Discord channel.
- Toggle the workflow to Active for daily production use.
Common Gotchas
- Gmail OAuth credentials can expire or need specific permissions. If things break, check the Gmail credential status inside n8n and re-authenticate the connected Google account first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Discord webhooks get rotated or deleted more often than people expect. If the PDF stops posting, verify the webhook URL in your Discord server settings and update it in the “Post Discord Update” step.
Frequently Asked Questions
About 30 minutes if your Gmail and Discord accounts are ready.
No. You will connect credentials and tweak a few settings in n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs (often a few cents per day for a single daily digest) and PDF.co usage based on your PDF volume.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes. You can change the schedule in the “Scheduled Daily Trigger,” then adjust the Gmail search in “Retrieve Recent Emails” to target other labels, senders, or keywords. Many teams add a “VIP” label for client emails, or exclude newsletters completely. You can also tweak the summarization prompt in “Summarize Mail Digest” so it matches your brand voice and highlights only what you care about.
Usually it’s expired Google OAuth authorization in n8n or the connected account lost permission. Reconnect the Gmail credential in n8n, then re-run the workflow. Also confirm the Gmail node is allowed to read the labels you’re filtering on, because label mismatches can look like “no data” failures. If you’re pulling a lot of mail, Google can throttle requests briefly, so retrying a few minutes later may succeed.
A typical setup handles dozens to a few hundred emails per day comfortably, and the limiting factor is usually API rate limits and PDF generation volume. On n8n Cloud, your monthly execution allowance depends on your plan; self-hosting has no execution cap, but your server still has to do the work. If you expect heavy volume, filter aggressively (labels, senders, keywords) so the digest stays readable.
Often, yes, because this is more than “send email to Discord.” You’re doing parsing, cleanup, AI summarization, markdown-to-HTML rendering, PDF generation, and then posting the final artifact, which gets expensive or awkward in simpler tools. n8n also gives you branching and custom logic without nickel-and-diming you for every extra step. Zapier or Make can still work if you only want a basic notification, not a real digest. If you’re unsure, Talk to an automation expert and get a quick recommendation.
Once this is running, your inbox stops being a hiding place for urgent work. You get one daily brief in Discord, and the rest of your day feels a lot more manageable.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
