Gmail to Slack, newsletters turned into team briefs
Your inbox is probably “fine” right up until the moment you realize you’ve saved 30 newsletters “for later” and none of them actually get read. Important updates get buried. Good ideas vanish. And the team keeps making decisions without the same context.
This Gmail Slack automation hits product managers and marketing leads hardest, honestly. But founders feel it too when trends move faster than your reading time. The outcome is simple: your labeled newsletters turn into a clean daily brief in Slack, with takeaways and next steps your team can use.
Below, you’ll see how the workflow pulls only the emails you label, runs AI analysis through your business lens, and posts a structured Slack message your team will actually read.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Gmail to Slack, newsletters turned into team briefs
flowchart LR
subgraph sg0["Daily Morning Flow"]
direction LR
n0@{ icon: "mdi:message-outline", form: "rounded", label: "Get Labeled Newsletters", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Combine All Newsletters", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "AI Newsletter Analyst", pos: "b", h: 48 }
n3@{ icon: "mdi:play-circle", form: "rounded", label: "Daily Morning Trigger", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Out Empty Results", pos: "b", h: 48 }
n5["<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/>Format for Slack"]
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/slack.svg' width='40' height='40' /></div><br/>Send to Slack"]
n7@{ icon: "mdi:brain", form: "rounded", label: "OpenRouter Chat Model", pos: "b", h: 48 }
n8@{ icon: "mdi:brain", form: "rounded", label: "Output Parser Model", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out Questions", 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/notion.dark.svg' width='40' height='40' /></div><br/>Save Questions to Notion"]
n11@{ icon: "mdi:cog", form: "rounded", label: "Perplexity Research Tool", pos: "b", h: 48 }
n12@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n13@{ icon: "mdi:memory", form: "rounded", label: "Conversation Memory", pos: "b", h: 48 }
n14@{ icon: "mdi:swap-vertical", form: "rounded", label: "Configuration", pos: "b", h: 48 }
n14 --> n0
n5 --> n6
n13 -.-> n2
n8 -.-> n12
n9 --> n10
n2 --> n5
n2 --> n9
n3 --> n14
n7 -.-> n2
n1 --> n2
n0 --> n4
n4 --> n1
n11 -.-> n2
n12 -.-> n2
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 n3 trigger
class n2,n12 ai
class n7,n8 aiModel
class n13 ai
class n4 decision
class n10 database
class n5 code
classDef customIcon fill:none,stroke:none
class n5,n6,n10 customIcon
The Problem: Newsletters Create “Invisible” Work
Industry newsletters are supposed to make you smarter, but they usually create a backlog you feel guilty about. You skim a subject line, star it, and tell yourself you’ll read it after the meeting. Then you forget, and a week later someone shares the same link in Slack like it’s breaking news. Even when you do read them, the value is trapped in your head, not shared as decisions, experiments, or content ideas. Multiply that across a team, and you’re paying for information twice: once in subscriptions, and again in wasted attention.
It adds up fast. Here’s where it breaks down in real life.
- You spend about 10 minutes per newsletter just deciding if it’s worth reading.
- Key details stay siloed because forwarding raw emails to Slack is messy and nobody reads the whole thing.
- Great insights don’t turn into action because there’s no consistent “takeaway + next step” format.
- Content and research ideas get lost in threads instead of being captured somewhere reusable.
The Solution: Daily AI Newsletter Briefs Posted to Slack
This workflow runs on a daily schedule and checks Gmail for newsletters you’ve already labeled as worth monitoring. It pulls those emails, filters out empty or irrelevant messages, and then combines the content into one “batch” for analysis. Next, an AI agent reviews everything using the business context you set (your industry, audience, what counts as relevant, and what to ignore). The output isn’t a wall of text. It’s a structured intelligence brief, formatted as a rich Slack message, so your team sees the signal without the noise. If you want, it can also split out the best “questions” and store them in Notion for content planning.
The workflow starts with your schedule trigger, then uses Gmail labels to fetch only the newsletters you chose. AI produces the brief and questions, and Slack receives a formatted post using Block Kit styling. Optionally, Notion becomes your running backlog of prompts and angles.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team tracks 8 newsletters across product, competitors, and your market. Manually, even a quick skim and forward takes about 10 minutes each, so that’s roughly 80 minutes a day (and it still arrives as messy links). With this workflow, you label emails as they come in, the daily run aggregates them automatically, and you spend about 5 minutes reading one Slack brief. Net result: around an hour back each workday, plus a shared view of what matters.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail for labeled newsletter intake
- Slack to deliver the daily team brief
- OpenRouter API key (get it from your OpenRouter dashboard)
Skill level: Beginner. You’ll connect accounts, set a Gmail label, and paste a Slack channel ID.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled run kicks things off. Each morning (or whenever you choose), n8n starts the workflow automatically so this becomes a habit, not a heroic effort.
Gmail labels decide what gets analyzed. The workflow fetches only emails under your chosen “newsletter” label, then filters out empty messages so the AI doesn’t waste tokens summarizing junk.
The AI agent creates an intelligence brief. Your “Settings Builder” configuration tells the agent what matters to your business (industry context, relevance filters, content pillars). It then produces structured insights and a set of questions your team can act on.
Slack receives a formatted post. A code step builds a clean Block Kit message, and the Slack node posts it to your channel so the brief is readable, skimmable, and easy to discuss.
You can easily modify the business context fields to match a new market, product line, or audience based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Morning Start Trigger
Set the schedule so the workflow runs every morning before your team starts the day.
- Select Scheduled Morning Start and set the cron rule to
0 8 * * *. - Confirm the trigger connects to Settings Builder as the first step in the workflow.
Step 2: Connect Gmail and Configure Newsletter Retrieval
Pull the latest tagged newsletter emails from Gmail for analysis.
- Open Fetch Tagged Emails and set Operation to
getAll. - Set Limit to
20and keep Simple asfalse. - In Filters, set Label IDs to your newsletter label and Received After to
{{ $today.minus(1, 'days') }}. - Credential Required: Connect your gmailOAuth2 credentials.
Step 3: Build the Settings and Aggregate Newsletter Content
Define audience context and consolidate newsletter content into a single structured payload.
- In Settings Builder, fill in all key fields like recipient_name, company_name, business_context, and relevance_filter with your actual values.
- Configure Filter Empty Messages to keep items where Left Value is
{{ $json.id }}and the operator isexists. - Set Aggregate Newsletter Items to Include
specifiedFieldsand Fields To Include toheaders.from, subject, textAsHtml. - Set Destination Field Name to
newsletterin Aggregate Newsletter Items.
Step 4: Set Up AI Newsletter Reviewer and AI Sub-Nodes
Configure the AI agent, its memory, tools, and output parsing to generate structured intelligence.
- In AI Newsletter Reviewer, keep Prompt Type as
defineand ensure Text includes the full analysis prompt with expressions like{{ $('Settings Builder').item.json.recipient_name }}and the newsletter map block. - Connect OpenRouter Chat Engine as the language model for AI Newsletter Reviewer with Model set to
google/gemini-2.5-flash. Credential Required: Connect your openRouterApi credentials. - Attach Dialogue Memory Buffer to AI Newsletter Reviewer and set Context Window Length to
7. Add memory credentials on AI Newsletter Reviewer if required by your n8n setup. - Attach Perplexity Lookup Tool to AI Newsletter Reviewer with Model set to
sonar-pro. Credential Required: Connect your perplexityApi credentials on AI Newsletter Reviewer, not the tool node. - Attach Structured JSON Parser to AI Newsletter Reviewer with Auto Fix enabled and keep the full JSON schema example for output structure. Add parser credentials on AI Newsletter Reviewer if required by your n8n setup.
- Connect Parser Chat Model to Structured JSON Parser with Model set to
google/gemini-2.5-flash. Credential Required: Connect your openRouterApi credentials.
newsletter array, so make sure both exist before running the agent.Step 5: Configure Parallel Outputs to Slack and Notion
Send the intelligence brief to Slack and store content questions in Notion simultaneously.
- AI Newsletter Reviewer outputs to both Build Slack Blocks and Split Question Items in parallel.
- In Build Slack Blocks, keep Mode as
runOnceForEachItemand leave the JavaScript code as-is to format Block Kit. - In Post Slack Brief, set Message Type to
block, Text toDaily Newsletter Brief, and Blocks UI to{{ $json.blocksUi }}. Credential Required: Connect your slackOAuth2Api credentials. - In Split Question Items, set Field To Split Out to
output.content_questions. - In Store Questions in Notion, set Title to
{{ $json.question }}and keep the block content fields that use{{ $json.context }},{{ $json.content_pillar }}, and{{ $today.format('MM-dd-yyyy') }}. Credential Required: Connect your notionApi credentials.
Step 6: Test and Activate Your Workflow
Verify the end-to-end run and then enable the scheduled automation.
- Click Execute Workflow from Scheduled Morning Start to run a manual test.
- Confirm Post Slack Brief posts a Block Kit message to your selected Slack channel.
- Verify Store Questions in Notion creates database entries for each content question.
- Enable the workflow by turning Active on so Scheduled Morning Start runs daily at
08:00.
Common Gotchas
- Gmail credentials can expire or need specific permissions. If things break, check your connected Gmail credential status inside n8n 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.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your Gmail label and Slack channel are ready.
No. You’ll connect Gmail and Slack, then change a few settings like the label name and channel ID.
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 OpenRouter API costs around $0.01-0.05 per run.
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, and it’s the main point of the template. Update the “Settings Builder” configuration fields (audience, business context, relevance filters, and content pillars) so the AI agent evaluates newsletters like someone on your team would. You can also remove the Notion storage portion if you only want Slack output, or swap the AI model by changing the OpenRouter chat model nodes. If you want a different format, tweak the “Build Slack Blocks” code so the brief matches how your team likes to read.
Usually it’s expired Gmail credentials inside n8n or the connected Google account lost permission. Reconnect the Gmail credential, then confirm the label name matches exactly what the “Fetch Tagged Emails” node is looking for. If it still fails, check whether Google security settings are blocking the sign-in.
Plenty for most teams, since the practical limit is usually your AI usage budget rather than n8n itself.
For AI-heavy briefing like this, n8n is often a better fit because you can add branching logic, structured parsing, and richer transformations without paying extra per “step.” Self-hosting also removes execution limits, which matters if you scale to multiple inboxes or multiple channels. Zapier or Make can still work if you want a lightweight version (grab email, summarize, post), but you may hit complexity walls sooner. If you’re torn, Talk to an automation expert and we’ll help you pick the simplest option that won’t break later.
Once this is running, your team stops “collecting reading” and starts collecting decisions. The workflow handles the repetitive sorting and summarizing, so you can focus on what to do next.
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.
