Send Facebook Group Posts to GoHighLevel (Inbound Webhook)

With the Groups Watcher Pro plan, you can send new Facebook group and page posts into GoHighLevel by using a custom webhook. In GoHighLevel, create a workflow with an Inbound Webhook trigger (method POST), copy the trigger URL, and paste it into Groups Watcher. Most alerts arrive in under 60 seconds.

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

Set up GoHighLevel inbound webhook

1. In GoHighLevel, open Automation > Workflows and create a workflow.
2. Add trigger: Inbound Webhook and choose POST.
3. Copy the webhook URL generated by GoHighLevel.
4. In Groups Watcher Dashboard, choose Custom webhook and paste that URL. If you do not have dashboard access yet, you can test your webhook by clicking Send test webhook below.
5. Send a test webhook so GoHighLevel captures the payload and exposes mapping references.
6. Add actions like Create/Update Contact, Add Note, or pipeline updates, then map incoming fields from the webhook trigger.
7. Save and publish the workflow.

Test your GoHighLevel webhook

Use the button below to send a sample payload to your GoHighLevel inbound webhook URL, then confirm the request appears in GoHighLevel references for mapping.

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 (for GoHighLevel mapping)

In the default format, GoHighLevel receives message and data. Use data.poster_name, data.post_url, data.body, data.group_name, and related fields in your contact and follow-up actions.

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).

Frequently asked questions