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 per request with message and data (group name, poster, post URL, body, images, videos, and more).

Test your webhook

Before or after connecting your CRM, send a test to your webhook URL (from Zapier, Make, or n8n). Open Send test webhook, enter the URL, and we send a sample POST so you can verify the flow.

Request

• Method: POST
• Headers: Content-Type: application/json
• Body: JSON with message and a data object (one post per request). 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.

Each POST includes a short message and a data object with all post fields. See the full write-up on Custom webhook.

Payload shape

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

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

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