Webhook logo
Hacker News logo
Google Sheets logo

Workflow template

Log a Hacker News item in Google Sheets

Look up a Hacker News item from an incoming item_id and append its ID, title, author and discussion link to Google Sheets. Each request creates a row in your selected worksheet using RAW values.

How it works

From a Hacker News item ID to a worksheet snapshot

1 Trigger · 2 Actions
Webhook1 · Trigger

Item lookup webhook

Receive item_id in the JSON body. This requests one item rather than subscribing to new stories or importing the whole Hacker News feed.

Hacker News2 · Action

Read Hacker News item

Read the requested public item using the Hacker News connection, which needs only a local label. The following row uses returned id, title, by and discussion_url.

Google Sheets3 · Action

Append item to worksheet

Append the returned item ID, title, author and Hacker News discussion link in A:D. RAW input preserves text as text; the workflow does not upsert or synchronize an existing row.

The result

A four-column item lookup record

Four returned fields in A:D of an existing worksheet. Add the shown labels manually if wanted.
Item IDTitleAuthorDiscussion link
123FICTIONAL workshop planning notesfictional_authorhttps://news.ycombinator.com/item?id=123

Illustrative returned-item fixture for the sample item_id: 123, not a claim about that real item's title or author. The link is the Hacker News discussion, not the story's external source URL.

Before activation

Set up your workflow

  1. Connect Hacker News with a local label

    Create the public Hacker News connection using a local label. Prepare a valid item_id for lookup; the source is your incoming webhook rather than a new-story trigger.

  2. Choose the Google Sheets destination

    Connect Google Sheets and select an existing spreadsheet and worksheet. Reserve A:D for item ID, title, author and discussion link, with RAW and INSERT_ROWS. Add labels manually if desired.

  3. Compare a controlled item lookup

    Protect the webhook, activate and send one item_id request. Compare the appended values with the returned item, then send again only if another snapshot row is intended.

Details and limitations
  • The discussion link is separate from the source article. The row maps discussion_url from the Hacker News action. It does not copy the external article URL, article body, comments, score or a lookup timestamp.

  • Item fields depend on the item type. Not every Hacker News item has a story title or author field. Choose a suitable item and inspect its output before relying on populated title/author columns; no fallback title is generated by the mapping.

  • Each request appends another snapshot. This is not an upsert or feed import. Later edits do not update an existing row, and repeated requests or manual reruns can append duplicates. RAW keeps formula-looking titles as text.

Questions about this template

Does the Hacker News connection require an API key?

No. Create the public connection with a local label, then connect Google Sheets for the destination. Send the item_id to the workflow webhook.

Is the copied link the article's external URL?

No. It is the returned Hacker News discussion_url. The row also has item ID, title and author; article body, comments, score and lookup time are not mapped.

Will every item have a title and author?

No. Available fields depend on the item type and state. Inspect a suitable item's output; the mapping does not generate a fallback title or author.

Will requesting the same item update its existing row?

No. Each accepted lookup appends a new row with RAW values. There is no upsert, scheduled feed import or synchronization of later changes, and reruns can duplicate rows.

Explore connected apps