Hacker News logo
DeepL logo
ntfy logo

Workflow template

Send Russian Hacker News headlines to ntfy

Receive new Show HN headlines through ntfy with a Russian title translated by DeepL. Keep the original English headline and discussion link in the notification body.

How it works

From a new Show HN story to a translated phone notification

1 Trigger · 2 Actions
Hacker News1 · Trigger

New Show HN story

Record the current Show HN feed on the initial silent poll, then observe new arrivals. Existing stories are not sent as an initial backlog.

DeepL2 · Action

Translate to RU

Translate the story title into Russian using target language RU. Only the headline is sent to DeepL; the article and comments are not fetched or translated.

ntfy3 · Action

Send translated headline

Publish to your selected ntfy topic with the first translated text as the notification title. Keep the original headline and Hacker News discussion URL in the message body.

The result

A Russian notification title with its original source below

Illustrative ntfy Show HN notification

Show HN: вымышленный инструмент для мастер-классов

Show HN: Fictional workshop tool https://news.ycombinator.com/item?id=123

Illustrative translation of the fictional sample headline, not a live DeepL result. Actual translated wording can differ. The link format comes from the template sample.

Before activation

Set up your workflow

  1. Connect the Show HN source and DeepL

    Select the Hacker News connection and connect DeepL. Review the fixed RU target language and headline-only text mapping. Each new headline consumes DeepL characters.

  2. Choose and subscribe to your ntfy topic

    Connect ntfy, set the destination topic and subscribe to that same topic on your phone. Review the topic’s access settings and audience on your chosen ntfy server.

  3. Wait for a new story after the initial poll

    Activate and let the first silent poll record the current feed. On a later arrival, compare the Russian notification title, original headline and discussion link. Source arrivals determine when there is something new to send.

Details and limitations
  • Only the headline is translated. DeepL receives trigger.title and translates to RU. The notification body retains the original title and discussion URL. No article text, comment thread or summary is included.

  • The first poll is silent. It records the current Show HN feed rather than notifying for its backlog. Subsequent new arrivals are processed. This is polling, so a notification is not guaranteed immediately when a story appears.

  • A topic subscription is needed on your phone. Publishing to ntfy does not subscribe your device automatically. Use the same topic in the workflow and your ntfy client; visibility depends on your server and topic configuration.

  • Translation usage and reruns apply. Each translated headline consumes DeepL characters. Manual reruns can translate and notify again. Adopting this template does not change your existing workflows.

Questions about this template

Is the whole story translated into Russian?

No. Only the Show HN headline is passed to DeepL with target language RU. The ntfy body contains the original headline and discussion link, not the article or comments.

Why is there no notification on the first poll?

The first poll silently records the current feed. Later new Show HN arrivals are processed, so the existing feed is not sent as a backlog.

How do I receive these notifications on my phone?

Choose your ntfy topic in the action and subscribe to that same topic in your phone’s ntfy client. The workflow publishes messages but does not subscribe a device for you.

Does this use DeepL characters for every new headline?

Yes. Each headline translated by the DeepL action consumes characters. Manual reruns can repeat translation usage and send another notification.