Turn every new beehiiv issue into a push notification
When a new free issue publishes, an agent writes three push headline options, sends the strongest one to your subscribers, and shares the alternates in Slack.
Whenever I publish a new post in beehiiv, turn that issue into a push notification for my app and web subscribers, without me rewriting the subject line by hand. Use a poll trigger on beehiiv new post so this runs the moment an issue goes live.
First decide whether this issue should be pushed at all. Take the post id from the trigger and call beehiiv Get Post with the content expansion, so you read the actual body of the issue rather than just the title. Only continue if the post is actually published and free to read. If it is still a draft, or it is a premium subscriber only issue, stop and send nothing, because I do not want to push anyone to a paywall. If the trigger payload does not carry enough detail to judge status or audience, confirm with beehiiv List Posts using its status and audience filters before going any further.
Then write the push copy. Working from the body, write three push headline options, each under about 60 characters. Every option should lead with the single most interesting or surprising thing in the issue, such as a specific number, a claim, or a striking phrase pulled from the text. Do not simply restate the email subject line, because a push that repeats the subject line gets ignored. Pick the strongest of the three and note in one sentence why it won.
Resolve my target audience with OneSignal View Segments and choose the segment that holds my newsletter push subscribers. Send the winning headline with OneSignal Create Message. This is a push send, so set the message contents together with a single included segment, and set exactly one targeting method on the message. Include a link back to the post's web URL so tapping the notification opens the published issue. Derive one idempotency key from the beehiiv post id and reuse that same key on every attempt, so a retry can never double push the same issue to the audience.
Finally, post to Slack with Send a Message to my editorial channel. Show which headline went out, the two runners up, the one sentence explaining why the winner was chosen, and a link to the post, so my editor can see the reasoning and reuse the alternates for social.
What does this prompt do?
- Watches your newsletter and fires the moment a new issue goes live, with no scheduling on your side
- Reads the actual body of the issue, not just the subject line, then writes three push headlines under about 60 characters that lead with the most surprising thing inside
- Sends the strongest headline to the audience you choose, with a tap straight through to the web version of the post
- Skips anything still in draft and any subscriber only issue, so nobody gets pushed to a paywall
- Posts the winning headline plus both runners up to Slack, so your editor can see the reasoning and reuse the alternates for social
What do I need to use this?
- A beehiiv account with a publication you send issues from
- A OneSignal account with push set up for your app or website, and at least one audience segment to send to
- A Slack workspace and a channel where your editorial team can see what went out
How can I customize it?
- Change which audience gets the push, for example everyone or only your app users
- Adjust the headline length limit or the tone, such as more playful or more newsy
- Decide what happens with premium issues: skip them entirely, or send a teaser push that points at the signup page
- Pick which Slack channel the recap lands in, or route it to a direct message instead
FAQs
Will this push my premium, subscriber only issues?
How is the push headline different from my email subject line?
Can I see the headline before it goes out?
What stops the same issue from being pushed twice?
Do I need a mobile app for this to be useful?
Related templates
When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.
Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Every Monday, rank the week's matches by expected demand, put the big ones on your venue calendar, and post a rota-ready summary to Slack.
Every Tuesday we pull your best new reviews, draft social captions, email testimonials and product page quotes, then stage them in Notion for approval.
Every weekday morning, unfulfilled orders get an address check: harmless typos fixed automatically, risky addresses held with a note to the customer.
Stop letting your best issues sit unread.
Every new issue becomes push copy written for the push channel, sent while the story is still fresh.