GitHub Action (signed release webhook) · Facebook

Announce GitHub releases on your Facebook Page after review

If your customers follow a Facebook Page, release notes should reach them there too, in their language. socialhandoff-announce-action sends each published release to SocialHandoff, which drafts a Facebook Page post with a citation back to the release. Facebook accepts text and links, so the draft can go out as-is, or a reviewer can add a screenshot in the inbox and simplify the wording before approving.

Prompt

Release rule: on release published, draft for Facebook, approval required. Reviewer rewrites developer terms into customer language and adds a screenshot if the release has a visible change.

How to do it

  1. Add a release rule In https://app.socialhandoff.com, sign in with Facebook and pick the Pages to connect; each Page becomes its own channel. Then add a GitHub trigger in Connections with a release rule that targets Facebook, and copy the trigger id and signing secret.
  2. Store the secret and add the action Add ANNOUNCE_WEBHOOK_SECRET as an Actions secret, copy the socialhandoff-announce-action folder from https://github.com/socialhandoff/socialhandoff into the repository, and reference it from a workflow on release published.
  3. Publish a release The action signs the payload and sends tag, name, notes, and URL. A Facebook draft appears in the inbox with a citation back to the release.
  4. Add media Release drafts arrive as text. Attach photos (up to 10, each with alt text) or one video in the inbox, or import a public release asset URL with POST https://app.socialhandoff.com/v1/media/import using an agent key and attach it before you approve, or leave it as a text post.
  5. Approve for the right Page The card shows which Page the post goes to. Approve on desktop or in the phone swipe stack, and it publishes to that Page at the scheduled time.

Example draft

Version 3.2 is out.

You can now export any report as a PDF, and dashboards load noticeably faster on large accounts. We also fixed the bug that sometimes logged people out on mobile.

Update from your app store, or read the full notes: https://example.com/releases/3.2

Gotchas

  • Facebook Page tokens do not expire, but removing the app's access in Facebook disconnects the Page. Reconnect it in Connections.
  • The action sends the release, not a finished post. Which networks it targets lives on the release rule in Connections, not in the workflow file.
  • Only Facebook Pages can be connected, not personal profiles. Every Page you grant at sign-in becomes its own channel, so check which Page the card names before approving.
Facebook
  • Where you can post: Facebook Pages only. The API does not allow posting to personal profiles or to Groups through SocialHandoff.
  • Page access: You need a role on the Page that allows creating content.
  • Photos: One photo with alt text, or up to 10 photos in one post.
  • Video: One video per post.
Facebook post scheduler for Pages, with approval built in

Frequently asked questions

Do Facebook Page posts need an image?
No. A Page post can be text and a link, one or more photos (up to 10), or one video.
Does the action need an agent key?
No. It uses the trigger id and a signing secret, verified with HMAC-SHA256. The draft cites the release in the audit log.
Can I post to a personal Facebook profile?
No. Meta only allows API publishing to Pages. Personal profiles cannot be connected.

Let your agents post. Keep the final say.

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

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