Send Facebook Group Posts to Your CRM

With the Groups Watcher Pro plan, you can send every new post from your monitored Facebook groups and pages into your CRM (HubSpot, Salesforce, Pipedrive, and others). Use Zapier, Make.com, or n8n. Groups Watcher sends each post to your webhook URL, and you build a flow that creates or updates a contact, lead, or deal and attaches the post link and text. You map data.poster_name, data.body, data.post_url, data.group_name, and more to your CRM fields. Most alerts arrive in under 60 seconds.

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

Set up CRM

Use one of these to get a webhook URL, then add an action that sends data to your CRM:

• Zapier: Trigger = Webhooks by Zapier (Catch Hook). Action = HubSpot Create Contact / Create Deal, Salesforce Create Lead / Create Opportunity, Pipedrive Create Person / Create Deal, etc. For example map contact name = data.poster_name, note or description = data.body plus link data.post_url, source = data.group_name.
• Make.com: First module = Webhooks (Custom webhook). Second module = HubSpot / Salesforce / Pipedrive / etc. → Create a record (Contact, Lead, Deal). Map data.* to your CRM fields.
• n8n: First node = Webhook (POST). Next node = HubSpot, Salesforce, Pipedrive, or similar. Map body.data fields into the CRM (contact name, notes, link to post).

Copy the webhook URL from your chosen tool and paste it into Groups Watcher as your webhook URL (campaign or Pro plan setup). Each new post will trigger the flow and create or update a record in your CRM.

The information we send matches our custom webhook doc: one alert at a time with message and data (group name, poster, 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 webhook

Before or after connecting your CRM, you can send a test to your webhook URL (the one from Zapier, Make, or n8n) to confirm 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 flow and see the data in your automation.

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 (map to CRM fields)

For the default format, the body has a short message and a data object with all post fields. In Zapier, Make, or n8n map data.poster_name, data.poster_url, data.post_url, data.body, data.group_name, and so on to your CRM contact, lead, or deal fields and notes.

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>"
}

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 your automation receives for each new post. Map these fields to your CRM (e.g. contact name = poster_name, note = body + post_url, source = group_name).

{
  "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