Hacker News to Google Docs, shareable trend briefs
Keeping up with Hacker News sounds easy until you actually do it. A few “quick checks” turn into 20 tabs, half-read comment threads, and a messy doc you still need to rewrite.
This is where HN brief automation pays off. Newsletter writers feel it first, but founders tracking their space and consultants building client updates run into the same grind. You want a clean trend brief you can share, not another pile of links.
This workflow pulls trending HN posts, has Gemini turn them into readable insights, and publishes everything into a Google Doc. You’ll see what it does, what you need, and what to watch out for.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Hacker News to Google Docs, shareable trend briefs
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", 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/hackernews.png' width='40' height='40' /></div><br/>Hacker News"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n3@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Create a Google Doc", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Update Google Docs", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set the Input Fields", pos: "b", h: 48 }
n7@{ icon: "mdi:robot", form: "rounded", label: "Extract Human Readable Data", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set the url, author", pos: "b", h: 48 }
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/httprequest.dark.svg' width='40' height='40' /></div><br/>Create an HTTP Request"]
n1 --> n2
n2 --> n8
n5 --> n2
n4 --> n5
n8 --> n9
n6 --> n1
n9 --> n7
n3 -.-> n7
n7 --> n4
n0 --> n6
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 n7 ai
class n3 aiModel
class n9 api
classDef customIcon fill:none,stroke:none
class n1,n9 customIcon
The Problem: Trend research turns into tab chaos
Hacker News is great at surfacing what people care about right now. The problem is everything after you find a thread. You open the post, skim the comments, grab the link, copy the author, then try to summarize what’s actually happening in plain English. Do that 10 times and you’ve burned about an hour, and you still don’t have something you’d feel good sending to a client or publishing in a newsletter. Worse, the summaries end up inconsistent because you’re rushing.
It’s not one big failure. It’s dozens of tiny frictions stacked together.
- You keep re-reading the same threads because nothing is captured in one place.
- Copy-paste errors sneak in, so links or attributions end up wrong.
- Summaries vary wildly depending on how busy you are that day.
- Sharing is awkward because your “draft” is usually a pile of raw notes.
The Solution: Turn trending threads into a Google Doc brief
This workflow takes the “research → summarize → format → share” loop and turns it into one repeatable run in n8n. You start it (manually, or later on a schedule if you want). n8n pulls a list of trending Hacker News items, then processes them in batches so you’re not hammering APIs or dealing with timeouts. For each item, it maps the key fields (title, URL, author), fetches extra context via an HTTP call, and hands that content to a Gemini-powered summarizer. Finally, it generates a Google Doc and inserts each enriched summary into the doc in a consistent format, so it reads like a briefing instead of scraped data.
The workflow begins by fetching the HN feed. Then it loops through each post, pulls the content it needs, and asks Gemini for a readable summary with actual takeaways. At the end, Google Docs becomes the “single place” where your trend brief lives, ready to share or archive.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you want a weekly brief with 10 trending HN discussions. Manually, assume about 6 minutes each to open the thread, skim, grab the link/author, and write a decent summary. That’s roughly an hour, and you still have to format it for sharing. With this workflow, you spend maybe 5 minutes kicking it off and scanning the finished Google Doc, then you send one link. The “busywork” hour mostly disappears.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Hacker News API to pull trending discussion items.
- Google Gemini to generate human-readable summaries.
- Google Docs to publish and share the briefing.
- Gemini API key (get it from Google AI Studio/Google Cloud).
Skill level: Intermediate. You’ll connect accounts, add API credentials, and tweak a prompt, but you won’t be writing an app.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Trigger a run when you need a new brief. The workflow starts from a manual trigger, then reads your input settings (like how many items to pull) so you control the scope.
Pull the latest items from Hacker News. n8n fetches the HN feed and prepares the list for processing, which keeps your “source of truth” simple and repeatable.
Batch through each thread and enrich it. Items are processed in batches, mapped into a clean structure (URL, author, title), then an HTTP request grabs any extra content needed for a stronger summary.
Generate the brief and publish it. Gemini produces a readable summary, n8n creates a Google Doc, and each item gets inserted in a consistent format so the final result feels like a briefing you can share.
You can easily modify the number of posts pulled to match your cadence, or adjust the summary format to fit your newsletter template. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow manually to control when the news summarization run begins.
- Add the Manual Start Trigger node as the workflow trigger.
- Leave all default settings in Manual Start Trigger as-is.
- Connect Manual Start Trigger to Configure Input Values.
Step 2: Connect the News Data Source
Set the number of items to fetch and pull the latest Hacker News items.
- Open Configure Input Values and add a string field named Count with the value
5. - In Fetch News Feed, set Resource to
all. - Set Limit to
={{ $json.Count }}in Fetch News Feed. - Connect Configure Input Values to Fetch News Feed, then to Batch Iterate Items.
⚠️ Common Pitfall: If Count is missing or not a string, Fetch News Feed will not return the expected number of items.
Step 3: Set Up Content Mapping and Retrieval
Map each story’s URL and author, then fetch the linked page content.
- In Map URL and Author, set author to
={{ $json.author }}. - Set url to
={{ $json._highlightResult.url.value }}in Map URL and Author. - Connect Batch Iterate Items to Map URL and Author.
- In External HTTP Call, set URL to
={{ $json.url }}and keep retry enabled. - Connect Map URL and Author to External HTTP Call.
⚠️ Common Pitfall: Some Hacker News items may not have a valid url field, so verify your dataset if HTTP requests fail.
Step 4: Set Up the AI Summary and Google Docs Output
Generate a readable summary with Gemini and write it into a Google Doc.
- Open Generate Readable Summary and set Text to
=Extract a human readable content. Here's the context : {{ $json.data }}. - Ensure Gemini Chat Engine is connected as the language model for Generate Readable Summary and set Model to
models/gemini-2.0-flash-exp. - Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine (credentials are added to the parent model node, not the chain node).
- In Generate Google Document, set Title to
={{ $('Map URL and Author').item.json.author }}-HackerNewsand Folder ID todefault. - Credential Required: Connect your googleDocsOAuth2Api credentials in Generate Google Document.
- In Insert Doc Content, set Operation to
updateand Document URL to={{ $json.id }}. - In Insert Doc Content, add an action with Text set to
={{ $('Generate Readable Summary').item.json.text }}and Action set toinsert. - Credential Required: Connect your googleDocsOAuth2Api credentials in Insert Doc Content.
⚠️ Common Pitfall: If the document URL input is incorrect, Insert Doc Content won’t update the right file.
Step 5: Test and Activate Your Workflow
Run a manual test to confirm content flows from Hacker News to Google Docs, then activate for production use.
- Click Execute Workflow to run Manual Start Trigger.
- Verify Fetch News Feed returns the number of items set in Configure Input Values.
- Confirm Generate Readable Summary outputs a summarized text field.
- Check Google Docs to ensure a new document is created by Generate Google Document and populated by Insert Doc Content.
- Toggle the workflow to Active when the test succeeds.
Common Gotchas
- Google Docs credentials can expire or need specific permissions. If things break, check your Google connection in n8n’s Credentials and the Google account access 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 Google and Gemini access are ready.
No. You’ll connect accounts, paste an API key, and edit a prompt.
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 Gemini API usage costs, which depend on how many items you summarize and how long your prompts are.
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, but plan the format first. Most people customize the “Configure Input Values” step to pull fewer items, then adjust the AI summary prompt so it outputs short sections (headline, why it matters, one notable comment theme). You can also change the Google Docs insert step to add a dated heading for each run. If you want a daily send, swap the manual trigger for a schedule trigger in n8n.
Usually it’s expired or revoked Google OAuth access. Reconnect the Google Docs credential in n8n, then confirm the Google account actually has permission to create and edit Docs in the target Drive. If you’re working inside a company Google Workspace, an admin policy can also block third-party app access, which looks like “random” failures. Finally, check if the workflow is inserting content into a Doc ID that no longer exists.
Plenty for a normal brief. If you self-host, it mostly depends on your server and how hard you push Gemini and Google Docs rate limits. On n8n Cloud, your monthly execution limit depends on your plan, so higher volume usually means upgrading. In practice, most teams keep it to 10–30 items per run so the doc stays readable and costs stay predictable.
Often, yes. This kind of workflow tends to need batching, looping, and a bit of “shape the data before you write the doc,” and n8n is strong there without charging you extra for every branch. Self-hosting is also a big deal if you run briefs frequently. Zapier or Make can still work if you keep it very simple, but costs can creep up once you start looping over items. If you want a second opinion for your setup, Talk to an automation expert.
Once this is in place, your “HN research” becomes a shareable Google Doc you can rely on. Honestly, it’s a relief to stop rebuilding the same brief from scratch every week.
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.
