Hacker News + n8n: The Complete Integration Guide
Connect Hacker News to n8n to monitor stories and dispatch alerts. Setup, triggers, actions, and production patterns.
Key takeaways
- Hacker News authenticates with n8n via OAuth or API key — pick OAuth for user-facing flows and API key for service accounts.
- Triggers (webhooks and polling) start workflows on Hacker News events; actions call Hacker News from any other workflow.
- Use the HTTP Request node to reach Hacker News endpoints the built-in node doesn't cover yet — the auth is reused.
- Rate limits, retries, and idempotency are the three biggest Hacker News production gotchas — handle them explicitly.
Hacker News is one of the most-used tech community platforms — and n8n is the fastest way to wire it into the rest of your stack without writing glue code. In this guide you'll set up authentication, pick the right triggers, and learn how teams use the Hacker News node in production to monitor stories and dispatch alerts.
Connecting Hacker News to n8n
Open Credentials in n8n and create a new Hacker News credential. Choose OAuth when a human should authorize on their own account, or an API key / access token for background workflows owned by an operations account. Store the client ID and secret from the Hacker News developer console; n8n handles the callback and refresh tokens automatically.
After the credential is saved, add a Hacker News node to any workflow and select the credential. Test the connection with a read-only action (list, get, or search) before wiring writes — a green execution proves the scopes are right.
- Grant only the minimum Hacker News scopes your workflow needs.
- Use one credential per environment (dev, stage, prod) and never share across projects.
- Rotate keys quarterly and immediately after any contractor offboards.
Triggers and actions
The Hacker News Trigger node starts a workflow when something happens in Hacker News — a new record, a status change, an inbound message, or a webhook event. Prefer webhooks over polling when Hacker News supports them; polling burns credits and adds latency.
Actions run from any node position and let you monitor stories and dispatch alerts. Chain them with Set, If, and Merge nodes to build the exact business rule you need without touching code.
Production patterns for Hacker News
Wrap every Hacker News write in retries with exponential backoff — the API will throw 429s during traffic spikes and you don't want to lose events. Add a dedupe step (Redis SETNX or a Postgres unique index) so a retried webhook doesn't create duplicate records.
For high-volume workflows, run n8n in queue mode with a Redis broker and separate workers. That way Hacker News throughput stops fighting with your other automations for the same CPU.
- Verify webhook signatures — never trust the payload alone.
- Log the full {name} response on failure so you can replay it later.
- Alert on 5xx rates, not just outages — silent degradation is the real killer.
Frequently asked questions
- Is there an official Hacker News node in n8n?
- Yes. n8n ships a first-party Hacker News node with common triggers and actions; use the HTTP Request node for endpoints the built-in node doesn't cover yet.
- OAuth or API key for Hacker News?
- OAuth for user-owned data, API key or service account for background workflows. Never share personal OAuth tokens across a team.
- How do I handle Hacker News rate limits?
- Add a Wait node between calls, use Split In Batches to control concurrency, and enable retries with exponential backoff at the node level.
- Can I self-host n8n and still use Hacker News?
- Yes — the same node works self-hosted. Make sure your n8n instance is reachable from the internet if you need inbound webhooks from {name}.