# Facebook Keyword Monitor for Business (`stratasignalsystems/facebook-keyword-monitor`) Actor

Monitor public Facebook posts for your keywords on a schedule. Only new posts, no duplicates across keywords, no Facebook account needed. Unofficial.

- **URL**: https://apify.com/stratasignalsystems/facebook-keyword-monitor.md
- **Developed by:** [stratasignalsystems.com](https://apify.com/stratasignalsystems) (community)
- **Categories:** Social media, News
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 posts

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Keyword Monitor for Business

**Watch public Facebook posts for the keywords your business cares about, on a schedule, and pay only for posts you haven't seen.** No Facebook account, cookies or proxy setup on your side.

Add your keywords, turn on **Only posts I haven't received**, and schedule it. Each run returns just what's new, with text, author, time, links, media and engagement counts.

### Who it's for

- **Communications and PR teams:** catch mentions of your brand, products and executives.
- **Security and risk teams:** watch for public reports about your sites, events and industry.
- **Market researchers:** follow competitors and topics over time.
- **Developers:** feed new posts into your own systems through the Apify API or webhooks.

### Built for monitoring

- **Only new posts:** memory is kept for each keyword between runs, so you aren't charged twice for the same post.
- **No duplicates across keywords:** a post found by several keywords is returned, and charged, once in a run.
- **Handles rate limits:** when Facebook limits a connection, the run retries on a new one through datacenter proxies.
- **Many keywords in one run:** searches run in parallel.
- **Clear reporting:** the `OUTPUT` record shows posts, errors and connection attempts for every keyword.

### Quick start

```json
{
  "keywords": ["your brand", "your product name", "power outage"],
  "only_new": true,
  "since": "1d",
  "results_limit": 25
}
```

**To monitor on a schedule:**

1. Add your keywords and turn on **Only posts I haven't received**.
2. Save it as a task and click **Schedule**, for example hourly.
3. Connect the results with a webhook or integration, or download them.

For several separate lists, give each a **Monitor name**.

### What you get

```json
{
  "input": "power outage",
  "search_query": "power outage",
  "post_id": "1234567890",
  "create_time": 1793500000000,
  "text": "Example post text",
  "post_url": "https://www.facebook.com/example/posts/1234567890",
  "author_username": "Example Page",
  "author_user_id": "100000000000001",
  "author_profile_url": "https://www.facebook.com/example",
  "image_list": ["https://example.com/photo.jpg"],
  "video_list": [],
  "type": "photo",
  "like_count": 12,
  "comment_count": 3,
  "share_count": 1
}
```

### What it costs

You pay **$10 per 1,000 posts** and **$0.0005 per run**, plus Apify platform usage for compute, storage and proxy.

| Example | Posts | Event charges |
|---|---|---|
| One-off: 10 keywords, 25 posts each | 250 | About $2.50 |
| Hourly check that finds nothing new | 0 | $0.0005 per run |
| Monitor collecting 100 new posts a day | 3,000 a month | About $30 a month |

Set a maximum charge per run in Apify if you want a firm limit. The run stops cleanly when it's reached.

### Good to know

- **Search results, not a complete feed:** Facebook decides what its public search returns, and results aren't strictly newest first.
- **Some phrases return nothing:** Facebook blanks some exact phrases. The monitor can try reworded versions, and `search_query` shows what was sent.
- **Rate limits vary:** runs can take longer when Facebook is limiting connections, and a keyword can fail if every attempt is limited.
- **No service guarantee:** this is a self-serve tool, and it can break when Facebook changes.

### Terms and responsible use

This is an unofficial tool, not affiliated with or endorsed by Meta or Facebook. **You are responsible for your use of the data**, including under Meta's terms, copyright and privacy law. Posts can contain personal data.

# Actor input Schema

## `keyword` (type: `string`):

One search phrase. Use Keywords for several.

## `keywords` (type: `array`):

Search phrases, one per line. A single run handles many keywords in parallel, which is much cheaper than one run per keyword.

## `only_new` (type: `boolean`):

Remembers delivered posts for each keyword between your runs, so scheduled runs return, and charge for, only what is new.

## `monitor_name` (type: `string`):

With only new posts on, separate monitors keep separate memory. Leave empty if you run just one.

## `results_limit` (type: `integer`):

Maximum distinct posts kept per keyword. A page holds about 10.

## `since` (type: `string`):

Only keep posts newer than this: 30m, 6h, 1d or 1w. Leave empty for no age cutoff (results are then relevance-ranked and can be months old).

## `filter_by_recent_posts` (type: `boolean`):

Ask Facebook for recent posts. Combined with the age cutoff this gives the freshest results.

## `rewrite_blocked_phrases` (type: `boolean`):

Facebook returns nothing for some exact phrases, such as 'plane crash' or 'bomb threat'. When on, those are searched as reworded variants ('aircraft crash', 'threat bomb') that still return matching posts.

## `max_pages` (type: `integer`):

Upper bound on requests per keyword (per rewrite variant).

## `concurrency` (type: `integer`):

Keywords searched at the same time.

## `sessions` (type: `integer`):

Separate anonymous browsing sessions. Raise only if you see errors at high concurrency.

## `min_wait_time_in_sec` (type: `integer`):

Random pause between pages of one keyword, lower bound.

## `max_wait_time_in_sec` (type: `integer`):

Random pause between pages of one keyword, upper bound.

## `proxyConfiguration` (type: `object`):

Used only when Facebook rate limits a run's direct connection, for the keywords still left. Runs that are not limited send nothing through it. Datacenter proxies only; residential is not used.

## `active_until` (type: `string`):

Optional ISO timestamp (UTC), such as 2026-12-31T00:00:00Z. Runs started after it exit immediately without searching, so a schedule can't keep spending after an end date.

## Actor input object example

```json
{
  "keywords": [
    "wildfire evacuation",
    "power outage"
  ],
  "only_new": false,
  "results_limit": 25,
  "since": "1d",
  "filter_by_recent_posts": true,
  "rewrite_blocked_phrases": true,
  "max_pages": 4,
  "concurrency": 8,
  "sessions": 1,
  "min_wait_time_in_sec": 0,
  "max_wait_time_in_sec": 1,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `posts` (type: `string`):

One item per post: keyword, post id, time (epoch ms), text, link, author, media and reaction, comment and share counts.

## `summary` (type: `string`):

Totals for the run and, per keyword, posts kept, pages fetched, posts dropped as older than the cutoff, and errors.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "wildfire evacuation",
        "power outage"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("stratasignalsystems/facebook-keyword-monitor").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "keywords": [
        "wildfire evacuation",
        "power outage",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("stratasignalsystems/facebook-keyword-monitor").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 '{
  "keywords": [
    "wildfire evacuation",
    "power outage"
  ]
}' |
apify call stratasignalsystems/facebook-keyword-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,stratasignalsystems/facebook-keyword-monitor"
        }
    }
}
```

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/qC1SMpsYPS4YomfzX/builds/PZaLYVrdtfCPKrUas/openapi.json