Start free trial
GitHub Action (signed release webhook) · LinkedIn

GitHub releases to LinkedIn posts, approved by a person

Developer tools sell to people who read LinkedIn: engineering managers, platform leads, CTOs. They care about releases, but a raw changelog does not speak to them. With socialhandoff-announce-action, each published GitHub release becomes a LinkedIn draft in SocialHandoff, linked to the release in the audit log. Someone edits it into a short business-facing note and approves. Your CI never holds a LinkedIn token.

Prompt

(GitHub release notes) v3.0.0: Single sign-on with SAML for all plans. New audit log export. Removed the legacy v1 API after 12 months of deprecation notices.

How to do it

  1. Add a release trigger In Connections, create a GitHub release trigger with LinkedIn as its network. Copy the trigger id and signing secret.
  2. Save repository secrets Store the server URL, trigger id, and webhook secret as GitHub Actions secrets.
  3. Add the workflow Create a workflow on release: published that runs socialhandoff-announce-action with those inputs. It sends tag, name, and notes by default.
  4. Publish the release A LinkedIn draft appears in the inbox, citing the release it came from.
  5. Rewrite for the audience Edit the draft for managers rather than developers, then approve.

Example draft

Version 3.0 is out, and it is mostly about the things a security review asks for.

Single sign-on with SAML is now included on every plan, not just enterprise. If your team has been waiting for SSO before rolling us out more widely, that blocker is gone.

Admins can also export the full audit log for any date range.

One removal: the v1 API is retired, after 12 months of notice. If you still call it, the migration guide takes about an hour.

Release notes: https://example.com/releases/v3.0.0

Gotchas

  • The draft starts from raw release notes, which are written for developers. Plan to edit it in the inbox before approving.
  • Markdown in release notes, such as headings and bullet asterisks, shows up literally on LinkedIn. Reserved characters are escaped, not removed.
  • If the signing secret in GitHub does not match the trigger, the request is refused and no draft is created. Check the workflow log.
LinkedIn
  • Character limit: 3,000 characters for a post. The feed shows the first few lines and hides the rest behind a see more link.
  • Media per post: LinkedIn allows multi-image posts, documents, and video. SocialHandoff publishes 1 image per post.
  • Alt text: Supported on images through the API's alt text field. Not available for video or documents.
  • Threads: LinkedIn has no threads. If a draft has several parts, SocialHandoff joins them into one post.
A LinkedIn post scheduler that waits for your approval

Frequently asked questions

Can one release draft for X and LinkedIn together?
Yes. Add both networks to the release trigger. The draft is checked against each network's own limits, and on LinkedIn any thread is joined into one post.
Does the action work with a self-hosted server?
Yes, as long as GitHub's runners can reach it over HTTPS.

Let your agents post. Keep the final say.

Connect your first agent in minutes. Every draft waits in your inbox until you approve it.

Start free trial Self-host free

14 days free. No card required.

The hosted version is opening soon

Leave your email and we will send one message when hosted accounts open, with your 14-day trial ready. Want it today? Self-host it free from the repo.
Start free trial