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.

Agentic Task
beehiivBitlySlack BotMarketingContent GenerationNotifications & Alerts
PromptCreate

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

New issue live: The Compounding Loop Why small weekly systems beat big quarterly pushes *LinkedIn* Most teams overhaul their process once a quarter, then wonder why nothing sticks. This week's issue breaks down why weekly systems compound while quarterly pushes stall, plus the three checks we run every Friday. Link: bit.ly/3xLnKd9 *X* Big quarterly overhauls feel productive. Weekly systems actually compound. New issue on why: Link: bit.ly/3pQrTz2 *Internal* New issue is live on why weekly systems beat quarterly pushes. Grab your link and share it if it fits your feed. Link: bit.ly/4aBcVw1

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?
No. It writes the copy and prepares the links, then hands the finished kit to your team in Slack. Everyone shares from their own account, which usually gets better reach than posting from a company page.
How do I know which channel actually drove traffic?
Each channel gets its own short link, so your link dashboard shows the clicks separately instead of one blended number. Comparing LinkedIn against X becomes a matter of reading two rows.
What happens to drafts and premium-only issues?
Nothing at all. The workflow only runs for posts that are actually live to your free or public audience, so work in progress and paid-subscriber-only issues are skipped.
Do I need a paid Bitly plan?
A standard Bitly account is enough to create the short links this uses. Branded domains and some advanced reporting do require a paid plan, but the workflow runs fine without them.
Can the team edit the copy before posting?
Yes. The copy arrives as a draft in Slack, ready to copy and paste, so anyone can tweak the wording to sound like themselves before sharing.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

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.