- Home
- Resources
- Integrations
- Hacker News
Hacker News n8n integrationAutomate Hacker News with n8n.
Reading Hacker News by hand stops working the day it becomes a daily job. The Hacker News n8n integration exposes 3 operations spread over 3 resources: search the whole index, pull one article with its comment thread, look up a user. No trigger node ships with it, so a schedule or a webhook starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Hacker News n8n integration actually do?
The Hacker News node ships inside n8n and reads the public Hacker News API. It covers 3 resources, All, Article and User, with 1 operation each, so a workflow can search the whole index, fetch a single story together with its comments, or pull one user record. Nothing goes back the other way: from n8n, Hacker News is read-only.
Start with the watch scenario, because it is the one people build first. A schedule runs every morning, the node searches for a product name with the Keyword field, the Tags field keeps only story and show_hn, and the rows land in Google Sheets next to the ones from last week. Nobody opens the site to find out a launch got picked up.
Second scenario: a single thread that matters. One story gets traction, so the workflow calls the Article resource with Include Comments switched on, hands the discussion to a model or a filter, and posts the short version to Slack. The comment thread is where the signal usually is, and it arrives in the same run as the article.
Third, the person behind the post. The User resource takes a handle and returns that account, which is enough to decide whether an author is worth a follow-up. Send the result to Telegram if the workflow is a personal alert rather than a team channel.
When the node stops short, switch to HTTP Request. That node calls any endpoint of the API directly, and it stays the right answer for anything outside these 3 operations. Hacker News stays read-only from n8n either way: the node only fetches data, nothing gets written back to Hacker News from a workflow.
Two limits worth knowing before you build. Search results are paginated, so Return All off means the run stops at Limit and a quiet workflow silently misses items. And there is no trigger node for this tool, which means the workflow never wakes up on its own; a Schedule Trigger or an n8n Webhook, an URL a third-party service calls, has to start it. The n8n review covers how that plays out on bigger setups, and the n8n training walks through building one end to end.
How do you connect Hacker News to n8n?
- 01
Add the node to a workflow
Open the node panel in n8n and search for Hacker News. The node is called
n8n-nodes-base.hackerNewsand its one-line description, Consume Hacker News API, tells you what it is scoped to. It ships with n8n, on n8n Cloud and on a self-hosted instance alike, so there is no package to install and no extra cost on the n8n side. - 02
Skip the credential step
This node does not require authentication. There is no API key to generate, no token to paste, no entry to create in the Credentials menu of n8n. That is unusual: most nodes ask you to save a credential once and then reuse it across every workflow. Here the dropdown simply is not there, and a fresh n8n instance can call Hacker News in its first minute.
- 03
Pick a resource, then an operation
The node starts with a Resource choice, All, Article or User, and each one carries a single operation. All searches items, Article returns one story, User returns one account. Choosing the resource first is what changes the fields below, so set it before filling anything in, otherwise you configure a form that is about to be replaced.
What the Hacker News node can do
The Hacker News node exposes 3 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Operations index
All
1 operationGet many items
all.getAllWhat you see in n8n
Notes & use cases
Runs a search across the Hacker News index and returns every matching item as its own n8n item, ready for whatever node comes next.
Key parameters
- Return All: on, n8n chains the pages of the API until nothing is left; off, Limit sets the maximum number of items that come back.
- Keyword: the term used to filter the results of the query, a product name or a competitor for instance.
- Tags: restricts the query to any of the 6 tags the API exposes,
story,comment,poll,ask_hn,show_hnandfront_page.
story and show_hn, and appends each hit to a sheet.Article
1 operationGet an article
article.getWhat you see in n8n
Notes & use cases
Pulls one Hacker News article by its identifier, so a workflow can work on a specific story instead of a result set.
Key parameters
- Article ID: required, the ID of the article to return. Type it in for a one-off, or map it from an earlier node with an expression such as
{{ $json.id }}. - Include Comments: sits under Additional Fields. Switch it on and all the comments of the article come back with it, in the same item.
User
1 operationGet a user
user.getWhat you see in n8n
Notes & use cases
Looks up a single Hacker News account and returns that user, which is the fastest way to put a face on a handle inside a workflow.
Key parameters
- Username: required, the Hacker News user to return. Spell it exactly as it appears on the site, or feed it from the previous node with
{{ $json.username }}.
Need help automating Hacker News with n8n?
A person reads every message.
Questions people ask next
01Is the Hacker News n8n integration free?
02What credentials does the Hacker News node need in n8n?
03What are the limits of the Hacker News node?
04Does the Hacker News node react in real time?
05n8n or Make for Hacker News?
Get our weekly integration tips.
No spam. Unsubscribe anytime.



