Slack + Google Sheets, trend reports sent daily
You know the drill. Someone spots a trend on Twitter, another person saves a Reddit thread, and the “final” notes end up scattered across bookmarks, DMs, and half-finished spreadsheets.
This is where Slack Sheets trends automation pays off fast. Marketing managers feel it when the content calendar goes stale. Agency leads feel it when clients ask, “Why didn’t we jump on this?” And founders doing their own marketing, honestly, have no time to play detective.
This workflow pulls fresh trend signals daily, turns them into usable content insights, posts the report to Slack, and logs the same ideas into Google Sheets so your calendar stays current.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Slack + Google Sheets, trend reports sent daily
flowchart LR
subgraph sg0["Scheduled Trend Pulse Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Trend Pulse", 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/code.svg' width='40' height='40' /></div><br/>Trend Setup Builder"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Batch Query Splitter", 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/code.svg' width='40' height='40' /></div><br/>Query Assembly Logic"]
n4@{ icon: "mdi:cog", form: "rounded", label: "Social Trend Scraper AI", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Google Trends Scraper AI", pos: "b", h: 48 }
n6@{ icon: "mdi:cog", form: "rounded", label: "Viral Content Analyzer AI", pos: "b", h: 48 }
n7@{ icon: "mdi:cog", form: "rounded", label: "Reddit Insights Scraper AI", 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/merge.svg' width='40' height='40' /></div><br/>Combine Trend Outputs"]
n9["<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/>Trend Insight Engine"]
n10@{ icon: "mdi:database", form: "rounded", label: "Content Calendar Writer", pos: "b", h: 48 }
n11["<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/>Team Alert Dispatcher"]
n3 --> n4
n3 --> n5
n3 --> n6
n3 --> n7
n8 --> n9
n2 --> n3
n4 --> n8
n5 --> n8
n9 --> n10
n9 --> n11
n0 --> n1
n1 --> 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 n0 trigger
class n10 database
class n1,n3,n9 code
classDef customIcon fill:none,stroke:none
class n1,n3,n8,n9,n11 customIcon
The Problem: Trend Research Becomes “Extra Work”
Trend research is supposed to be a quick input to your content plan. In practice, it turns into a daily scavenger hunt across platforms, then another round of “someone please put this in the sheet.” Even when you do capture ideas, they’re inconsistent: no context, no why-now, no suggested angle, no priority. A week later you can’t tell what’s worth posting, and you end up defaulting back to safe, generic content because it’s easier than sorting the mess.
It adds up fast. Here’s where it breaks down.
- You lose about an hour a day collecting links, screenshots, and notes across multiple platforms.
- Good ideas don’t make it into the content calendar, so they never get assigned, written, or published.
- The team sees trends too late, which means you post after the conversation has already moved on.
- Manual copy-paste creates errors and missing context, so people stop trusting the “trend doc.”
The Solution: Daily Trend Intelligence, Delivered Where You Work
This n8n workflow runs on a daily schedule and monitors trending topics across multiple sources. It builds a set of search queries for your target industries, then uses AI-powered scraping to pull trend signals from social platforms and search interest data. Next, it combines those sources into a single dataset and generates a cleaned, actionable report: what’s trending, what’s driving engagement, and what content angles are likely to work right now. Finally, it sends that report to Slack for the team to act on, and writes the same items into Google Sheets so your content calendar (or idea backlog) stays up to date without anyone doing admin work.
The workflow starts with a daily trigger in n8n. From there, it batches your queries and runs several scrapers in parallel (social trends, Google Trends, viral content patterns, and Reddit insights). Once everything is merged, a final insight engine formats the recommendations and pushes them to Slack and Google Sheets.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you review trends across LinkedIn, Twitter, Instagram, Google Trends, BuzzSumo, and Reddit. If you spend roughly 10 minutes per platform collecting examples and another 30 minutes turning that into a “shareable” summary, you are at about 90 minutes a day. With this workflow, the daily trigger runs automatically, the scraping and analysis happens in the background, and you get a finished report in Slack plus a row set in Google Sheets. Your time drops to a quick 10-minute review and decision.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Slack for delivering the daily report to your team
- Google Sheets to log trends into a calendar or backlog
- ScrapeGraphAI API key (get it from your ScrapeGraphAI dashboard)
Skill level: Intermediate. You’ll connect accounts, add an API key, and adjust a few configuration fields for your industry and keywords.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Daily schedule trigger. The workflow starts automatically every 24 hours, so you’re not relying on someone to “remember” to do trend research.
Query setup and batching. A setup step builds the topics and industries you care about, then splits them into manageable batches so the scrapers can run reliably even as you add more queries.
Multi-source scraping and analysis. ScrapeGraphAI nodes pull trend and viral content signals (including Google Trends and Reddit). A combine step merges the outputs, then an insight engine turns it into content opportunities and platform-specific notes your team can actually use.
Slack + Google Sheets output. The final report is sent to Slack for visibility and written into Google Sheets for tracking, planning, and later review.
You can easily modify the target industries and keywords to match your niche, then change the report format to fit your team’s planning style. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the workflow to run on a daily cadence so the trend intelligence pipeline refreshes automatically.
- Add the Scheduled Trend Pulse node and open its settings.
- Set Rule to an hourly interval with hoursInterval set to
24. - Connect Scheduled Trend Pulse to Trend Setup Builder.
Step 2: Build Trend Configuration and Batch Execution
Prepare the trend configuration and split queries into manageable batches for processing.
- Open Trend Setup Builder and confirm the JavaScript Code contains your industry lists, platforms, and content calendar settings.
- Keep the generated date and session values as defined in the code for consistent reporting, including the
date: '2025-07-25'field. - Connect Trend Setup Builder to Batch Query Splitter to enable batched processing.
- Leave Batch Query Splitter settings as default unless you need to control batch size in advanced scenarios.
totalQueries output during testing.Step 3: Set Up Query Assembly and Parallel AI Scrapers
Assemble the current query and scrape trend data from multiple sources simultaneously.
- In Query Assembly Logic, confirm the batch index is pulled from
$('Batch Query Splitter').item.jsonand the current query is selected from the combined arrays. - Verify that Query Assembly Logic outputs currentQuery, batchIndex, and totalBatches.
- Connect Query Assembly Logic to Social Trend Scraper AI, Google Trends Scraper AI, Viral Content Analyzer AI, and Reddit Insights Scraper AI.
- Set Social Trend Scraper AI Website URL to
{{ $json.currentQuery.search_url }}. - Keep Google Trends Scraper AI Website URL as
https://trends.google.com/trends/explore?date=now%207-d&geo=US. - Keep Viral Content Analyzer AI Website URL as
https://buzzsumo.com/trending-now. - Set Reddit Insights Scraper AI Website URL to
{{ 'https://www.reddit.com/r/' + $json.currentQuery.industry.replace(/\s+/g, '') + '/hot/' }}.
Query Assembly Logic outputs to Social Trend Scraper AI, Google Trends Scraper AI, Viral Content Analyzer AI, and Reddit Insights Scraper AI in parallel.
Step 4: Combine and Analyze Trend Data
Merge the AI scraping outputs and generate the unified trend intelligence report.
- Set Combine Trend Outputs to Mode
combine. - Connect Social Trend Scraper AI and Google Trends Scraper AI into Combine Trend Outputs to align multi-source data.
- Connect Combine Trend Outputs to Trend Insight Engine.
- Review Trend Insight Engine to confirm it merges trending_topics, calculates trend_health_score, and builds recommended_actions.
Step 5: Configure Output and Team Notifications
Write trend-driven content ideas to Google Sheets and alert the team in Slack.
- In Content Calendar Writer, set Operation to
append. - Set Document ID to your sheet URL:
[YOUR_ID]and Sheet Name toContent_Calendar_2025. - Confirm column mappings use the provided expressions, such as Date
{{ new Date().toISOString().split('T')[0] }}and Session_ID{{ $('Trend Insight Engine').item.json.session_id }}. - In Team Alert Dispatcher, set Channel to
[YOUR_ID]. - Keep the Slack Text message as the expression block that references
{{ $('Trend Insight Engine').item.json.trend_health_score }}and other summary fields. - Connect Trend Insight Engine to both Content Calendar Writer and Team Alert Dispatcher.
Trend Insight Engine outputs to both Content Calendar Writer and Team Alert Dispatcher in parallel.
Step 6: Test and Activate Your Workflow
Validate the workflow end-to-end and switch it on for daily trend monitoring.
- Click Execute Workflow to run a manual test from Scheduled Trend Pulse.
- Verify that Content Calendar Writer appends a new row to
Content_Calendar_2025and includes Session_ID and Trend_Score values. - Check Slack to confirm Team Alert Dispatcher posts the formatted trend report message.
- Fix any errors in the scrape or write steps, then re-run until the execution completes without failures.
- Toggle the workflow to Active to enable daily automated runs.
Common Gotchas
- Slack credentials can expire or need specific permissions. If things break, check the n8n Slack credential and your Slack app/workspace access first.
- If you’re using Wait nodes or external scraping, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- ScrapeGraphAI prompts and defaults can be a little generic. Add your brand voice and “what to prioritize” rules early or you will be editing outputs every morning.
Frequently Asked Questions
About 15 minutes if your accounts and API key are ready.
No coding is required for the core setup. You will mostly connect accounts, paste an API key, and tweak a few configuration fields.
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 ScrapeGraphAI API usage costs based on how many queries you run daily.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. This specific workflow uses community nodes, so self-hosting is typically the safer choice for compatibility. If you go that route, plan for basic server upkeep like updates and backups.
Yes, and you should. Most teams customize the “Trend Setup Builder” and “Query Assembly Logic” steps to define industries, keywords, and platforms, then adjust the “Trend Insight Engine” rules so the report outputs the fields you care about (hooks, angles, titles, or priority scores). You can also reduce sources if you want a lighter report, or add more queries if you’re running multiple brands. If you already keep an editorial calendar format in Google Sheets, map the output fields to your existing columns so the workflow fits your process instead of replacing it.
Usually it’s expired credentials or missing permission scopes in your Slack connection inside n8n. Reconnect Slack in n8n, confirm the workflow is posting to the right channel, and double-check that your Slack workspace allows the app to post messages. If it works once and then stops, rate limits can also show up when you expand to lots of queries.
If you self-host, there’s no hard execution limit, but your server and your scraping API limits become the real bottleneck.
For multi-source trend scraping and “merge + analyze + write” logic, n8n is usually a better fit than Zapier or Make because you can branch, batch, and transform data without paying for every little step. The batching and merging matter here because you’re pulling multiple sources and combining them into one report. Also, this workflow uses community nodes, which Zapier and Make won’t support in the same way. If you only want a simple “Google Trends result to Slack message,” those tools can be fine, but you’ll hit ceilings quickly once you want scoring, prioritization, and structured Sheets logging. If you’re on the fence, Talk to an automation expert and describe your volume and channels.
Once this is running, your trend research stops being a daily scramble and starts showing up like a utility. The workflow handles the repetitive collection and formatting so you can spend your time choosing angles and publishing.
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.