Turn new beehiiv posts into a tracked Slack share kit
When a new issue goes live, your team gets ready-to-paste share copy and a separate tracked link per channel, all in one Slack message.
When a new post is published in my beehiiv publication, build a distribution share kit and drop it into Slack so the team can amplify the issue the same morning. Use a poll trigger on beehiiv for new posts.
Start with beehiiv's Get Post to pull the post's title, subtitle, web URL, slug, status, and audience. Only continue for posts that are genuinely live to the free or public audience. If the post is still a draft, or it is restricted to a premium or paid-only audience, stop the run and post nothing. Handle each post once so a single issue never produces two share kits.
For each of the three distribution channels, LinkedIn, X, and internal team sharing, create its own tracked short link using Bitly's Create a Bitlink. Every link points at the same post web URL, but each carries its own UTM tagging so clicks can be compared per channel later: set utm_source to linkedin, x, or internal, set utm_medium to social for LinkedIn and X and to internal for the team link, and set utm_campaign to the post slug. Tag every Bitlink with the post slug and give it a title naming both the post and the channel, so the three links stay grouped and easy to find in Bitly when it is time to compare them.
Then draft short share copy for each channel, written in the newsletter's own voice rather than generic promo language. Use the title and subtitle as raw material, and give each channel a genuinely different angle on the post instead of repeating the headline three times. LinkedIn gets two or three sentences that lead with the insight and read as professional but not stiff. X gets a punchy hook under 280 characters. The internal version gets one or two sentences a teammate can paste into their own feed or forward to a contact without editing.
Finally, post the whole kit as a single Slack message using the Slack Bot integration's Send a Message, sending it to the team's marketing channel. Lead with the post title and subtitle, then include one clearly separated block per channel showing that channel's draft copy directly alongside its matching tracked link. Format it so a teammate can copy a block straight out of Slack and paste it where it belongs with no cleanup.
Example output
Additional information
What does this prompt do?
- Watches your newsletter and kicks in as soon as a new issue is published, skipping anything still sitting in draft.
- Creates a separate short, trackable link for each place you plan to share: LinkedIn, X, and your internal team.
- Writes ready-to-post share copy for each channel in your newsletter's own voice, so nothing reads like the same line pasted three times.
- Drops the whole kit into Slack as one message, with each channel's copy sitting right next to its own link.
What do I need to use this?
- A beehiiv account with a publication you send from
- A Bitly account for creating the short links
- A Slack workspace and a channel where the team picks up the share kit
How can I customize it?
- Change which channels get their own link and copy, for example adding Reddit or a newsletter-swap partner.
- Pick the Slack channel the kit lands in, or send it as a direct message to whoever runs distribution.
- Adjust the tone and length of the copy per channel, or limit the whole thing to issues carrying a certain tag.
FAQs
Will this post to LinkedIn or X for me?
How do I know which channel actually drove traffic?
What happens to drafts and premium-only issues?
Do I need a paid Bitly plan?
Can the team edit the copy before posting?
Related templates
Every weekday, find every unpaid JobNimbus invoice, email each customer one reminder that gets firmer as it ages, and post a receivables summary to Slack.
Every weekday at 7am, your active courses are checked for missing work, silent logins, and slipping grades, with a ranked list sent to your advising channel.
Every hour, find the tickets closest to breaching, leave a nudge on each one, and post a ranked at-risk list to your support channel.
Every weekday afternoon, each student who is behind gets a warm, personal message in their Canvas inbox listing exactly what they owe.
Every Monday at 8am, see exactly which assignments have work waiting, sorted worst first, posted to Slack and logged to a spreadsheet.
Every weekday morning we compare your password vault against your HR records and suspend access for anyone who has already left.
Stop rebuilding the same share kit every issue.
Publish the newsletter and let the copy, the links, and the tracking be waiting in Slack before the team logs on.