Facebook Post Search (Apify)
Find exact keyword, brand and product mentions in public Facebook posts, pages, groups, reels and videos, filtered by date and market, with engagement metrics. JSON or CSV.
Hosted MCP Server
npx add-mcp 'https://mcp.apify.com/?tools=monkey.d.scraping/facebook-public-group-mentions'Installs into Claude Code, Codex, Cursor and more
Documentation
Facebook Post Search — Exact Keyword Mentions (monkey.d.scraping/facebook-public-group-mentions) Actor
Find exact keyword, brand and product mentions in public Facebook posts, pages, profiles, groups, reels and videos. Filter by date and market, export available engagement metrics and reuse history to refresh known posts.
- URL: https://apify.com/monkey.d.scraping/facebook-public-group-mentions.md
- Developed by: Monkey D. Scraping (community)
- Categories: Social media, MCP servers
- Features: Limited permissions
- Stats: 2 total users, 2 monthly users, 86.2% runs succeeded, 1 bookmarks
- User rating: No ratings yet
Pricing
from $1.99 / 1,000 matched public group posts
This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 section below.
Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).
README
Facebook Post Search — Exact Keyword Mentions
Find public Facebook posts that mention your brand, product or topic. Verify the exact phrase in the available post text, then refresh reactions, comments and shares by post ID on each run that reuses your history dataset.
Find exact mentions and refresh engagement
- Search a phrase. For example, enter
tailgate, choose the US market and a date range, and set Search scope to all public posts to include pages, public profiles, groups, reels and videos. The Actor checks the available post text and reports the matched phrase inmatchedKeywords. Matching ignores case and normalizes whitespace and Unicode. Add spelling variants as separate keywords. - Reuse your history. In all-public-posts mode, the summary reports the history dataset ID under
retention.datasetId. Reuse that ID inhistoryDatasetIdon later runs. The Actor rereads known posts and saves the latest available reactions, comments and shares alongside newly discovered posts. - Review the refresh. The summary reports how many known IDs were refreshed and how many new IDs were found. If a known post cannot be refreshed, the earlier observation remains in the history dataset. The run dataset contains posts verified during that run. Missing counters are exported as
null.
Several phrases are searched at the same time, so long keyword lists in several languages finish faster within the same run timeout.
Pricing: $0.029 per run + $0.00199 per matched post delivered ($1.99 per 1,000 posts, plus the run fee). Platform usage is included. The run fee applies even when no posts match.
中文用户 / 中文用戶: 简体中文说明 · 繁體中文說明(Facebook群组监控、脸书公开群组帖子搜索、品牌提及监测)
When to use it
- Find literal mentions of a brand, product, place or phrase in discoverable public Facebook posts.
- Collect research samples whose matching rule can be checked against the original text.
- Exclude unwanted phrases without sending post text to an AI classifier.
For example, pasta madre matches that phrase with normalized spacing and capitalization. To include alternatives such as lievito naturale, add each one as its own phrase.
Quick start
- Enter one or more words or phrases.
- Choose a maximum number of posts per phrase, a publication period and search market.
- Start the run and review Matching posts and the run summary.
Start with a small sample:
{"keywords":["python programming"],"maxPosts":3,"afterDate":"anytime","countryCode":"us"}
Matching and filters
| Input | Behavior |
|---|---|
keywords | Match any listed word or phrase in the available original post text; up to 100 phrases. List each variant explicitly. |
excludeKeywords | Reject a post containing any excluded word or phrase, even when an inclusion matches. |
maxPosts | Per-phrase upper bound. |
afterDate | Use anytime, last_week (7 days), last_month (30 days), this_year, a start date such as 2026-01-01, or 14 days. All dates use UTC. When a date filter is active, only posts with a publication date are included. |
countryCode | Discovery market: US, UK, Italy, Germany, France or Spain. |
searchScope | groups searches posts published in public Facebook groups only; all also includes pages, public profiles, reels and videos. |
Matching ignores letter case and normalizes Unicode and whitespace. Accents and punctuation remain meaningful. Word boundaries prevent apple from matching inside pineapple. Enter plain words or phrases. Matching always runs on the original post text.
Group posts and Facebook visibility
Facebook shows many group posts only to logged-in members, even in groups whose name and description are public. Visitors who are not logged in get another post of the group instead. This Actor reads posts as a visitor, so it saves only group posts whose text Facebook shows publicly; the rest cannot be collected by any login-free tool. In real Italian health-topic searches, Facebook showed the text of about half to 60% of the group posts found. The run summary reports both counts (groupPostsRead, groupPostsHiddenFromVisitors) and, in groups mode, the final status message states them in plain words. Very specific phrases such as a disease plus a city often have few or no public group posts at all: the message then says that search found no more matching posts for those phrases. For broader coverage, add shorter phrases or use all, which also searches pages and public profiles.
Each post is saved once per run. When it matches several configured phrases, matchedKeywords lists all matches and searchKeyword records the first matching phrase with remaining capacity. Deduplication applies within each run.
Output
| Fields | Meaning |
|---|---|
post_id, post_url, text | Unique post identity, source link and public post text. |
textCompleteness | complete when text is the full post body Facebook serves on the post's own page (also for long posts); unavailable when no text is available. Text inside a shared or attached post is not part of text. |
source_type | Where the post was published: group, page_or_profile, video or reel. |
matchedKeywords, matchReason | Literal phrases found and the rule explaining inclusion. |
group_id, group_name, group_url | Filled for group posts. Empty (null) for posts by pages and profiles, which have no group: check source_type. When Facebook omits the group details, group_id and group_url come from the post link (group_id can then be the group's URL name) and group_name stays null. |
author_id, author_name, author_url | Available author details. |
date, processed_at | Publication time when available and collection time. |
reaction_count, comment_count, share_count | Public engagement counts at collection time. |
image_url | An available post image. |
searchKeyword, searchCountry | Attribution and discovery market. |
Unavailable fields are null. The dataset contains one row per public post. Export the dataset using Apify's JSON, CSV or Excel options. API/MCP consumers can read the linked SUMMARY record alongside the dataset.
Example output
Illustrative record with fictional identifiers; unavailable source fields stay null:
{
"post_id": "123456789",
"post_url": "https://www.facebook.com/groups/example/posts/123456789/",
"text": "Looking for Python programming study partners.",
"matchedKeywords": ["python programming"],
"matchReason": "literal-phrase",
"searchKeyword": "python programming",
"searchCountry": "us",
"source_type": "group",
"group_name": "Python Study Group",
"textCompleteness": "complete",
"date": null,
"reaction_count": null
}
Run summary
The SUMMARY record reports each run's search status: SUCCEEDED when targets were reached or the source pagination ended, PARTIAL when searching stopped before every phrase finished (phrases not reached are not-started), and FAILED when an error ended the search. Saved posts stay in the dataset in every case. The run's status message in Apify Console says in plain words how many of the requested posts were saved and, when fewer, why; if your maximum cost per run cannot cover all the requested posts, the message says so as soon as the run starts.
Stop reasons: target-reached means the phrase got all requested posts, source-exhausted means search found no more matching public posts for the phrase (search results ended before the last planned page), planned-searches-completed means every planned search ran without reaching the target, customer-spending-limit means your maximum cost per run was reached, economic-cost-limit means the searches found too few matching posts to continue, source-unavailable and results-unreadable mean search results were temporarily unavailable or unreadable after several attempts. request-limit means one phrase used its page allowance (about four pages per requested post) and the next phrase started; time-limit means the run timeout was reached: raise it in the run options for large requests (the default is 30 minutes). Rejected, excluded, unavailable and out-of-range counts show why candidates were not delivered; groupPostsHiddenFromVisitors counts group posts Facebook shows only to logged-in members. unavailableReasons explains posts that could not be read (for example a post removed from Facebook, or a temporary refusal). When Facebook refuses or empties pages for the run's network address, the Actor rereads them through another address and continues on it (postReadRoute), so a busy address does not cut the results.
Pricing and comparison
One run at the supported 256 MB memory costs $0.029 + $0.00199 × delivered posts, on every Apify tier. There is no result charge for rejected posts or duplicates. The run fee also applies to empty or failed searches. The default maximum cost per run is $1.00, enough for about 490 posts, and the default run timeout is 30 minutes; you can change both in the run options. The minimum supported limit is $0.03099, enough for the start and one result.
| Delivered posts | This Actor, all tiers | Lofomachines Free | Lofomachines Gold/Platinum/Diamond |
|---|---|---|---|
| 0 | $0.02900 | $0.03000 | $0.03000 |
| 1 | $0.03099 | $0.03499 | $0.03299 |
| 10 | $0.04890 | $0.07990 | $0.05990 |
| 100 | $0.22800 | $0.52900 | $0.32900 |
Tariff comparison checked 3 November 2026 against the Lofomachines pricing, assuming one run and one start event for each. These are calculations for the same delivered count. Intermediate Lofomachines tiers fall between the shown prices.
Lofomachines advertises semantic topic relevance; this product verifies literal mentions and exclusions. Choose based on the matching behavior you need.
Which tool fits your search?
| Need | This Actor | Lofomachines (documented behavior) |
|---|---|---|
| Literal phrase evidence | matchedKeywords and matchReason explain every saved match | Topic relevance with an estimated probability |
| Meaning and synonyms | List each phrase explicitly | Semantic matching advertised |
| Exclude unwanted phrases | Global literal exclusions, applied before saving | An exclusion input is not documented in the reviewed listing |
| Access | Public, anonymously readable group posts | Public posts without login or cookies |
| Dates | Presets, UTC start dates and relative day counts | Presets plus custom API dates advertised |
| Price | $0.029/run + $1.99/1,000 delivered posts | $0.03/run + $2.99–$4.99/1,000 results, depending on tier |
Comparison checked 3 November 2026 against the Lofomachines listing. Their column describes their published claims.
FAQ
Does it use AI? No. Inclusion and exclusion use deterministic matching against available public post text. No AI account or enrichment service is required.
Which posts does it search? Posts readable without login, found through public discovery: public group posts with searchScope: "groups", plus pages, public profiles, reels and videos with "all".
Why are some group posts missing? Facebook shows many group posts only to logged-in members. They cannot be read without an account, so they are not saved and not charged. The summary and status message report how many were found but hidden.
Why is group_name empty on some rows? Those posts were published by a page or a profile, not in a group; source_type says which.
Can I sort the posts by date? Yes. Sort by the date field after export.
What happens to results when a run stops? Saved results stay in the dataset and are not billed twice; a restarted run does not repeat work. A new run is separate and can find overlapping posts.
Ready-to-run examples
Use these inputs to try a small sample. Set a maximum run charge of $0.10; the start fee and delivered posts determine the actual charge.
| Example | Input | Expected maximum |
|---|---|---|
| Sourdough mentions | keywords: ["sourdough"], afterDate: "anytime", countryCode: "us", maxPosts: 5 | 5 posts |
| Python this year | keywords: ["python programming"], afterDate: "this_year", countryCode: "us", maxPosts: 3 | 3 posts |
Chinese Simplified
中文说明:Facebook公开群组帖子搜索工具(Facebook Group Post Search 爬虫 / API)
Facebook Group Post Search — Exact Mentions 在可公开发现的Facebook(脸书)群组帖子中,精确搜索你指定的词语和短语,导出匹配帖子的正文、链接、群组和作者信息、发布时间以及可获取的互动数据。可设置排除词过滤无关提及,每条结果都通过 matchedKeywords 说明被收录的原因。无需Facebook账号、无需登录、无需Cookie,也无需AI密钥。
价格:每次运行0.029美元 + 每条匹配帖子0.00199美元(每1,000条1.99美元),平台用量已包含。适合需要Facebook群组监控、品牌提及监测和海外社媒舆情监控的品牌方、出海团队和研究人员。
为什么选择这款Facebook群组帖子搜索工具?
- 精确匹配,结果可核对:只保存正文中包含你所列词语的帖子,
matchedKeywords和matchReason说明每条结果为何被收录,可直接对照原文核实。 - 排除词过滤:帖子包含任一排除词即被剔除,即使同时命中了搜索词,帮你去掉无关提及。
- 不依赖AI:收录和排除均为确定性的文本匹配,不把帖子正文发送给AI分类服务。
- 价格透明:每次运行0.029美元,每条交付的匹配帖子0.00199美元,所有Apify套餐同价;被排除和重复的帖子不收结果费。
- 一次搜索多个短语:最多100个词语或短语,同一帖子在一次运行中只保存一次,并列出它命中的全部短语。
- 运行摘要清楚:
SUMMARY记录说明搜索是否完成,以及候选帖子因排除、日期范围、重复等原因未交付的数量;运行状态消息直接说明保存了多少条帖子、为何少于请求数量。默认每次运行费用上限为1.00美元(约490条帖子),默认运行超时30分钟;若上限不足,运行开始时即会提示。
同等交付量价格对比
2026年11月3日按Lofomachines价格页核对,假设双方均为一次运行、一次启动事件,按相同交付帖子数计算:
| 交付帖子数 | 本工具(所有套餐) | Lofomachines Free | Lofomachines Gold / Platinum / Diamond |
|---|---|---|---|
| 10 | $0.04890 | $0.07990 | $0.05990 |
| 100 | $0.22800 | $0.52900 | $0.32900 |
以上为相同交付数量下的价格计算。Lofomachines主打语义相关性匹配;本工具专注于字面精确匹配和排除词,请按所需的匹配方式选择。
适用场景
- 品牌提及监测:在公开群组帖子中查找品牌名、产品名或地名的字面提及。
- 海外社媒舆情监控:可选择美国、英国、意大利、德国、法国或西班牙搜索市场,发现公开群组中关于品牌或话题的讨论。
- 研究样本采集:收集匹配规则可对照原文核实的帖子样本,用于定性研究。
- 竞品与话题追踪:同时搜索多个短语,并用排除词去掉无关内容。
可以获取哪些数据?
- 帖子:
post_id、post_url、text(可获取的公开正文)、image_url(可获取的帖子图片)。 - 匹配说明:
matchedKeywords、matchReason、searchKeyword。 - 群组:
group_id、group_name、group_url。 - 作者:
author_id、author_name、author_url。 - 时间:
date(可获取时的发布时间)、processed_at(采集时间)。 - 互动数据:采集时的
reaction_count、comment_count、share_count。 - 来源:
source_type:group(群组)、page_or_profile(主页或个人资料)、video(视频)或reel(短视频)。主页和个人发布的帖子不属于任何群组,因此group_name等群组字段为null。 - 其他:
searchCountry(搜索市场)、textCompleteness:complete表示text是Facebook在帖子页面提供的完整正文(长帖同样完整),unavailable表示无法获取正文。
无法获取的字段为 null。数据集可通过Apify导出为JSON、CSV或Excel;通过API或MCP使用时,请同时查看关联的 SUMMARY 记录。
价格
| 计费项 | 价格 |
|---|---|
| 每次运行(支持的256 MB内存) | 0.029美元 |
| 每条交付的匹配帖子 | 0.00199美元(每1,000条1.99美元) |
| 被排除或重复的帖子 | 不收结果费 |
单次运行总价示例:1条帖子0.03099美元;10条0.04890美元;100条0.22800美元。平台用量已包含,所有Apify套餐同价。没有匹配结果或搜索失败时,仍收取运行费。可设置每次运行的最高费用,最低支持0.03099美元(足够支付启动费和一条结果);试用时建议设为0.10美元。
使用方法
- 在 Words or phrases to find(
keywords)中输入一个或多个词语或短语。 - 可选:在 Exclude words or phrases(
excludeKeywords)中输入排除词。 - 设置 每个短语的最大帖子数(
maxPosts),建议先用3条试用。 - 选择 发布时间范围(
afterDate):anytime、last_week(7天)、last_month(30天)、this_year、起始日期如2026-01-01,或相对天数如14 days,日期均为UTC。 - 选择 搜索市场(
countryCode):us、gb、it、de、fr或es。 - 点击 Start,完成后查看 Matching posts 和运行摘要,导出为JSON、CSV或Excel。
{
"keywords": ["pasta madre", "lievito madre"],
"excludeKeywords": ["vendita"],
"afterDate": "anytime",
"countryCode": "it",
"maxPosts": 1
}
搜索范围(searchScope):groups 只搜索公开群组中的帖子;all 同时搜索主页、公开个人资料、短视频和视频。多个短语会同时搜索,长关键词列表(包括多种语言)能在同一运行时限内更快完成。
群组帖子与Facebook可见性:即使群组名称公开,Facebook也常常只向已登录的成员显示群组帖子,未登录访客看到的是该群组的其他帖子。本工具以访客身份读取,因此只保存Facebook公开显示正文的群组帖子,其余帖子任何免登录工具都无法采集,也不会收费。运行摘要中的 groupPostsRead 和 groupPostsHiddenFromVisitors 分别统计可读和被隐藏的群组帖子数量,groups 模式下运行状态消息也会直接说明。如果Facebook拒绝或返回空白页面,工具会通过其他网络地址重新读取并继续使用该地址(postReadRoute),unavailableReasons 说明无法读取的原因。非常具体的短语(例如疾病名加城市名)往往几乎没有公开群组帖子;如需更广覆盖,请添加更短的短语或使用 all。
匹配规则:不区分大小写,并统一Unicode和空格;按完整词匹配,例如 apple 不会匹配 pineapple 中的字母。工具按字面匹配,不做同义词扩展:如需搜索同一概念的不同说法(例如 pasta madre 和 lievito naturale),请分别列出每个短语。
常见问题
需要Facebook账号、Cookie或AI密钥吗? 不需要。工具读取可匿名访问的公开群组帖子,匹配过程不使用AI。
可以按日期排序吗?
可以,导出后按 date 字段排序。
一条帖子命中多个短语会重复收费吗?
不会。每条帖子在一次运行中只保存并计费一次,matchedKeywords 列出它命中的全部短语。
能通过API调用吗?
可以。通过Apify API以上述JSON作为输入运行,结果保存在数据集中,并可读取 SUMMARY 记录。
中文说明会翻译采集到的数据吗? 不会。中文说明只是使用文档;采集到的数据保持来源的原始语言(帖子正文按发布时的原文呈现)。
其他工具
- 哔哩哔哩(B站)数据采集工具:采集B站公开视频、UP主资料和评论。
- Telegram关键词搜索工具:按关键词或品牌搜索公开Telegram帖子,追踪品牌提及。
- Telegram频道采集工具:导出公开Telegram频道的历史帖子。
- Lemon8帖子与评论采集工具:按主页、关键词或话题采集Lemon8帖子、评论和回复。
- Likee视频采集工具:采集Likee视频、评论、创作者资料和话题。
- TikTok广告库采集工具:按品牌或关键词导出TikTok广告库中的公开广告及定向数据。
以上均为独立工具,本工具不会调用它们。
Chinese Traditional
中文說明(繁體):Facebook公開社團貼文搜尋工具(Facebook Group Post Search 爬蟲 / API)
Facebook Group Post Search — Exact Mentions 在可公開找到的Facebook社團貼文中,精確搜尋你指定的字詞與片語,匯出符合貼文的內文、連結、社團與作者資訊、發布時間及可取得的互動數據。可設定排除字詞,每筆結果都以 matchedKeywords 說明收錄原因。不需要Facebook帳號、不必登入,也不需Cookie或AI金鑰。
為什麼選擇這款Facebook社團貼文爬蟲?
- 精確比對、可核對:只保存內文包含你所列字詞的貼文,
matchedKeywords與matchReason說明收錄原因。 - 排除字詞:貼文含任一排除字詞即剔除,去掉無關提及。
- 不使用AI:收錄與排除都是確定性的文字比對。
- 費用透明:所有Apify方案同價,被排除與重複的貼文不收結果費。
- 執行狀態一看就懂:狀態訊息直接說明保存了幾則貼文、為何少於要求數量。預設每次執行費用上限為1.00美元(約490則貼文),預設執行逾時30分鐘;上限不足時執行一開始就會提示。
適用場景
- 品牌提及監測:在公開社團貼文中找出品牌、產品或地名的字面提及。
- 海外社群輿情:可選擇美國、英國、義大利、德國、法國或西班牙搜尋市場。
- 研究樣本:收集比對規則可對照原文核實的貼文樣本。
使用方法
- 在 Words or phrases to find(
keywords)輸入一個或多個字詞或片語;選填 Exclude words or phrases(excludeKeywords)。 - 設定每個片語的最大貼文數(
maxPosts,建議先用3則)、發布時間範圍(afterDate)與搜尋市場(countryCode)。 - 點擊 Start,完成後匯出JSON、CSV或Excel。
搜尋範圍(searchScope):groups 只搜尋公開社團貼文;all 另外包含粉絲專頁、公開個人檔案、短影片與影片。多個片語會同時搜尋,長關鍵字清單能在同一執行時限內更快完成。
社團貼文與Facebook可見性:即使社團名稱公開,Facebook也常只讓已登入的成員看到社團貼文,未登入訪客看到的是該社團的其他貼文。本工具以訪客身分讀取,因此只保存Facebook公開顯示內文的社團貼文,其餘貼文任何免登入工具都無法擷取,也不收費。執行摘要以 groupPostsRead 與 groupPostsHiddenFromVisitors 列出可讀與被隱藏的數量;若Facebook拒絕或回傳空白頁面,工具會改由其他網路位址重新讀取(postReadRoute),unavailableReasons 說明無法讀取的原因。
欄位說明:textCompleteness 為 complete 時,text 是貼文頁面提供的完整內文;source_type 標示來源(group、page_or_profile、video、reel),粉絲專頁或個人發布的貼文沒有社團,group_name 為 null。
{
"keywords": ["pasta madre", "lievito madre"],
"excludeKeywords": ["vendita"],
"afterDate": "anytime",
"countryCode": "it",
"maxPosts": 1
}
價格
每次執行0.029美元 + 每則交付的符合貼文0.00199美元(每1,000則1.99美元),平台用量已包含。沒有符合結果時仍收取執行費。
常見問題
需要Facebook帳號、Cookie或AI金鑰嗎? 不需要。工具讀取可匿名存取的公開社團貼文,比對過程不使用AI。
同一則貼文符合多個片語會重複收費嗎? 不會,每則貼文在一次執行中只保存並計費一次。
中文說明會翻譯擷取到的資料嗎? 不會。說明是中文,資料保留來源的原始語言(貼文內文以發布時的語言呈現)。
More public-source research
For video research, Bilibili Scraper collects Bilibili video, creator and comment data. It is a separate Actor with its own pricing and source coverage.
Actor input Schema
keywords (type: array):
Match any listed phrase in the original public post text. Case-insensitive; no synonyms or semantic interpretation.
excludeKeywords (type: array):
Reject a post if its text contains any listed phrase, even when an inclusion matches.
afterDate (type: string):
Use anytime, last_week (7 days), last_month (30 days), this_year, YYYY-MM-DD or N days (for example 14 days). Dates use UTC; posts without a verifiable date are excluded when filtering.
maxPosts (type: integer):
Maximum number of matching posts to save for each phrase.
countryCode (type: string):
Tunes discovery toward this market. Author location is not filtered.
searchScope (type: string):
Search posts in public groups only, or all public posts including pages, profiles, reels and videos. Facebook shows many group posts only to logged-in members; those cannot be collected and are counted in the run summary.
beforeDate (type: string):
Inclusive UTC date YYYY-MM-DD.
historyDatasetId (type: string):
Optional existing history dataset. Known posts are reread and new observations appended each run. Reuse the same dataset to maintain coverage.
Actor input object example
{
"keywords": [
"python programming"
],
"excludeKeywords": [],
"afterDate": "anytime",
"maxPosts": 3,
"countryCode": "us",
"searchScope": "groups"
}
Actor output Schema
posts (type: string):
Unique public posts containing the requested literal phrases after exclusions and date filters. Includes original text, matchedKeywords, matchReason and available author, group and engagement fields. The summary reports per-phrase counts.
summary (type: string):
Counts of saved, rejected, unavailable and out-of-range posts; per-phrase stop reasons. Search status is SUCCEEDED when targets were reached or the source pagination ended, PARTIAL when searching stopped before every phrase finished, and FAILED when an error ended the search. Billing events are recorded by Apify.
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
import { ApifyClient } from 'apify-client';
// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
token: '<YOUR_API_TOKEN>',
});
// Prepare Actor input
const input = {
"keywords": [
"python programming"
],
"maxPosts": 3
};
// Run the Actor and wait for it to finish
const run = await client.actor("monkey.d.scraping/facebook-public-group-mentions").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
from apify_client import ApifyClient
# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")
# Prepare the Actor input
run_input = {
"keywords": ["python programming"],
"maxPosts": 3,
}
# Run the Actor and wait for it to finish
run = client.actor("monkey.d.scraping/facebook-public-group-mentions").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
echo '{
"keywords": [
"python programming"
],
"maxPosts": 3
}' |
apify call monkey.d.scraping/facebook-public-group-mentions --silent --output-dataset
MCP server setup
{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,monkey.d.scraping/facebook-public-group-mentions"
}
}
}
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 <APIFY_API_TOKEN> 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/gQoYhudm0XdRBM0Rm/builds/3rrdp2WUkj36sbZpm/openapi.json