# Facebook Groups Scraper - Posts, Comments & Replies \[No Login]✅ (`unseenuser/fb-groups`) Actor Scrape public Facebook group posts with full comment threads and replies - no login, no cookies, never member data. The only Groups scraper that returns complete comment threads. Export JSON, CSV, or Excel. - **URL**: https://apify.com/unseenuser/fb-groups.md - **Developed by:** [Unseen User](https://apify.com/unseenuser) (community) - **Categories:** Social media, Automation, Developer tools - **Features:** Limited permissions - **Stats:** 59 total users, 6 monthly users, 100.0% runs succeeded, 4 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing from $3.00 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Facebook Groups Scraper (No Login) > **Public group posts only. We never scrape members or private data.** No login, no cookies, fast bulk public group posts. Extract post text, author, reactions, comment counts, top comments and timestamps from any public Facebook group, by URL. Optional add-ons pull full comment threads and replies per post. Use it as a **Facebook Groups API** alternative for the post and engagement data Meta's official Graph API no longer exposes - for social listening, brand monitoring, lead generation, and community research. ### Table of contents - [What this Actor does NOT do](#what-this-actor-does-not-do) - [Disambiguation](#disambiguation-which-facebook-actor-do-you-need) - [Paid plan required](#paid-plan-required) - [Pricing](#pricing) - [Use cases](#use-cases) - [Quick start](#quick-start) - [Example tasks](#example-tasks) - [Inputs](#inputs) - [Output](#output) - [Output views](#output-views) - [Sample outputs](#sample-outputs) - [Run statuses you may see](#run-statuses-you-may-see) - [Performance and limits](#performance-and-limits) - [Reliability](#reliability) - [Integration examples](#integration-examples) - [Scheduling](#scheduling) - [Troubleshooting](#troubleshooting) - [FAQ](#faq) - [Related scrapers](#related-scrapers) - [Terms of Service](#terms-of-service) - [Support and contact](#support-and-contact) *** ### What this Actor does NOT do Four hard boundaries. Each one is a deliberate product decision, not a missing feature: 1. **No member harvesting.** We never return member lists, member contact details, or anything that could be used to build a roster of who is in a group. Post and comment content only. 2. **No group search.** This Actor works on known group URLs (or IDs) you provide. It cannot discover groups by keyword. 3. **No group details / metadata.** Member counts, admin lists, rules, descriptions and join settings are out of scope. Posts only. 4. **No private groups, ever.** Public groups only. No cookies, no session tokens, no authentication of any kind. If you need member rosters, group discovery, group metadata, or private-group access, this is not the Actor for you, and no Actor in the UnseenUser portfolio provides those. *** ### Disambiguation: which Facebook Actor do you need? > Groups: which Actor do you need? > > - Scraping groups specifically, group-first workflow? -> **Facebook Groups Scraper** (you are here) > - Mixing pages, profiles AND groups in one run? -> [Facebook Page Posts & Reels Scraper](https://apify.com/unseenuser/fb-posts) (group mode) > - Just comments on a known post? -> [Facebook Comment Scraper - Posts & Reels](https://apify.com/unseenuser/fb-comments) > > Same group/posts backend, listings split by search intent so you land on the right one. *** ### Paid plan required This Actor requires a **paid Apify plan**. A run started on the free plan exits immediately without scraping: it finishes successfully (status `SUCCEEDED`, so it doesn't look like an error), writes a single row to the dataset explaining the situation, and sets a status message. No upstream calls are made and you are not charged for scraping. To use the Actor, upgrade to any paid Apify plan: https://apify.com/pricing *** ### Pricing **Pay per result**, with automatic discounts on higher Apify subscription plans. **Platform usage (compute, memory, storage) is included** - no separate Apify platform charges. | Your Apify plan | Price per 1,000 results | |---|---| | Free | $4.00 | | Starter | $3.70 | | Scale | $3.50 | | Business | $3.00 | A result is a single dataset row, and results are **threaded**: the post, each comment, and each reply are **separate rows**, so results = posts + comments + replies. Turn comments/replies off (`fetchAllComments` / `fetchCommentReplies`) to bill posts only. Example volumes (cost shown at the Starter $3.70/1,000 rate; varies by plan): | Scenario | Results (rows) | Cost (Starter) | |---|---|---| | 1,000 posts, comments & replies off | 1,000 | $3.70 | | 100 posts averaging 20 comments + 5 replies each | ~2,600 | ~$9.62 | | 10 posts, comments off, across 50 groups | 500 | $1.85 | **Deleted and private groups are never billed.** If a group is gone or private, the upstream reports it as not-found and charges nothing, so no row is produced for it. A group that is reachable but simply has no posts produces a **single `notice` row** (`mode: "empty"`) - one honest row that reflects the one upstream request the run actually made. **AI lead-intent (`llm` mode)** is billed separately on **your own Anthropic account** via your API key - it is not part of the per-result price above. *** ### Use cases - **Social listening** - monitor what a public community is discussing in real time. - **Community and trend research** - track topics, sentiment shifts and engagement curves in a group over time. - **Lead and demand signals** - spot intent in public group discussion (always with a lawful basis for any follow-up). - **Market research** - understand a niche community's vocabulary, pain points, and product references. - **Content research** - study which post formats (questions, polls, photos, long-form) resonate in a given group. - **Brand monitoring** - watch public mentions and sentiment around your brand in relevant groups. - **Competitive intelligence** - see how a competitor's product is being discussed in user-run communities. - **Editorial / journalism** - source primary public material for reporting on online community trends. - **Academic research** - quantitative analysis of public group discourse with a documented ethics framework. - **Facebook group monitoring** - schedule recurring runs to catch new posts and comment threads the moment they appear in tracked groups. - **Bulk multi-group scraping** - process a list of public Facebook group URLs in one run with a single API call. - **Group post archive and data export** - build a long-term Facebook group dataset for downstream analysis or CSV/Excel export. *** ### Quick start 1. Click **Try for free** on this Actor's page. 2. Paste one or more **public** Facebook group URLs into **Public Group URLs** (replace the placeholder). 3. (Optional) Adjust **Max posts per group**. 4. (Optional) Toggle **Include top comments** on if you want them (off by default). 5. (Optional) Turn off **Fetch full comment threads** and/or **Fetch comment replies** to reduce cost. Both are on by default and are billed add-ons. 6. Click **Start**. 7. Watch results stream into the **Overview** dataset view. 8. When the run finishes, export as JSON, CSV, XLSX, or pull via the Apify API. *** ### Demo video New to Apify? Schedule this Actor to run automatically: [![How to schedule your actors](https://img.youtube.com/vi/GRFW_Loo2dk/hqdefault.jpg)](https://www.youtube.com/watch?v=GRFW_Loo2dk) Connect this Actor to your stack with one of Apify's integrations: [![Apify integrations](https://img.youtube.com/vi/bNACk1_S_6w/hqdefault.jpg)](https://www.youtube.com/watch?v=bNACk1_S_6w) *** ### Example tasks Common use cases this Actor solves out of the box. Configure any of these by pasting your public group URL into the **Try it for free** section above and tweaking the input - every recipe below is a 1-2 setting change away. - **Facebook Groups API Alternative - Public Posts** - get the post and engagement data Meta's official Graph API does not expose. - **Bulk Scrape Posts From Multiple Facebook Groups** - paste a list of public group URLs, pull recent posts from each in one run. - **Facebook Group Monitoring - Track Brand Mentions** - schedule a daily scan of your category groups for fresh mentions. - **Find Top-Performing Posts in a Facebook Group** - sort by reactions and comments to see what content wins. - **Get Full Comment Threads From Facebook Group Posts** - pull every comment, not just the top three. - **Facebook Group Lead Generation - Find Intent Posts** - surface posts asking for recommendations or describing a problem you solve. - **Mine Customer Feedback From Facebook Group Posts** - complaints, feature requests, and how-do-I questions for product teams. - **Track Competitor Mentions Across Facebook Groups** - watch how a competitor is being discussed in your category. - **Pull a Deep Post History From One Facebook Group** - long pagination for trend analysis and year-over-year comparisons. - **Extract Comments and Replies From Facebook Group Posts** - the complete discussion tree per post. - **Preview Recent Posts From a Facebook Group** - the cheapest way to confirm a group is public before a larger run. *** ### Inputs | Input | Type | Required | Default | Description | |---|---|---|---|---| | `startUrls` | array of strings | yes | - | One or more public Facebook group URLs (or numeric IDs). Minimum 1 entry. | | `maxPosts` | integer | no | 0 | Stop after this many posts per group. `0` (the default) means fetch every available post. Pagination returns 3 posts at a time, so positive values are effectively rounded up to the next multiple of 3. | | `onlyPostsNewerThan` | string (date) | no | - | Optional. Skip posts older than this date. Accepts an ISO date (`2026-07-01`) or full date-time. Posts whose timestamp cannot be determined are always kept. | | `sortBy` | string | no | `RECENT_ACTIVITY` | Post ordering hint sent to Facebook: `RECENT_ACTIVITY` (posts with recent comments - **best for comment threads**), `TOP_POSTS` (high engagement), `CHRONOLOGICAL` (newest first), or `CHRONOLOGICAL_LISTINGS`. `RECENT_ACTIVITY`/`TOP_POSTS` surface older, more-commented posts; `CHRONOLOGICAL` returns freshly-posted (often comment-less) posts first in busy groups. Final order is Facebook's to decide. | | `verifyPublicBeforeScraping` | boolean | no | false | Check each group's About page first; if it isn't Public, report `status: private` with certainty and skip the posts scrape (not billed) instead of inferring privacy from a failed request. Adds one group-info request per group - reused (no extra call) when `includeGroupProfile` is also on. | | `includeGroupProfile` | boolean | no | false | Also return one profile row per group (member count, privacy, categories, rules, activity, description, created date). No member/personal data - admin and moderator lists are excluded. Adds one result row per group. | | `leadIntentDetection` | string | no | `off` | `off`, `heuristic`, or `llm`. Flags posts whose author is a potential customer (asking for a recommendation/service, wanting to buy, or hiring) by adding a `leadIntent` object to each post row. Posts advertising the author's own product/service are tagged `category: "selling"` but are **not** flagged as leads. `heuristic` = free keyword rules. `llm` = a Claude classifier for higher accuracy (needs an `ANTHROPIC_API_KEY` secret; billed by Anthropic; adds per-post cost/latency). | | `leadIntentScope` | string | no | `posts` | Which rows get a `leadIntent`: `posts` (default), `posts_and_comments`, or `all` (posts + comments + replies). Comments can hold real buyer intent, but most are noise. **Under `llm` mode each comment/reply is its own Anthropic call**, so wider scope can multiply cost/latency many times over (a 40-comment post = 40 extra classifications). Free `heuristic` mode makes wider scope cheap. | | `leadIntentLlmModel` | string | no | `claude-haiku-4-5` | Only used when `leadIntentDetection` is `llm`. Which Claude model classifies each post: `claude-haiku-4-5` (cheapest, recommended), `claude-sonnet-5` (balanced), or `claude-opus-5` (most accurate, most expensive). The `LEAD_INTENT_LLM_MODEL` env var overrides this with any model id. | | `anthropicApiKey` | string (secret) | no | - | Only used when `leadIntentDetection` is `llm`. Paste your own Anthropic API key in the input; it's stored **encrypted and masked** and billed on your own Anthropic account. Never written to the saved input snapshot or the output. Falls back to an `ANTHROPIC_API_KEY` env var if left empty. | | `includeTopComments` | boolean | no | false | Top comments are returned alongside each post at no extra cost. Off by default; enable to include them. | | `fetchAllComments` | boolean | no | true | **Billed add-on.** Paginate the full comment thread for every returned post. On by default; turn off to reduce cost. | | `fetchCommentReplies` | boolean | no | true | **Billed add-on.** Pull replies for every comment returned. On by default. Only effective when `fetchAllComments` is also true. | #### Group input key: URL works, ID works Either form is accepted in `startUrls`: - Full URL with numeric ID: `https://www.facebook.com/groups/1234567890` - Full URL with vanity name: `https://www.facebook.com/groups/your-group-vanity-name` - Numeric ID alone: `1234567890` Paste whichever you have. The Actor normalizes them. #### Where to find a real public group URL 1. Open https://facebook.com. 2. Search for any topic in the search bar. 3. Click **Groups** in the left sidebar of the search results. 4. Pick a group whose listing says **"Public"** under its name. 5. Click into it. Copy the URL from your browser's address bar. 6. Paste that URL into **Public Group URLs**. If a group is marked Private or requires you to be a member to see posts, the Actor does not fail or produce a billed row. It records the group's status (`private`) and a plain-language reason in the run summary and the run's status message, and moves on to the next URL. You are not charged for it. *** ### Output #### Threaded rows Results are emitted as a thread: the post, then each comment, then that comment's replies, **each on its own row**, in order: ``` post ├─ comment 1 │ ├─ reply 1a │ └─ reply 1b ├─ comment 2 │ └─ reply 2a └─ ... next post ... ``` Rows are marked by `type` (`post` / `comment` / `reply`); comment rows carry `post_id`, reply rows carry `post_id` + `comment_id`, so you can always re-link them. **Billing note:** every comment and reply is its own billed result, so a post with 37 comments produces ~38+ rows. **Uniform columns:** every row - post, comment, and reply - carries the same top-level columns, so the dataset reads as one clean thread in a table and in CSV/Excel (no scattered per-type columns). The full original object is kept alongside them under its own key (`post` / `comment` / `reply`). | Field | Type | Present on | Description | |---|---|---|---| | `type` | string | every row | `post`, `comment`, `reply`, or `group_profile`. | | `id` | string | every row | ID of this row's item. | | `text` | string | null | every row | Text/message of the item. | | `author` | string | null | every row | Author name of the item. | | `reactions` | number | null | every row | Reaction count, when upstream provides one. | | `url` | string | null | every row | Item URL. Posts: the permalink. Comments/replies: a constructed Facebook deep link (`…/permalink//?comment_id=…[&reply_comment_id=…]`). | | `publishTime` | number | null | every row | Unix **seconds**. Normalised from the post's `publishTime` or a comment/reply's `created_at`. | | `post_id` | string | post/comment/reply rows | ID of the post the row belongs to - **group/sort by this to cluster a whole thread.** | | `comment_id` | string | null | reply rows | ID of the parent comment. | | `post` | object | post rows | The full post object as returned upstream. See per-field table below. | | `comment` | object | comment rows (`fetchAllComments`) | The full comment object as returned upstream. | | `reply` | object | reply rows (`fetchCommentReplies`) | The full reply object as returned upstream. | | `groupProfile` | object | group-profile rows (`includeGroupProfile`) | The group's public About-page data. See below. | | `leadIntent` | object | post rows when `leadIntentDetection` is on (also comment/reply rows per `leadIntentScope`) | `{ isLead, category, confidence, method }` - flags authors signalling buyer intent. See below. | | `commentsError` | string | post rows, when comment fetch failed | Error message; the post row is still emitted. | | `error` | string | legacy - not emitted | Retained for backward compatibility. Groups that return no posts are reported in the run summary, not as dataset rows. | | `_metadata` | object | every row | `{ fetched_at, group_url, page, status, type, post_id?, post_url?, comment_id? }`. | #### `post` sub-fields (typical shape) | Field | Type | Notes | |---|---|---| | `id` | string | Numeric post ID. | | `text` | string | Post body. May be empty for photo-only or video-only posts. | | `url` | string | Canonical post URL. | | `permalink` | string | Permalink URL. | | `groupUrl` | string | URL of the group the post was made in. | | `author.id` | string | Author's numeric ID. | | `author.name` | string | Author's display name. | | `author.short_name` | string | Author's short/first name, when provided. | | `reactionCount` | number | Total reactions on the post. | | `commentCount` | number | Total comments on the post. | | `videoViewCount` | number | null | View count for video posts; `null` for non-video posts. | | `publishTime` | number | Unix epoch **seconds** (not milliseconds). | | `videoDetails` | object | `{ sdUrl, hdUrl, thumbnailUrl }` for video posts. | | `topComments` | array | Off by default; toggle on via `includeTopComments`. Each comment carries `id`, `text`, `publishTime`, and `author` (`id`, `name`, and, when public, `url`). | Sub-fields are not strictly typed in the dataset schema, because the upstream may add or remove fields over time. The Actor passes whatever it receives, plus the `_metadata` envelope. #### `_metadata` sub-fields | Field | Type | Description | |---|---|---| | `fetched_at` | string (ISO 8601) | When the Actor pushed this row. | | `group_url` | string | The group URL that produced this row. | | `page` | integer | 1-indexed pagination page within that group. | | `status` | string | `public_ok` on post rows. | | `type` | string | `post` for a post row, `group_profile` for a group About-page row. | #### Group-profile rows (`includeGroupProfile`) When `includeGroupProfile` is enabled, the Actor emits one extra row per group under a `groupProfile` object (with `_metadata.type = "group_profile"`). It carries the group's **public** About-page data and **no member or personal data** - administrator and moderator lists are deliberately excluded to honor this Actor's never-member-data boundary. | Field | Type | Notes | |---|---|---| | `id`, `url`, `name`, `description` | string | Group identity. | | `privacy`, `visibility` | object | `{ label, description }`, e.g. `label: "Public"`. | | `categories` | array | Group categories (`{ id, name }`). | | `member_count`, `member_count_text` | number / string | Total members (aggregate). | | `administrator_count`, `moderator_count` | number | Aggregate counts only - the lists themselves are not returned. | | `activity` | object | `{ posts_last_day, posts_last_month, new_members_text }`. | | `rules` | array | Group rules (`{ id, title, description }`). | | `created_at`, `history_summary` | string | When the group was created and a short history. | ```json { "groupProfile": { "id": "366190054572553", "name": "Python Programming", "privacy": { "label": "Public" }, "member_count": 710386, "administrator_count": 3, "activity": { "posts_last_day": 16, "posts_last_month": 512 }, "categories": [ { "name": "Software & tech" } ] }, "_metadata": { "fetched_at": "...", "group_url": "...", "page": 0, "status": "public_ok", "type": "group_profile" } } ``` #### Lead-intent detection (`leadIntentDetection`) Set `leadIntentDetection` to `heuristic` or `llm` to flag posts whose author is a potential **customer** - the highest-value signal in group data. Each post row gains a `leadIntent` object: | Field | Type | Notes | |---|---|---| | `isLead` | boolean | True only when `category` is a buyer-side category (`service_request`, `recommendation_request`, `buying_intent`, `hiring`). **Derived from `category`**, so it can never contradict it. | | `category` | string | `service_request`, `recommendation_request`, `buying_intent`, `hiring`, `selling`, or `none`. `selling` = the author advertising their **own** offering (a vendor, not a lead). `none` = no commercial intent. | | `confidence` | number | 0-1 score. | | `method` | string | `heuristic` or `llm`. | | `matched` | array | (heuristic only) which signal categories matched. | ```json { "post": { "text": "Can anyone recommend a good plumber in Austin?" }, "leadIntent": { "isLead": true, "category": "recommendation_request", "confidence": 0.9, "method": "heuristic" } } ``` - **`heuristic`** - keyword/pattern rules. Free, fast, runs inline. Good default. - **`llm`** - a Claude model classifies each post's text for higher accuracy. **This mode transmits each processed post's text to Anthropic's API** for classification, so before enabling it note the data-flow and compliance point below. It **requires an Anthropic API key**, which you can provide two ways: paste it into the **`anthropicApiKey`** input field (stored encrypted and masked, never persisted to the run's input snapshot or output), or set an `ANTHROPIC_API_KEY` environment variable. The key is billed on your own Anthropic account and adds latency and cost **per post**. Pick the model with **`leadIntentLlmModel`**: | Model | Best for | |---|---| | `claude-haiku-4-5` *(default)* | High-volume runs - cheapest and fastest. | | `claude-sonnet-5` | Balanced accuracy vs. cost. | | `claude-opus-5` | Highest accuracy; far more expensive per post. | Model resolution precedence: the `LEAD_INTENT_LLM_MODEL` env var (any model id) > the `leadIntentLlmModel` input > the `claude-haiku-4-5` default. Each `leadIntent` result records which `model` produced it. If `llm` is selected without a key, the Actor falls back to `heuristic`. > **⚠️ Data flow & compliance (`llm` mode only).** Enabling `llm` transmits each processed post's text to Anthropic's API under your own key and account. In that transfer **you are the data controller** and Anthropic is your processor - UnseenUser is not a party to it and never receives the data. You are responsible for having a lawful basis to send post content (which can include special-category data or content authored by minors) to Anthropic, for complying with Anthropic's terms and data-retention policies, and for your downstream use of the lead signals. Classifying text is inference, not model training. See the Terms of Service, Actor-Specific Addendum, Clause M. The `heuristic` mode has none of this - it runs locally and sends nothing. #### Groups that return no posts Deleted/not-found (`not_found`), private, rate-limited, and errored groups do **not** produce a dataset row and are **not charged** (the upstream charges nothing for them). A group that is reachable but simply has no posts produces one honest `notice` row (`mode: "empty"`), matching the single upstream request it cost. Either way, each group's outcome is recorded in the run summary (saved to the key-value store) and summarized in the run's status message, with a `status` (`private`, `not_found`, `empty`, `rate_limited`, or `error`) and a plain-language `reason`: ```json { "groups": [ { "url": "https://www.facebook.com/groups/private-example", "status": "private", "postsPushed": 0, "reason": "The group is private, restricted, or requires login. This Actor supports public groups only." } ] } ``` One bad or private URL never crashes the run - the Actor records its status and moves on to the next URL. *** ### Output views The Apify Console renders results in four tabs, three of which are pre-defined by this Actor's output schema: | View | Purpose | |---|---| | **Overview** | One row per post with post ID, text, author, reactions, comment count, timestamp and links. The default view. | | **Engagement** | Posts ranked by reactions and comment counts. Useful for surfacing high-signal posts fast. | | **Leads** | Lead-intent columns (`isLead`, `category`, `confidence`) surfaced next to the post text and author. Sort by **Is lead** to bring commercial-intent posts to the top. Populated only when `leadIntentDetection` is enabled. | | **Errors** | Legacy view, now always empty - private, empty, and failed groups are reported in the run summary and status message (and are never charged), not as dataset rows. | | **All fields** | Apify's built-in catch-all view. Shows every field on every row, including nested objects. | Field-coverage badges in the column headers (e.g. "100%") show the percentage of dataset rows that have a value for that column. They are descriptive, not failure indicators. *** ### Sample outputs #### Basic post row (no add-ons) ```json { "post": { "id": "1204545088344463", "text": "Anyone else having issues with their delivery this week? Mine has been delayed twice.", "url": "https://www.facebook.com/groups/example/posts/1204545088344463", "permalink": "https://www.facebook.com/groups/example/posts/1204545088344463", "groupUrl": "https://www.facebook.com/groups/example", "author": { "id": "100063669491743", "name": "Sample Author" }, "reactionCount": 133, "commentCount": 12, "publishTime": 1734553170, "videoDetails": { "sdUrl": null, "hdUrl": null, "thumbnailUrl": null }, "topComments": [ { "id": "987654321", "text": "Same here, third delay this month.", "publishTime": 1734569761, "author": { "id": "100063669491800", "name": "Sample Commenter" } } ] }, "_metadata": { "fetched_at": "2026-06-03T12:00:00.000Z", "group_url": "https://www.facebook.com/groups/example", "page": 1 } } ``` #### Post row with full comment thread (`fetchAllComments: true`) ```json { "post": { "id": "1204545088344463", "text": "...", "author": { "name": "Sample Author" } }, "comments": [ { "id": "987654321", "text": "Same here, third delay this month.", "publishTime": 1734569761, "author": { "id": "100063669491800", "name": "Sample Commenter" } }, { "id": "987654322", "text": "Mine arrived early actually!", "publishTime": 1734571200, "author": { "id": "100063669491801", "name": "Another Commenter" } } ], "_metadata": { "fetched_at": "2026-06-03T12:00:00.000Z", "group_url": "https://www.facebook.com/groups/example", "page": 1 } } ``` #### Post row with comments AND replies (`fetchAllComments: true`, `fetchCommentReplies: true`) ```json { "post": { "id": "1204545088344463", "text": "...", "author": { "name": "Sample Author" } }, "comments": [ { "id": "987654321", "text": "Same here, third delay this month.", "author": { "name": "Sample Commenter" } } ], "replies": { "987654321": [ { "id": "111", "text": "Try contacting support, they refunded mine.", "publishTime": 1734580000, "author": { "id": "100063669492000", "name": "Helper" } } ] }, "_metadata": { "fetched_at": "2026-06-03T12:00:00.000Z", "group_url": "https://www.facebook.com/groups/example", "page": 1 } } ``` #### Run summary (groups that returned no posts) Deleted/private/rate-limited/failed groups are **not** written to the dataset and are **not charged**; a reachable-but-empty group instead produces one `notice` row (`mode: "empty"`). Group outcomes also appear in the run summary (key-value store) and the run's status message: ```json { "pushedCount": 42, "groups": [ { "url": "https://www.facebook.com/groups/example", "status": "public_ok", "postsPushed": 42 }, { "url": "https://www.facebook.com/groups/private-example", "status": "private", "postsPushed": 0, "reason": "The group is private, restricted, or requires login. This Actor supports public groups only." } ] } ``` *** ### Run statuses you may see | Status | Meaning | What to do | |---|---|---| | `SUCCEEDED` (green) | Run completed without unrecoverable errors. Deleted/private/failed groups (if any) are reported in the run summary and status message, not billed; a reachable-but-empty group yields one `notice` row. | Open the **Overview** view for real posts; read the status message or run summary for any per-URL issues. | | `SUCCEEDED` (green) with a status message about a paid plan | The run was started on the free Apify plan; it exited immediately without scraping and wrote one `notice` row (`mode: "blocked"`). | Upgrade to any paid Apify plan: https://apify.com/pricing | | `FAILED` (red) | Unrecoverable error (e.g. malformed input, missing required configuration). | Check the run **Log** tab for the exact error; fix input or configuration and re-run. | | `ABORTED` | You stopped the run manually, or it ran out of memory/time. | Reduce `maxPosts` or split the URL list across multiple runs. | | `TIMED-OUT` | Run exceeded its timeout setting. | Increase the run timeout in **Actor settings**, or split the URL list. | *** ### Performance and limits - **Pagination granularity.** The underlying source returns 3 posts per pagination page. `maxPosts` is honored but effectively rounds up to the next multiple of 3. - **Concurrency.** A single group is paginated sequentially. Multiple groups in the same run are processed one after another to keep memory low and behavior predictable. - **Memory.** Default 256 MB is enough for most runs. Increase to 1024 MB if you are pulling very large comment threads. - **Run time.** A typical 30-post run for a single group completes in 5 to 30 seconds depending on upstream latency. Larger runs scale roughly linearly. - **Comment add-ons.** Each post with `fetchAllComments` enabled triggers one or more comment-page requests; `fetchCommentReplies` adds one or more requests per comment. Both are on by default; turn them off if you only need posts and want to minimize cost. - **Output streaming.** Rows are streamed to the dataset as they are produced. You can start downloading partial results before the run finishes. *** ### Reliability - **Retries.** 3 attempts with exponential backoff (1s, 2s, 4s) on transient HTTP errors (`429`, `502`, `503`, `504`). - **Per-group error isolation.** A failure on one group does not crash the run; its `status` and `reason` are recorded in the run summary and the next group is processed. - **Per-row `_metadata`.** Every row carries `{ fetched_at, group_url, page, status }` so you can correlate output back to inputs. - **Deleted/private groups are free.** A group the upstream reports as not-found, deleted, or private is charged 0 by the upstream and produces no billed row; its outcome is reported in the run summary and status message. A reachable-but-empty group produces one honest `notice` row matching the single request it cost. - **Optional public-group preflight.** With `verifyPublicBeforeScraping`, the Actor confirms a group is Public from its About page before scraping, so private groups are flagged `private` with certainty rather than inferred from a failed request. - **Resilient AI calls.** In `llm` lead-intent mode, Anthropic requests retry transient failures (429, 5xx, overloaded, network) with exponential backoff, and any post that still fails falls back to the heuristic classifier. - **Sanitized error messages.** Upstream error bodies are parsed and only the human message is surfaced; internal fields are never leaked into your dataset or logs. - **Stable output schema.** The Actor never blocks a push because of upstream sub-field variation; whatever the upstream returns inside `post` is passed through. *** ### Integration examples #### Run the Actor via Apify API (HTTP) ```bash curl -X POST "https://api.apify.com/v2/acts/unseenuser~fb-groups/runs?token=YOUR_APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "startUrls": ["https://www.facebook.com/groups/your-public-group"], "maxPosts": 30, "includeTopComments": true, "fetchAllComments": false, "fetchCommentReplies": false }' ``` #### Run synchronously and get the dataset items in one call ```bash curl -X POST "https://api.apify.com/v2/acts/unseenuser~fb-groups/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "startUrls": ["https://www.facebook.com/groups/your-public-group"], "maxPosts": 30 }' ``` #### Node.js (Apify client) ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('unseenuser/fb-groups').call({ startUrls: ['https://www.facebook.com/groups/your-public-group'], maxPosts: 30, includeTopComments: true, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(`Got ${items.length} rows`); ``` #### Python (Apify client) ```python from apify_client import ApifyClient import os client = ApifyClient(os.environ["APIFY_TOKEN"]) run = client.actor("unseenuser/fb-groups").call(run_input={ "startUrls": ["https://www.facebook.com/groups/your-public-group"], "maxPosts": 30, "includeTopComments": True, }) items = list(client.dataset(run["defaultDatasetId"]).iterate_items()) print(f"Got {len(items)} rows") ``` #### Webhook on run completion Configure a webhook in **Actor settings -> Integrations -> Webhooks** to receive a POST when each run finishes. Apify sends the run ID, status, and dataset ID; fetch the dataset items with `GET /v2/datasets/{id}/items`. *** ### Scheduling Use the Apify Console scheduler to run this Actor on a cadence: 1. Open the Actor page. 2. Click **Actions -> Schedule**. 3. Set cron (e.g. `0 */6 * * *` for every six hours). 4. Save your input as the schedule's task input. For daily change-detection on a small set of groups, hourly or six-hourly schedules with `maxPosts: 30` strike a good balance. *** ### Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | Dataset has 0 rows total, run SUCCEEDED, status message says groups returned no posts | Group is empty, private, restricted, or the upstream response shape is unrecognized. You were not charged. | Read the run summary / status message for each group's `status` and `reason`. Try a different known-public group URL. If multiple real groups all return `empty`, share the run summary with support so the extractor can be extended. | | Status message reports a group as `error` (e.g. "Group ID not found") | The URL or numeric ID does not resolve to a real group. | Open the URL in a browser. If it 404s for you too, you have the wrong URL. | | Run finished SUCCEEDED with a status message about a paid plan, dataset has one `notice` row | You are on the Apify free plan; this Actor requires a paid plan and exits immediately. | Upgrade to any paid Apify plan: https://apify.com/pricing | | Comments fetched but replies empty | `fetchCommentReplies` was true but `fetchAllComments` was false, so there were no comments to iterate. | Enable `fetchAllComments` as well. | | A group I expected is missing from the dataset | It was deleted, private, or failed (upstream charged $0) so no row was produced. A reachable-but-empty group instead appears as one `notice` row. | Check that group's `status` and `reason` in the run summary or status message. | *** ### FAQ **Q: Do you scrape group members?** A: No, never. This Actor pulls public post content only. It does not return member lists, member emails or phones, or any member data - by design and by policy. **Q: Can it find groups by keyword?** A: No. This Actor works on known group URLs or IDs you provide. **Q: Does it return group details like member count, admins, rules?** A: No. Posts only. **Q: Does it work on private groups?** A: No, by design. This Actor is public-only and never uses cookies or authentication. **Q: How many posts can I get per run?** A: As many as you want (a paid Apify plan is required to run the Actor). Pagination is automatic. Each underlying page returns 3 posts, so `maxPosts` is effectively rounded up to the next multiple of 3. **Q: How are the comment add-ons billed?** A: They are separate, opt-in billed events. Leave both off if you only need post text, author and engagement counts. **Q: How fresh is the data?** A: Posts are fetched at the moment of the run. Each row has `_metadata.fetched_at` so you can reason about staleness in downstream pipelines. **Q: Can I dedupe across runs?** A: Yes - `post.id` is stable. Use it as a primary key in your downstream store. **Q: Can I run multiple groups in parallel?** A: Within a single run, groups are processed sequentially for predictability. To parallelize, launch multiple runs (e.g. with the API or scheduler) each with a subset of URLs. **Q: What time zone are timestamps in?** A: `publishTime` is Unix epoch **seconds** (UTC). `_metadata.fetched_at` is ISO 8601 in UTC. Format to local time in your downstream code. **Q: What about Meta's anti-scraping enforcement?** A: Meta's Terms restrict automated extraction. Your downstream use of the data must comply with Meta's Terms. The data-collection infrastructure is operated by an independent third-party provider, not by us. See the Terms section below. **Q: Can I use this data to train AI?** A: No. Meta's Terms prohibit AI training on Facebook data, and group posts and comments are independently copyrighted by their authors. **Q: What about minors?** A: Facebook has many under-18 users. Posters in groups may be minors. This Actor's Terms strictly prohibit using data of users you know or suspect are minors. See the Addendum below. **Q: Is there a Facebook Groups API I can use instead?** A: Meta's official Graph API exposes very limited Facebook group data and requires app review for most fields. This Actor is the practical Facebook Groups API alternative for posts, authors, reactions, top comments, and timestamps from public groups - no Facebook login, no cookies, no member data. **Q: Can I export Facebook group posts to CSV or Excel?** A: Yes. Every run's dataset can be downloaded as JSON, CSV, or XLSX from the Actor's dataset tab, or pulled via the Apify API. **Q: Can I use this for Facebook group lead generation?** A: Yes, where your lawful basis allows it. The Buyer-intent-signals example task is built for exactly this - surfacing posts where members ask for recommendations or describe a problem you solve. Compliance with privacy law is your responsibility (see the Terms of Service). **Q: Can I track a Facebook group over time?** A: Yes. Schedule the Actor to run on a cadence (see the Scheduling section) and dedupe rows by `post.id` in your downstream store to track changes, new posts, and engagement growth. **Q: Does it scrape Facebook group comments and replies?** A: Yes - the `fetchAllComments` add-on pulls the full comment thread per post, and `fetchCommentReplies` pulls replies per comment. Both are on by default and billed separately; turn them off if you only need posts. **Q: What is the alternative to the Facebook Groups API?** A: This Actor. Meta deprecated the Facebook Groups API in 2024-2025 - the `publish_to_groups` and `groups_access_member_info` permissions were removed and most group endpoints no longer return data. This Actor scrapes the public group post content the official API used to expose (posts, authors, reactions, top comments, timestamps) without requiring app review, OAuth, or a Facebook developer account. **Q: Does Meta allow scraping?** A: Meta's Terms of Service restrict automated extraction. This Actor is a software wrapper that calls a third-party data infrastructure provider; that provider, not the Publisher, bears responsibility for the data collection itself. Your downstream use of the returned data must independently comply with Meta's Terms. See the Terms of Service section below. **Q: How do I export Facebook group data?** A: Paste one or more public Facebook group URLs into the **Public Group URLs** input, click **Start**, and when the run finishes export the dataset as JSON, CSV, or XLSX from the dataset tab. You can also pull results programmatically via the Apify API. **Q: Can Apify scrape Facebook groups?** A: Yes - this Actor (and a small number of others on the Apify Store) scrape public Facebook group post data. This particular Actor positions as the alternative to Meta's deprecated official Groups API, with public-only access, no login, no cookies, and no member-data harvesting. **Q: What is replacing Facebook groups in 2026?** A: Public Facebook groups still exist and are still widely used; what changed is the official API access path. This Actor restores programmatic access to the public post content (not member rosters) that businesses and researchers used to get via Meta's Graph API. Communities themselves keep migrating to mixed channels - Discord, WhatsApp groups, LinkedIn Groups, and Reddit - but Facebook groups remain dominant for many verticals. **Q: How do I cancel a run?** A: Click **Abort** in the run's status header. The Actor honors abort signals and exits cleanly. **Q: Where do I report a bug?** A: Use UnseenUser's Apify profile contact form: https://apify.com/UnseenUser *** ### Related scrapers The full Facebook public-data cluster - every Actor in the family, with the slugs that actually resolve on Apify: - [Facebook Page Posts & Reels Scraper](https://apify.com/unseenuser/fb-posts) - the multi-mode Facebook posts Actor: pages, profiles, AND groups in one tool - [Facebook Page Details Scraper - Lead Gen](https://apify.com/unseenuser/fb-pages) - public Page details for B2B lead generation - [Facebook Comment Scraper - Posts & Reels](https://apify.com/unseenuser/fb-comments) - full comment threads and reactions on public Facebook content - [Facebook Events Scraper](https://apify.com/unseenuser/fb-events) - public Facebook event listings and details - [Facebook Marketplace Scraper](https://apify.com/unseenuser/fb-marketplace) - public Marketplace listings - [Facebook Profile Scraper - Bio & Followers](https://apify.com/unseenuser/fb-profile) - public profile bios and follower data - [Facebook Reels Scraper](https://apify.com/unseenuser/fb-reels) - public Reels with metadata - [Facebook Photos Scraper](https://apify.com/unseenuser/fb-photos) - public photo posts - [Facebook Reel Transcript Scraper](https://apify.com/unseenuser/fb-transcript) - transcripts of public Facebook Reels - [Facebook Page Follower Count](https://apify.com/unseenuser/fb-followers) - public Page follower counts [See all scrapers by UnseenUser ->](https://apify.com/unseenuser) *** ### Terms of Service By running this Actor you accept the UnseenUser Master Terms of Service V4.0 and the Actor-Specific Addendum below. Acceptance is by use. #### Architecture You (User) -> Apify Platform -> Actor (software) -> Third-party data infrastructure -> Public Facebook content - **You** run the Actor on the Apify platform with input parameters you choose. - **Apify** operates the cloud infrastructure that hosts and executes the Actor. - **The Publisher (UnseenUser)** publishes software code (the Actor) on Apify's platform. The Publisher does not store or retain data returned by the Actor. Because requests are made under the Publisher's provider accounts, copies of results may remain temporarily in those accounts for the retention periods listed in the Addendum, after which the provider deletes them. The Publisher does not access these copies except where needed to troubleshoot a run at the User's request. The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through. - **The third-party data infrastructure provider** is an independent company that operates the actual data-collection infrastructure and bears responsibility for the lawfulness of the collection itself. - **The source platform** is Facebook (Meta). Its public-facing group content is what the Actor returns. #### Actor-Specific Addendum **A. Architectural disclosure.** This Actor is a software wrapper. It accepts your input parameters, requests the relevant public Facebook group content via a third-party data infrastructure provider, and returns the structured result to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. Because requests are made under the Publisher's provider accounts, copies of results may remain temporarily in those accounts for the retention periods listed in the Addendum, after which the provider deletes them. The Publisher does not access these copies except where needed to troubleshoot a run at the User's request. **B. Nature of data returned.** This Actor returns public Facebook group post data: post text, author, reaction and comment counts, top comments, timestamps, and (when enabled) full comment threads and replies. It returns **no member data of any kind** - no member lists, no member contact details. Post and comment authors are personal data subject to GDPR, CCPA, Israeli Privacy Protection Law (including Amendment 13), and equivalent laws in your downstream processing, but only in your hands as the data controller, not in UnseenUser's hands as the software vendor. **C. Permitted use cases.** Social listening, community and trend research, lead and demand signals (with a lawful basis), market research, content research, brand monitoring. **D. Specifically prohibited uses.** In addition to Master ToS Section 4 prohibitions, you may NOT: - Scrape, derive, infer, or emit Facebook group member lists or any member data (post content only) - Use group post or commenter data to power mass-DM or auto-message tools, or build engagement-scoring databases for sale - Republish group posts or comments verbatim in commercial products without licensing - Train commercial AI/ML models on group content without separate licensing authority - Use sensitive group content (health, religion, politics, sexual orientation) to profile or target individuals - Attempt to access private groups or use cookies/authentication of any kind **E. Platform Terms of Service considerations.** Meta's Terms of Service prohibit automated extraction. Meta has aggressively litigated against scrapers. Your downstream use of any data obtained must independently comply with Meta's Terms. If Meta issues a cease-and-desist regarding data obtained via this Actor, notify UnseenUser within 48 hours via the Apify profile contact form (https://apify.com/UnseenUser) and cease your use immediately. **F. Group posts only - no member harvesting.** This is the central boundary of this Actor. It returns **post content only**. You may NOT use it, or pair it with other tools, to collect, infer, or build lists of group members, member contact details, or membership rosters. **G. Groups are a sensitive context.** Group membership and participation can reveal special-category data under GDPR Article 9: a health-condition support group, a religious or political group, an addiction-recovery group, or an LGBTQ group all expose sensitive characteristics by association. Treat post and comment content from such groups with heightened care. **H. Post and comment author personal data.** Authors and commenters are identified individuals whose posts reveal opinions, interests and sometimes special-category views. Establish and document a lawful basis, apply data minimization, set retention limits, and honor data subject rights. **I. Content copyright and AI training.** Each post and comment is independently copyrighted by its author. You may quote short excerpts with attribution and use aggregated metrics (counts are facts). You may NOT republish posts or comments verbatim in commercial products, build a "Facebook group search engine," or train commercial AI/ML models on group content without proper licensing. Meta's Terms prohibit AI training on Facebook data. **J. Sensitive-content patterns.** Group discussions frequently include sensitive disclosures: support groups carry illness and bereavement content, advocacy groups carry political and protected-category views, and recovery groups carry addiction disclosures. Do NOT weaponize these. **K. Minor protection - CRITICAL.** Facebook has a significant under-18 user population, and group posters and commenters may be minors. You MUST NOT use this Actor to scrape posts or comments of users you know or suspect are minors. You MUST NOT use this Actor for any product or service targeted at minors without parental-consent mechanisms compliant with COPPA (US), GDPR Article 8 (EU), and Israeli Privacy Law (heightened sensitivity for minors). DELETE any data you discover relates to a minor unless you have valid parental consent. **L. Data subject rights.** Authors and commenters have rights under GDPR / CCPA / Israeli Privacy Law: access, deletion, objection, rectification, and portability. Honor these with a typical 30-day SLA. **M. Optional AI enrichment (lead-intent "llm" mode).** Lead-intent detection is optional and off by default. Its `heuristic` mode runs locally and sends no data anywhere. Its `llm` mode transmits each processed post's text to Anthropic's API for classification, using an Anthropic API key you supply and an account you control: - In that flow you are the data controller and Anthropic is your processor; UnseenUser is not a party to your Anthropic agreement and never receives, stores, or processes the data. - You must have a lawful basis to send post content - which can include GDPR Article 9 special-category data, or content authored by minors - to Anthropic. - You must comply with Anthropic's terms and its data-use and retention policies. - Your downstream use of the lead signals is subject to the mass-messaging and lawful-basis restrictions in Clauses C and D. - Classifying post text is inference, not model training; it does not authorize training under Clause I. #### Governing law The Master Terms of Service are governed by the substantive laws of the State of Israel. Any dispute shall be brought exclusively in the competent civil courts of Tel Aviv-Jaffa, Israel. *** ### Support and contact - **Bug reports and feature requests:** UnseenUser's Apify profile contact form: https://apify.com/UnseenUser - **Response target:** Within 2 business days for first response. - **Service status:** Inherits the Apify platform status (https://status.apify.com) and upstream third-party data infrastructure availability. No independent uptime SLA from UnseenUser. - **Security disclosures:** Use the same Apify profile contact form. Do not include the affected API key in your message. *** *Document version: 1.1. Master ToS version: 4.0.* *** ## Apify Actor - Terms of Service **Version:** 4.0 **Effective Date:** May 5, 2026 ------------------------------- ### 0. ACCEPTANCE BY USE - IMPORTANT **Read this section first.** These Terms of Service ("Terms") form a binding legal agreement between you ("User," "you," "your") and UnseenUser, the Publisher of this Apify actor ("UnseenUser," "the Publisher," "we," "us," "our"). #### 0.1 How You Accept These Terms You accept these Terms by **any of the following actions**, each of which constitutes a clear, affirmative act of acceptance: - (a) **Running the Actor** - Initiating any execution of the Actor on the Apify platform - (b) **Using any output** returned by the Actor for any purpose - (c) **Continuing to access** the Actor's listing or documentation after these Terms are visible #### 0.2 Continuing Acceptance Each time you run the Actor or use its outputs, you reaffirm your acceptance of the then-current Terms. If you do not agree to these Terms or any subsequent update, you must stop using the Actor immediately. #### 0.3 No Anonymous Acceptance You cannot disclaim acceptance by: - Failing to read these Terms before running the Actor - Running the Actor through automated systems - Sharing your Apify account with others who may not have read these Terms By the act of running the Actor on Apify, you bind yourself, your organization (if applicable), and any individuals or systems acting on your behalf or under your authority. #### 0.4 If You Do Not Accept ## **If you do not agree to these Terms, you must not run the Actor.** No use is authorized without acceptance. ### PREAMBLE - UNDERSTANDING THE ARCHITECTURE Before using the Actor, please understand the technical architecture of the service: #### The Data Flow You (User) -> Apify Platform -> Actor (software) -> Third-Party API -> Source Platform You (User) <- Apify Platform <- Actor (software) <- Third-Party API #### What Each Party Does - **You (the User):** Run the Actor on the Apify platform with input parameters you choose - **Apify:** Operates the cloud infrastructure that hosts and executes Actors. Apify is a Czech-incorporated company (Apify Technologies s.r.o.) governed by its own Terms of Service. - **The Publisher (us):** Publishes software code (the Actor) on Apify's platform. The Actor is a thin wrapper that translates your input into requests to a third-party API and returns the API's responses to you. **The Publisher does not operate scraping infrastructure. The Publisher does not store or retain data returned by the Actor.** Because requests are made under the Publisher's provider accounts, copies of results may remain temporarily in those accounts for the retention periods listed in the Addendum, after which the provider deletes them. The Publisher does not access these copies except where needed to troubleshoot a run at the User's request. **The Publisher does not see, log, or process the personal data of any individuals returned in the Actor's outputs beyond what is incidental to passing the data through.** - **Third-Party API Provider:** HarvestAPI (https://harvest-api.com) or Scrape Creators (https://scrapecreators.com). These are independent third-party companies that operate scraping infrastructure and return data from source platforms. - **Source Platform:** LinkedIn, TikTok, YouTube, Reddit, Linktree, etc. These are the platforms whose publicly visible data is accessed by the Third-Party API Providers. #### Why This Matters ## Your relationship with the Publisher is that of a **software user** to a **software vendor**. The Publisher has the responsibilities of a software vendor (functional code, accurate documentation) and the limits of one (the Publisher is not responsible for how you use the data you obtain). These Terms operate alongside but do not replace: - Apify's Terms of Service and Acceptable Use Policy (governing your relationship with Apify) - HarvestAPI Terms of Service and Scrape Creators Terms of Service (governing the underlying data infrastructure) - Source Platform terms (LinkedIn, TikTok, etc.) governing the public data accessed - Applicable law in your jurisdiction and the jurisdictions of data subjects These Terms incorporate the actor-specific addendum published in each Actor's individual listing ("Addendum"). In the event of a conflict, the more restrictive provision applies. *** ### 1. NATURE OF THE SERVICE #### 1.1 What the Actor Is The Actor is a software program published on the Apify platform. Each Actor: - (a) Accepts structured input from you on the Apify platform - (b) Translates that input into HTTP requests to a third-party API operated by HarvestAPI or Scrape Creators - (c) Receives HTTP responses from that third-party API - (d) Returns the response data to you in a structured format on the Apify platform The Actor's source code is hosted on Apify's infrastructure. The Actor runs in Apify's cloud, not on the Publisher's servers. The Publisher operates no servers running the Actor. #### 1.2 What the Actor Is Not The Actor is **not**: - (a) A scraping tool - the Publisher does not operate scraping infrastructure, proxies, headless browsers, or fake accounts - (b) A direct connection to any source platform - connections to source platforms are made by HarvestAPI / Scrape Creators - (c) A data storage or data retention service - the Publisher does not maintain a database of any data the Actor returns - (d) A licensed access channel to LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta, Linktree, or any other source platform - (e) Affiliated with, endorsed by, sponsored by, or authorized by any source platform #### 1.3 The Publisher's Limited Role The Publisher's role is limited to: - (a) Designing and writing the Actor's source code - (b) Publishing the Actor on the Apify Store - (c) Maintaining the Actor (updating it when API providers change schemas) - (d) Providing documentation and customer support via Apify's contact mechanism The Publisher is a software vendor, similar to a developer who publishes an app on the Apple App Store or Google Play Store. The Publisher is not a data provider, data broker, data processor, or data controller for purposes of GDPR, CCPA, Israel's Privacy Protection Law, or equivalent. #### 1.4 The Third-Party API Providers' Role HarvestAPI (https://harvest-api.com) and Scrape Creators (https://scrapecreators.com) are independent third-party companies. They: - (a) Operate the actual data scraping infrastructure - (b) Maintain relationships with source platforms (or accept the operational risk of accessing public data without such relationships) - (c) Are themselves Apify publishers (HarvestAPI publishes 9+ actors directly; Scrape Creators publishes 10+) - (d) Provide their own Terms of Service governing their operations - (e) Are responsible for compliance obligations relating to the data collection itself The Publisher is a customer of these providers. The Publisher is not their agent, partner, or representative. *** ### 2. WHO MAY USE THE ACTOR #### 2.1 Eligibility You may use the Actor only if: - (a) You are at least 18 years old or the age of majority in your jurisdiction - (b) You have legal capacity to enter into binding contracts - (c) You are not located in or resident of a country subject to comprehensive sanctions by the United States, European Union, United Kingdom, or Israel - (d) You are not on any prohibited persons list #### 2.2 User Representations By using any Actor, you represent and warrant that: - (a) **Truthful identity:** Information you provide about your identity and intended use is accurate - (b) **Lawful intent:** Your intended use complies with applicable law in your jurisdiction - (c) **Source platform compliance:** You will independently comply with the Terms of Service of any source platform whose data you obtain through the Actor - (d) **Data subject rights:** Where Actor outputs include personal data, you will respect data subject rights under applicable law - (e) **No prohibited use:** You will not use the Actor for any of the purposes prohibited in Section 4 These representations are continuous - they must remain true throughout your use. *** ### 3. PERMITTED USES The Actor may be used for any lawful purpose, including: - Market research and competitive analysis - Academic research - Journalism and investigative reporting - Internal business intelligence - Brand monitoring - Recruitment research where consistent with applicable employment law - Building products that further process publicly available information lawfully Specific permitted uses for each Actor are described in that Actor's individual listing and Addendum. *** ### 4. PROHIBITED USES You may not use the Actor for any of the following: #### 4.1 Illegal Activity Activity illegal under the law of your jurisdiction, the User's jurisdiction, or the jurisdiction of any data subjects. #### 4.2 Harassment, Stalking, and Personal Targeting - Compiling profiles for harassment, stalking, or doxxing - Tracking individuals' movements or activities without their knowledge - Building profiles of journalists, activists, dissidents, or vulnerable populations for retaliatory purposes #### 4.3 Discrimination - Using outputs for discriminatory employment, lending, housing, or insurance decisions based on protected characteristics - Building lists for discriminatory purposes #### 4.4 Spam and Unsolicited Commercial Communication - Sending unsolicited marketing in violation of CAN-SPAM, CASL, GDPR, PECR, Israeli Anti-Spam Law (Section 30A of the Communications Law), or equivalent laws - Building "lead lists" from scraped contacts without proper consent infrastructure - Reselling contact data for spam purposes #### 4.5 Fraud and Deception - Identity theft or impersonation - Generation of fake reviews, testimonials, or coordinated inauthentic behavior - Election interference or political disinformation - Securities fraud #### 4.6 Source Platform Abuse - Using outputs to circumvent technical protection measures of source platforms - Creating fake accounts on source platforms based on Actor outputs - Vote manipulation, engagement manipulation, or platform algorithm gaming - Building services that competitively substitute for source platforms #### 4.7 Reselling the Actor's Service - Reselling raw Actor outputs as your own data product or scraping-as-a-service - Sharing your Apify credentials to provide third parties indirect access - Building competing API services using Actor outputs #### 4.8 AI Training Without Authorization - Using Actor outputs as training data for commercial AI/ML models without separate licensing authority from the source platform #### 4.9 Sensitive Targeting - Specifically targeting or profiling based on health conditions, sexual orientation, religious beliefs, political opinions, or other sensitive characteristics - Targeting children under 16 (or local age of consent for data processing) #### 4.10 Privacy Law Violations - Processing personal data of EU/UK/California/Israeli residents without complying with applicable privacy law - Failing to honor data subject access, deletion, or objection requests - Processing data for purposes incompatible with its publication context *** ### 5. SOURCE PLATFORM TERMS - YOUR RESPONSIBILITY #### 5.1 Acknowledgment The Actor accesses publicly visible data on third-party platforms ("Source Platforms") through the Third-Party API Providers (HarvestAPI / Scrape Creators). Source Platforms include LinkedIn, TikTok, YouTube, Reddit, X (Twitter), Meta/Facebook, Linktree, Komi, Pillar, Linkbio, Linkme, and Amazon. #### 5.2 Your Sole Responsibility You acknowledge: - (a) **You are solely responsible for ensuring your downstream use of data obtained through the Actor complies with the Source Platform's Terms of Service** - (b) The Publisher makes no representation that any specific use is permitted under any Source Platform's terms - (c) The Third-Party API Providers, not the Publisher, bear responsibility for the lawfulness of the data collection itself - (d) You should review Source Platform terms before commercial use: - LinkedIn: https://www.linkedin.com/legal/user-agreement - TikTok: https://www.tiktok.com/legal/page/global/terms-of-service/en - YouTube: https://www.youtube.com/static?template=terms - X: https://twitter.com/en/tos - Reddit: https://www.redditinc.com/policies/user-agreement - Meta: https://www.facebook.com/legal/terms - Linktree: https://linktr.ee/s/terms/ #### 5.3 Cease-and-Desist Compliance If you receive a cease-and-desist letter or other legal demand from a Source Platform regarding your use of Actor outputs, you must: - (a) Cease the contested use immediately - (b) Notify UnseenUser within 48 hours via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) - (c) Cooperate with the Publisher as needed to mitigate - (d) Not assert against the Publisher any claim arising from your inability to use the Actor for that Source Platform *** ### 6. DATA PROTECTION - REFLECTING ACTUAL ARCHITECTURE #### 6.1 Roles Under Privacy Law For purposes of GDPR, UK GDPR, CCPA, Israel's Privacy Protection Law (PPL) including Amendment 13, and equivalents: - **You (the User) are the Data Controller** of any personal data you obtain through the Actor and subsequently process for your own purposes - **HarvestAPI and Scrape Creators** are the entities that collect data from source platforms - they bear the responsibilities of data processors or controllers (depending on context) for the collection itself - **The Publisher acts solely as a software vendor**, not as a data controller or processor, because the Publisher does not store, retain, or substantively process personal data - the Actor merely passes API responses through. Because requests are made under the Publisher's provider accounts, copies of results may remain temporarily in those accounts for the retention periods listed in the Addendum, after which the provider deletes them. The Publisher does not access these copies except where needed to troubleshoot a run at the User's request. #### 6.2 No Data Retention by the Publisher The Publisher confirms: - (a) The Publisher does not maintain a database of personal data obtained through the Actor - (b) The Actor passes data from the Third-Party API directly to you on the Apify platform - data does not flow through the Publisher's infrastructure - (c) Apify's standard execution and operational logging may include limited information about Actor runs (input parameters, run duration, data volume) - this is governed by Apify's own privacy practices - (d) The Publisher does not access, view, or analyze your Actor outputs except as needed for technical support if you specifically share them with the Publisher #### 6.3 Your Obligations as Data Controller Where your use of the Actor involves processing personal data, you are responsible for: - (a) Establishing a lawful basis for your processing (consent, legitimate interest with documented balancing test, contract, etc.) - (b) Providing transparent notice to data subjects as required by applicable law - (c) Honoring data subject access, rectification, erasure, restriction, and portability requests - (d) Implementing appropriate security measures - (e) Conducting Data Protection Impact Assessments where required - (f) Appointing a Data Protection Officer if your operations require one - (g) Registering databases with applicable supervisory authorities - (h) Honoring opt-out requests for direct marketing - (i) Cross-border transfer safeguards where data crosses borders #### 6.4 Israel's Amendment 13 - User Compliance If your use of the Actor involves Israeli residents' personal data, you must comply with the Privacy Protection Law as amended (Amendment 13, effective August 14, 2025). These obligations are yours as the data controller, not the Publisher's as the software vendor. #### 6.5 Sensitive Data Targeting Restrictions You will not use the Actor to specifically target, profile, or build datasets focused on: - Health or medical conditions - Religious beliefs - Political opinions - Sexual orientation or gender identity - Genetic or biometric data - Criminal history - Children under 16 *** ### 7. INTELLECTUAL PROPERTY #### 7.1 Actor Code The Actor's source code, schemas, documentation, and branding are owned by the Publisher. You receive a limited, non-exclusive, non-transferable, revocable license to use the Actor for permitted purposes during your active subscription/run with Apify. #### 7.2 Output Data The Publisher claims no ownership over the public data the Actor returns. Source Platforms may have copyright, database rights, or other rights in their data; data subjects may have copyright in user-generated content. Your use of output data must respect these rights independently. #### 7.3 Restrictions You may not reverse engineer, decompile, or reuse the Actor's code in a competing actor. #### 7.4 Feedback ## Feedback you provide may be used by the Publisher to improve products without compensation to you. ### 8. PRICING AND PAYMENT #### 8.1 Apify Platform Billing Pricing is administered through Apify's pricing models. Apify processes all payments. Apify's payment terms govern refunds and disputes. #### 8.2 Pricing Changes The Publisher may change Actor pricing with at least 14 days' notice via the Actor's Apify listing. #### 8.3 No Refunds for Misuse ## If your access is suspended or terminated for breach of these Terms, you forfeit any unused balance and are not entitled to refunds. ### 9. SERVICE AVAILABILITY AND CHANGES #### 9.1 No Uptime Guarantee The Actor depends on: - (a) The Apify platform - (b) Underlying API providers (HarvestAPI, Scrape Creators) - (c) Source Platforms' continued public accessibility Any of these may change behavior, restrict access, or become unavailable without notice. The Publisher makes no uptime guarantees. #### 9.2 Service Discontinuation ## The Publisher may discontinue any Actor at any time. Reasonable notice will be provided when feasible. ### 10. DISCLAIMERS #### 10.1 "AS IS" Service THE ACTOR IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR PURPOSE, NON-INFRINGEMENT, OR ACCURACY OF DATA. #### 10.2 No Representation of Lawfulness The Publisher makes no representation that your specific use of the Actor or the data it returns is lawful in your jurisdiction or under any Source Platform's terms. The burden of determining lawfulness for your use case is yours. #### 10.3 No Endorsement of Source Content ## Content returned by the Actor was created by third parties. The Publisher does not endorse, verify, or take responsibility for it. ### 11. LIMITATION OF LIABILITY #### 11.1 Aggregate Liability Cap TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AGGREGATE LIABILITY OF THE PUBLISHER FOR ALL CLAIMS RELATING TO THE ACTOR EXCEED THE GREATER OF: - (a) ONE HUNDRED U.S. DOLLARS (US $100), OR - (b) THE AMOUNTS YOU PAID THROUGH APIFY FOR USE OF THE ACTOR IN THE THREE (3) MONTHS IMMEDIATELY PRECEDING THE EVENT #### 11.2 Excluded Damages THE PUBLISHER IS NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOSS OF PROFITS, REVENUE, OR DATA, EVEN IF ADVISED OF THE POSSIBILITY. #### 11.3 Time Limit ## Any claim must be brought within one (1) year of the event. ### 12. INDEMNIFICATION #### 12.1 Your Indemnification of the Publisher You agree to defend, indemnify, and hold harmless the Publisher from any: - Claims arising from your use of the Actor - Claims arising from your violation of these Terms - Claims arising from your violation of any law (including privacy law) - Claims arising from your violation of any Source Platform's Terms of Service - Claims arising from your processing of personal data obtained through the Actor - Reasonable attorneys' fees and costs of defending such claims #### 12.2 Defense The Publisher may assume defense at your expense. You will cooperate with the Publisher's defense. #### 12.3 Scope The indemnification covers reasonable, foreseeable third-party claims arising from your use. It does not extend to: - Claims arising from the Publisher's gross negligence or willful misconduct - Claims regarding the Actor's source code itself (those are the Publisher's responsibility) - Claims regarding the Third-Party API Provider's data collection (those are their responsibility) *** ### 13. SUSPENSION AND TERMINATION #### 13.1 Termination by the Publisher The Publisher may terminate your access for material breach, illegal use, breach of warranty, or upon credible legal demand. #### 13.2 Effects of Termination Your license ends, you must cease use, and applicable provisions survive. #### 13.3 Termination by You ## You may stop using the Actor at any time on Apify. ### 14. DISPUTE RESOLUTION #### 14.1 Informal Resolution First Send a detailed written description of the dispute via UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) and wait 60 days for resolution attempt before any formal claim. #### 14.2 Governing Law These Terms are governed by the substantive laws of the State of Israel, without regard to conflict of law principles. #### 14.3 Exclusive Jurisdiction Any dispute shall be brought exclusively in the competent civil courts of Tel Aviv-Jaffa, Israel. #### 14.4 No Class Actions You agree to bring claims only in your individual capacity. #### 14.5 Attorneys' Fees ## The prevailing party recovers reasonable attorneys' fees. ### 15. MISCELLANEOUS #### 15.1 Entire Agreement These Terms (with Addendum and incorporated documents) are the entire agreement. #### 15.2 Severability Unenforceable provisions are reformed to the minimum extent or severed. #### 15.3 Assignment You may not assign without the Publisher's consent. The Publisher may assign to affiliates, successors, or acquirers. #### 15.4 Force Majeure Neither party is liable for failure due to events beyond reasonable control, including changes by Source Platforms or Third-Party API Providers, or actions by Apify. #### 15.5 Third-Party Beneficiaries Apify, HarvestAPI, and Scrape Creators are intended third-party beneficiaries of Sections 4 (Prohibited Uses), 5 (Source Platform Compliance), and 12 (Indemnification). #### 15.6 Survival Sections 0 (Acceptance), 4, 5, 6, 7, 10, 11, 12, 14, and 15 survive termination. #### 15.7 Language English controls. Translations are for convenience only. #### 15.8 Publisher Identification for Legal Process ## The Publisher operates on the Apify platform under the username UnseenUser (apify.com/UnseenUser). The Publisher is a registered legal entity. Upon receipt of valid legal process (subpoena, court order, or equivalent) directed through Apify's official channels, the Publisher's full legal identity may be disclosed as required by law. This Section ensures that you have a valid path to legal recourse if needed. ### 16. ACKNOWLEDGMENT By using any Actor, you acknowledge that: - (a) You have read these Terms - (b) You understand the architecture: you are using software (the Actor) on Apify's platform that calls third-party APIs - (c) You accept responsibility for your use, including for compliance with Source Platform terms - (d) Your indemnification obligations cover third-party claims arising from your use - (e) Disputes are resolved in Israeli courts - (f) The Publisher's identity, while not publicly disclosed in this listing, can be obtained through valid legal process via Apify For questions, use UnseenUser's Apify profile contact form (https://apify.com/UnseenUser) before running the Actor. *** ## 🛡️ Part 4: Actor-Specific Terms of Service Addendum ### 🛡️ Actor-Specific ToS Addendum - 👥 Facebook Groups Scraper This addendum supplements the Master Terms of Service V4.0. By running this Actor, you accept both the Master ToS and this addendum. #### A. Architectural Disclosure This Actor is a software wrapper. It accepts your input parameters, calls the Scrape Creators `/v1/facebook/group/posts` endpoint (and, only when you enable them, `/v1/facebook/post/comments` and `/v1/facebook/post/comment/replies`), combines the results into a structured output, and returns the combined data to you on the Apify platform. UnseenUser does not store, log, or substantively process the data returned. Because requests are made under the Publisher's provider accounts, copies of results may remain temporarily in those accounts for the retention periods listed in the Addendum, after which the provider deletes them. The Publisher does not access these copies except where needed to troubleshoot a run at the User's request. The data flows from Scrape Creators through Apify's runtime directly to you. #### Data Retention Scrape Creators: Requests are made through the Publisher's Scrape Creators account. Scrape Creators has confirmed in writing that full copies of responses linked to that account are designed to expire within 31 days. Scrape Creators also keeps request, usage, security and operational records to run and protect its service. Its privacy policy does not set a fixed retention period for these records, and usage logs may be kept indefinitely (https://scrapecreators.com/privacy). Scrape Creators does not currently offer automatic deletion on a shorter schedule. Where technically available, the Publisher can ask Scrape Creators to delete records linked to its account, and will pass on a User's reasonable deletion request relating to that User's runs. If the optional LLM lead-intent mode is turned on, post text is also sent to Anthropic under the User's own API key and account, not the Publisher's. Retention of that data is governed by the User's own agreement with Anthropic, and the Publisher has no access to that account. #### B. Nature of Data Returned This Actor returns public Facebook group post data: post text, author, reaction and comment counts, top comments, timestamps, and (when enabled) full comment threads and replies. It returns **no member data of any kind** - no member lists, no member contact details. Post and comment authors are **personal data** subject to GDPR, CCPA, Israeli Privacy Protection Law (including Amendment 13), and equivalent privacy laws in your downstream processing - but **only in your hands as the data controller**, not in UnseenUser's hands as the software vendor. #### C. Permitted Use Cases You may use this Actor for the following purposes (non-exhaustive list): - **Social listening** - what a public community discusses - **Community and trend research** - topics and engagement in a group - **Lead and demand signals** - intent in public discussion, with a lawful basis for follow-up - **Market research** - a niche community's conversations - **Content research** - what posts resonate - **Brand monitoring** - public mentions in relevant groups #### D. Specifically Prohibited Uses In addition to Master ToS Section 4 prohibitions, you may NOT: - Scrape, derive, infer, or emit Facebook group member lists or any member data (post content only) - Use group post or commenter data to power mass-DM/auto-message tools or build engagement-scoring databases for sale - Republish group posts or comments verbatim in commercial products without licensing - Train commercial AI/ML models on group content without separate licensing authority - Use sensitive group content (health, religion, politics, sexual orientation) to profile or target individuals - Attempt to access private groups or use cookies/authentication #### E. Platform Terms of Service Considerations Meta's Terms of Service prohibit automated extraction. Meta has aggressively litigated against scrapers (Meta v. BrandTotal - settled with permanent injunction; Meta v. Octopus Data; Meta v. Bright Data - pending). Facebook's Terms of Service prohibit automated extraction. This Actor accesses publicly visible group post data via Scrape Creators - Scrape Creators bears responsibility for the lawfulness of the data collection. Your downstream use must independently comply with Meta's Terms of Service. If Meta issues a cease-and-desist regarding data obtained via this Actor, notify UnseenUser within 48 hours via the Apify profile contact form (apify.com/UnseenUser) and cease your use immediately. #### F. Group Posts Only - No Member Harvesting This is the central boundary of this Actor. It returns **post content only**. You may NOT use it, or pair it with other tools, to collect, infer, or build lists of group members, member contact details, or membership rosters. Scrape Creators provides no member endpoint, and member harvesting is prohibited regardless. This is both a hard policy rule and a deliberate market boundary the Publisher does not cross. #### G. Groups Are a Sensitive Context Group membership and participation can reveal special-category data under GDPR Article 9: a health-condition support group, a religious or political group, an addiction-recovery group, or an LGBTQ group all expose sensitive characteristics by association. Treat post and comment content from such groups with heightened care: do not use it to infer or record a person's health, religion, politics, or sexual orientation, and do not build datasets that profile individuals by the sensitive groups they post in. Where group context is sensitive, the safest course is to store aggregate signal, not individual records. #### H. Post and Comment Author Personal Data Authors and commenters are identified individuals whose posts reveal opinions, interests and sometimes special-category views. Establish and document a lawful basis, apply data minimization (store the signal, not the full text, where possible), set retention limits, and honor data subject rights. Recent European DPA decisions increasingly hold that people do not reasonably expect their public group posts to be used for commercial outreach. #### I. Content Copyright and AI Training Each post and comment is independently copyrighted by its author. You may quote short excerpts with attribution (typically fair use) and use aggregated metrics (counts - facts). You may NOT republish posts or comments verbatim in commercial products, build a "Facebook group search engine," or train commercial AI/ML models on group content without proper licensing. Meta's Terms prohibit AI training on Facebook data. Recent litigation (NYT v. OpenAI, Andersen v. Stability AI, Reddit v. Perplexity) shows AI training on platform content is contested. Your AI training use is your own legal exposure. #### J. Sensitive-Content Patterns Group discussions frequently include sensitive disclosures: support groups carry illness and bereavement content, advocacy groups carry political and protected-category views, and recovery groups carry addiction disclosures. Do NOT weaponize these: do not build "vulnerability lists" from inferred life events, do not use bereavement content for grief-targeting marketing, and do not use health or recovery disclosures to identify candidates for products without explicit consent. #### K. Minor Protection - CRITICAL Facebook has a significant under-18 user population, and group posters and commenters may be minors (school groups, youth communities). You MUST: - NOT use this Actor to scrape posts or comments of users you know or suspect are minors - NOT use this Actor for any product or service targeted at minors without parental-consent mechanisms compliant with COPPA (US), GDPR Article 8 (EU), and Israeli Privacy Law (heightened sensitivity for minors) - DELETE any data you discover relates to a minor unless you have valid parental consent If content or an author suggests a minor, treat the data as belonging to a minor by default. This restriction is non-negotiable. #### L. Data Subject Rights and Cease-and-Desist Protocol Authors and commenters have rights under GDPR / CCPA / Israeli Privacy Law: access, deletion, objection (absolute for direct marketing under Article 21), rectification, and portability. Honor these with a typical 30-day SLA. If a data subject contacts YOU directly demanding deletion, honor it promptly, do NOT route them to UnseenUser (the software vendor is not the data controller), you may suggest they contact Meta directly since the data originates there, and document the request and your response. If Meta, Scrape Creators, or a regulator contacts UnseenUser regarding your use, UnseenUser will notify Apify per Master ToS Section 8, may suspend access pending investigation, and you agree to provide documentation of your lawful basis on reasonable request. #### M. Optional AI Enrichment (Lead-Intent "llm" Mode) Lead-intent detection is optional and off by default. Its `heuristic` mode runs locally and sends no data anywhere. Its `llm` mode transmits each processed post's text to Anthropic's API for classification, using an Anthropic API key you supply and an account you control: - In that flow you are the data controller and Anthropic is your processor; UnseenUser is not a party to your Anthropic agreement and never receives, stores, or processes the data. - You must have a lawful basis to transmit post content - which can include special-category data under GDPR Article 9, or content authored by minors - to Anthropic. - You must comply with Anthropic's applicable terms and its data-use and retention policies. - Your downstream use of the resulting lead signals is subject to the mass-messaging prohibition and lawful-basis requirement of Clauses D and C. - Classifying post text is inference, not model training, and does not authorize the AI/ML training prohibited by Clause I. # Actor input Schema ## `startUrls` (type: `array`): One or more public Facebook group URLs (or numeric group IDs). A sample public group is pre-filled so you can Run straight away - just replace it with your own. Private groups are not supported. ## `maxPosts` (type: `integer`): How many posts to fetch per group. Leave at 0 to fetch every available post. Tip: posts come in pages of 3, so small values round up to the next multiple of 3. The field is pre-filled with a small value so the first run finishes quickly and cheaply; raise it (or set 0) for a full scrape. ## `onlyPostsNewerThan` (type: `string`): Skip posts older than this date. Accepts a date (e.g. 2026-07-01) or a full date-time. Leave empty to fetch posts of any age. Posts with no detectable timestamp are always kept. ## `sortBy` (type: `string`): A hint sent to Facebook for how to order posts; Facebook decides the final order. Recent activity and Top posts surface older, more-commented posts (more comment/reply rows). Chronological returns the newest posts first, which in a busy group are often brand-new with no comments yet. For a guaranteed engagement ranking, sort the finished dataset by the Reactions column in the Engagement view. ## `fetchAllComments` (type: `boolean`): Fetch the full comment thread for every post (paginated). On by default. Billed add-on: each comment is its own result row, so this can significantly increase run cost on active groups. ## `fetchCommentReplies` (type: `boolean`): Also fetch replies for every comment. On by default. Billed add-on: each reply is its own result row. Only takes effect when 'Fetch full comment threads' is on. Replies are only requested for comments that actually have any. ## `includeTopComments` (type: `boolean`): Attach the post's few 'top comments' inside the post object itself, at no extra cost (they come free with the post). This is separate from the full comment threads above. Off by default. ## `includeGroupProfile` (type: `boolean`): Add one profile row per group with its public About-page data: member count, privacy, categories, rules, activity, description, and created date. No member or personal data (admin/moderator lists are excluded). Off by default; adds one extra result row per group. ## `verifyPublicBeforeScraping` (type: `boolean`): Check each group's About page before scraping and, if it isn't Public, skip it as 'private' (never billed) instead of guessing from a failed request. Adds one group-info request per group - but reuses the same request when 'Include group profile row' is also on, so there's no extra call in that case. ## `leadIntentDetection` (type: `string`): Adds a 'leadIntent' object flagging buyer intent. 'Heuristic' uses keyword rules locally and sends no data anywhere. 'AI / LLM' is more accurate but TRANSMITS EACH CLASSIFIED POST'S TEXT TO ANTHROPIC'S API under your own key/account (Anthropic's data-use and retention policies apply), and adds cost and latency per item. You are the data controller for that transfer. ## `leadIntentScope` (type: `string`): Which rows get a 'leadIntent'. Comments can hold real buyer intent, but most are noise. WARNING: in AI / LLM mode each comment and reply is a separate Anthropic call - a post with 40 comments means 40 extra classifications, so wider scope can multiply cost and latency many times over. In free Heuristic mode, wider scope is cheap. ## `leadIntentLlmModel` (type: `string`): Only used in AI / LLM mode. Haiku is cheapest and best for high-volume runs; Opus is most accurate but costs far more per item. Advanced: the LEAD_INTENT_LLM_MODEL env var overrides this with any model id. ## `anthropicApiKey` (type: `string`): Only used in AI / LLM mode. Paste your own Anthropic API key - it's stored encrypted and masked, billed on your own Anthropic account, and never written to the run's saved input snapshot or output. Leave empty to fall back to an ANTHROPIC_API_KEY environment variable, or if you're not using LLM mode. ## Actor input object example ```json { "startUrls": [ "https://www.facebook.com/groups/4950038445096459" ], "maxPosts": 3, "sortBy": "RECENT_ACTIVITY", "fetchAllComments": true, "fetchCommentReplies": true, "includeTopComments": false, "includeGroupProfile": false, "verifyPublicBeforeScraping": false, "leadIntentDetection": "off", "leadIntentScope": "posts", "leadIntentLlmModel": "claude-haiku-4-5" } ``` # Actor output Schema ## `results` (type: `string`): One row per public Facebook group post. Opens the dataset pre-filtered to the Overview view (post id, text, author, reactions, comments, timestamps, links). ## `runSummary` (type: `string`): Per-run summary written to the key-value store: groups processed, posts pushed, free-plan-cap status, per-group error counts. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ "https://www.facebook.com/groups/4950038445096459" ], "maxPosts": 3 }; // Run the Actor and wait for it to finish const run = await client.actor("unseenuser/fb-groups").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": ["https://www.facebook.com/groups/4950038445096459"], "maxPosts": 3, } # Run the Actor and wait for it to finish run = client.actor("unseenuser/fb-groups").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ "https://www.facebook.com/groups/4950038445096459" ], "maxPosts": 3 }' | apify call unseenuser/fb-groups --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,unseenuser/fb-groups" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/a0dmGh52E4yh5un7h/builds/0nwj8aUT1IW8cBKWw/openapi.json