Auto-post to social media from GitHub

The `release` event with `types: [published]` fires whenever a release is published on the repo, and the event payload's `release` object carries everything a post needs, including `release.name` and `release.html_url` (both confirmed fields on GitHub's release object, per the REST API's release response schema). The workflow below reads those two fields and posts a one-line announcement to a Discord webhook - the same pattern works for Slack's incoming-webhook URL format with the payload shape adjusted, or any endpoint that accepts a JSON POST.

This is genuinely enough to auto-post your first release announcement today: create the webhook in your destination, add it as a repository secret, and paste the workflow in. What it will not do is adapt the message per channel, hold it for review, or handle more than one destination without you copying the step - which is exactly the gap the rest of this guide is about.

Schedulers (Buffer, Hootsuite, Typefully, Postiz and the rest) automate the publish stage only: you still decide, write, and adapt, then queue everything to go out at chosen times - your repo never enters the picture. Event-driven automation, the family the recipe above belongs to, starts one stage earlier and at the source: a real GitHub event - a release, a merged pull request, a changelog update - triggers a draft automatically, so deciding and drafting are largely absorbed by the event itself. Pure AI drafting tools attack the blank page from a prompt, which helps when your content is editorial opinion rather than shipped work, but still needs someone to write the prompt.

The table below is the comparison to run before picking a method. If your content is your product - you ship, and the shipping is the story - event-driven automation triggered by your repo removes two more stages than a scheduler can, because the event carries the facts a draft needs.

X and LinkedIn both require an authenticated API call rather than a plain webhook POST, since neither accepts anonymous incoming webhooks the way Discord and Slack do - the GitHub Actions recipe above needs an API client step in place of the `curl` call, with the platform's API credentials stored as repository secrets. Instagram and TikTok are a different case again: both are built around image or video posts first, so a text-only release announcement is a weak fit for either platform even once the API call works, which is worth knowing before you spend the setup time.

Reddit and Hacker News are deliberately not part of this recipe. Both communities penalize automated, identical-looking submissions, so a release-triggered auto-post is the wrong tool for either destination - see our Hacker News launch guide for why that channel specifically wants a human, not a script.

S2P connects to your GitHub and treats releases, tags, merged PRs, and changelog updates as the posting trigger. When a qualifying event fires - you control qualification with rules on semver, branch, path, or label, so dependency bumps stay quiet - it drafts channel-native posts in your brand voice for the channels you connect: 11 native platform integrations (LinkedIn, X, Threads, Bluesky, Mastodon, Reddit, Facebook, Instagram, YouTube, Discord, Slack) plus Hacker News, Substack, and custom webhooks - 14 channels in total. Drafts land in a review queue; nothing publishes until a human approves, unless you explicitly switch a channel to autonomous mode.

That design is the recipe above with the gaps filled in: authenticated API calls per platform instead of a single webhook, channel-native adaptation instead of one message shape, and an approval step instead of nothing. Pricing, as of July 2026: a free plan (one repo, two social channels, one post a day) to feel the loop, and paid plans from $5 per month billed yearly ($6 monthly) to remove the branding and add channels - details on the pricing page.

If you want to feel the drafting quality before connecting anything, the free changelog-to-social generator takes pasted release notes and produces posts for six channel styles in your browser, no login. And if you are technical enough to want the DIY route further, the honest build-vs-buy comparison lives in our GitHub Actions vs webhooks decision matrix - DIY, like the recipe above, is genuinely fine for one channel and a tolerance for maintenance.

Automated accounts feel robotic for three reasons, and none of them is automation itself. First, identical cross-posting: the same text, same hashtags, same link card on every channel reads as broadcast, because it is - a single webhook message posted verbatim to five platforms is the fastest way to trigger this. Second, volume without selection: when every commit or trivial patch becomes a post, followers learn that nothing you post is signal. Third, missing authorship: no reactions, no replies, no human in the comments - the account publishes but never participates.

The fixes are structural, not cosmetic. Adapt per channel so each post is native (a compressed line on X, context on LinkedIn, no hashtags on Reddit or Discord) - a raw webhook recipe cannot do this on its own, which is the real gap between a first wire-up and a real pipeline. Gate volume with qualification rules so only releases with a story go public. And keep a human on approval and in the replies: automation should hand you a finished draft, not take over your keyboard.