Facebook group webhook: payload, signing and retries

HuddleWatch team

Nov 16, 2026 5 min read

Reference for the HuddleWatch webhook that sends new Facebook group posts to your endpoint: every field in the JSON, how to verify the signature, how retries work and how to get every post unfiltered.

Short answer

HuddleWatch POSTs each new Facebook group post to your URL as JSON with id, group, author, body, permalink, posted_at, score, confidence and reason. Add a signing secret and every request carries X-HuddleWatch-Signature: sha256= plus the HMAC-SHA256 of the raw body. Failed deliveries are retried up to 8 times with the same id, so dedupe on id.

Facebook group webhook: payload, signing and retries

Meta closed the Facebook Groups API on April 22, 2024, so there is no official way left to receive group posts in your own system. The HuddleWatch webhook fills that gap for reading: our accounts watch the public and private groups you choose, and each new post is sent to your endpoint. It is on every plan. For the background, see the Facebook Groups API alternative.

Set it up

  • Open Settings → Delivery → Webhook.
  • Paste your Endpoint URL. It must accept a JSON POST and answer with a 2xx status.
  • Optionally add a Signing secret so you can verify requests.
  • Set Minimum score. 0 sends every scored lead; 70 sends only strong buying intent.
  • For a raw feed of every post, unscored and including ads, email support@huddle.watch and ask for every-post mode.

The payload

FieldTypeWhat it is
idstringThe alert's id. Stays the same across retries, so use it to dedupe
groupstringName of the Facebook group
authorstringPoster's name. Empty string when Facebook does not show one
bodystringFull post text
permalinkstring | nullLink to the post
posted_atstring | nullISO 8601 time the post was published
scorenumberBuying intent from 0 to 100. Always 100 in every-post mode
confidencenumberThe same score from 0 to 1
reasonstringWhy the post was sent. In every-post mode: "every post is sent on this account"
Content-Type is application/json. The author's profile link is not included today.

Verify the signature

  • Read the raw request body as bytes, before any JSON parsing.
  • Compute HMAC-SHA256 of those bytes with your signing secret as the key, and hex-encode it.
  • Compare sha256= plus that hex string with the X-HuddleWatch-Signature header, using a constant-time comparison.
  • Reject the request if they differ. Without a secret set, no signature header is sent.

Delivery and retries

BehaviourDetail
SuccessAny 2xx response
RetriesUp to 8 attempts, waiting 1, 2, 4, 8… minutes between them
DuplicatesPossible after a timeout. The id is identical, so drop repeats
OrderNot guaranteed. Sort on posted_at if order matters
DelayMedian about 6 minutes from post to delivery in public groups, about 12 in private groups

Comments

The webhook sends new top-level posts. On the Comments plan, new comments and replies from public groups arrive at the same endpoint with type set to comment; see Facebook group comments to a webhook.

No-code tools work too: Zapier or Make and n8n.

Frequently asked questions

Is there a Facebook group webhook from Meta?

No. Meta's webhooks cover Pages, not groups, and the Groups API that apps used to read group posts was deprecated on April 22, 2024.

Can I get every post in a group, not just leads?

Yes. Ask support to switch your account to every-post mode. Every new post is then sent unscored, ads and off-topic posts included.

Which plan includes the webhook?

All of them. Pro is $50/month for 10 groups and Master is $150/month for 50 groups.

Does it work with private groups?

Yes. One of our accounts joins the group once an admin approves it, and posts are sent the same way as from public groups.

Want these posts found for you?

HuddleWatch scores every new post in your groups and sends the high scorers to your feed, Slack, or email.

Start free with 3 groups

See how Facebook group monitoring works, or compare the tools.