Send Facebook Group Posts to Make.com

With the Groups Watcher Pro plan, you can send every new post from your monitored Facebook groups and pages to Make.com. Use the Webhooks module to get a custom webhook URL, add it in Groups Watcher, and we deliver post details you can automate to Google Sheets, Slack, Airtable, CRM, or 1,500+ apps. Most alerts arrive in under 60 seconds.

This feature is available on the Pro plan. Check pricing here.

Set up Make.com

1. In Make.com, create a new scenario. Add the Webhooks module as the first (trigger) module.
2. Choose Custom webhook. Make will generate a unique URL for your scenario.
3. Copy that URL and paste it into Groups Watcher as your webhook URL (in your campaign or Pro plan setup).
4. When you are ready to test, trigger a post from Groups Watcher (or use the test tool below); Make will receive the data and you can map the output in subsequent modules.

The information we send matches our custom webhook doc: one alert at a time with message and data (group name, post URL, body, images, videos, and more). If your webhook is set to receive all posts, we send a batched body with a posts array. See Batched payload (all posts).

Test your Make.com webhook

Before or after configuring your scenario, you can send a test to your Make webhook URL to make sure it receives data. Open Send test webhook and choose default (keywords / AI validation) or all posts so the sample matches your campaign. Enter the URL and we send the matching sample so you can verify the scenario runs.

Request

• Method: POST
• Headers: Content-Type: application/json
• Body: Structured data with either message + data (one post), or message + posts + a top level timestamp when your Groups Watcher webhook is set to receive all posts (see Batched payload). Full reference: Custom webhook.

Payload (Make.com webhook data)

For the default format, the body has a short message and a data object with all post fields. In Make map data.group_name, data.post_url, data.body, and so on in your modules.

Depending on your campaign, Groups Watcher sends one of two layouts of structured data. Default means one post per request with message and data (posts that pass keywords or AI validation). All posts means a batched body with message, a posts array, and a top level timestamp. See Single post and Batched payload below, or the full write-up on Custom webhook.

Single post per request (default)

Each POST has a short message and a data object with all post fields.

{
  "message": "<string>",
  "data": {
    "group_name": "<string>",
    "group_id": "<string>",
    "poster_name": "<string>",
    "poster_url": "<string>",
    "post_url": "<string>",
    "group_url": "<string>",
    "post_id": "<string>",
    "post_type": "regular_post" | "marketplace",
    "body": "<string>",
    "images": ["<url>", ...],
    "videos": ["<url>", ...],
    "timestamp": "<ISO 8601 string>"
  }
}

Batched payload (all posts)

When your custom webhook is set to receive all posts, we send one POST per batch. The message summarizes the count (for example 1 new post in your groups or 3 new posts in your groups). Each element of posts uses the same field names as data above, as a flat object inside the array. The top level timestamp is when we sent the webhook.

{
  "message": "2 new posts in your groups",
  "posts": [
    {
      "group_name": "<string>",
      "group_id": "<string>",
      "group_url": "<string>",
      "poster_name": "<string>",
      "poster_url": "<string>",
      "post_url": "<string>",
      "post_id": "<string>",
      "post_type": "regular_post" | "marketplace",
      "body": "<string>",
      "images": ["<url>", ...],
      "videos": ["<url>", ...],
      "timestamp": "<ISO 8601 string>"
    },
    {
      "group_name": "<string>",
      "group_id": "<string>",
      "group_url": "<string>",
      "poster_name": "<string>",
      "poster_url": "<string>",
      "post_url": "<string>",
      "post_id": "<string>",
      "post_type": "regular_post" | "marketplace",
      "body": "<string>",
      "images": ["<url>", ...],
      "videos": ["<url>", ...],
      "timestamp": "<ISO 8601 string>"
    }
  ],
  "timestamp": "<ISO 8601 string>"
}

For batched payloads, use an Iterator (or split the posts array) so each post runs through the rest of your scenario.

Slack, Discord, ntfy, and Teams use different formats. The examples above apply when your automation receives a webhook URL from Groups Watcher (including via Zapier, Make, or n8n).

The field reference table below describes data.* for the default format. For batched all posts, each element of posts uses the same keys as data (flat objects in the array).

Field reference

Example payload

This is what Make.com receives for each new post. Use these fields in your scenario (e.g. add row to Google Sheets, send Slack message, create Airtable record).

{
  "message": "New post in Tampa Bay Homeowners",
  "data": {
    "group_name": "Tampa Bay Homeowners",
    "group_id": "123456789",
    "poster_name": "Maria Johnson",
    "poster_url": "https://facebook.com/maria.johnson",
    "post_url": "https://www.facebook.com/groups/123456789/permalink/987654321012345/",
    "group_url": "https://www.facebook.com/groups/123456789",
    "post_id": "987654321012345",
    "post_type": "regular_post",
    "body": "Anyone have a good HVAC person in St. Pete? Our AC went out last night",
    "images": ["https://scontent.xx.fbcdn.net/v/.../image1.jpg", "https://.../image2.jpg"],
    "videos": [],
    "timestamp": "2026-02-11T14:30:00.000Z"
  }
}

Frequently asked questions