# Threads Scraper & Mentions Monitor (`yushi3/threads-mentions-monitor`) Actor

Scrape public Threads posts from profiles and keyword searches without login: text, author, likes, replies, reposts, quotes and media. Monitor mode returns only posts that are new since the last run, with webhook alerts. Pay per post.

- **URL**: https://apify.com/yushi3/threads-mentions-monitor.md
- **Developed by:** [Yushi Homma](https://apify.com/yushi3) (community)
- **Categories:** Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 post scrapeds

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](#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

## Threads Scraper & Mentions Monitor

Scrape public [Threads](https://www.threads.com) posts from profiles and keyword searches, **without logging in**. Each post comes back as a flat row with text, author, likes, replies, reposts, quotes and media. Run it on a schedule with **Only new posts** turned on, and you only get (and pay for) posts that appeared since the previous run, plus a webhook alert for each one.

- **Profiles**: the latest posts of any public account, paginated up to 1,000 posts per profile.
- **Keyword search**: the newest and top-ranked posts mentioning a brand, product or topic.
- **Monitoring built in**: `newSinceLastRun` on every row, an **Only new posts** switch, and webhook alerts for new posts (to Slack, email or a spreadsheet via Zapier, Make or n8n).
- **API and AI agent tool**: fetch a profile's posts in one API call, or let an AI agent call it as a tool through the Apify MCP server.
- **No browser, no cookies, no account**: plain HTTP requests, 256 MB memory.

### Use cases

- Brand and competitor monitoring: get a webhook whenever someone posts about your brand on Threads.
- Track what creators, executives or competitors publish, with engagement numbers for each post.
- Collect posts on a topic for research, sentiment analysis or an LLM pipeline.
- Give an AI agent a "what is @someone posting on Threads?" tool.

### How to use it

1. Add **Profiles** (`zuck`, `@zuck` or `https://www.threads.com/@zuck`) and/or **Search keywords** (`apify`, `web scraping`).
2. Choose **Max posts per profile or keyword** (default 25).
3. For monitoring, turn on **Only new posts**, optionally set an **Alert webhook URL**, and run the Actor on a [schedule](https://docs.apify.com/platform/schedules) (for example hourly). The first run returns everything and becomes the baseline; later runs return only new posts.

Which posts were already seen is stored per profile or keyword in your account's key-value store `threads-mentions-monitor-state`.

### Tutorial: get a Slack message whenever someone mentions your brand on Threads

1. In [Zapier](https://zapier.com), [Make](https://www.make.com) or [n8n](https://n8n.io), create a scenario that starts with a **webhook trigger** ("Catch Hook" in Zapier, "Custom webhook" in Make, "Webhook" node in n8n) and copy its URL.
2. Add a **Slack → Send message** step. Map `item.authorUsername`, `item.text`, `item.likeCount` and `item.url` into the message.
3. In this Actor, add your brand name, product names and common misspellings under **Search keywords** (and your own or competitors' handles under **Profiles**), turn on **Only new posts**, and paste the webhook URL into **Alert webhook URL**.
4. Run it once. That run records the current posts as the baseline and sends no alerts.
5. Open **Schedules** in Apify Console and run the Actor hourly with the same input. Each new mention then becomes one Slack message, and you pay only for new posts.

For sentiment analysis, send the same webhook to an AI step (e.g. OpenAI or Claude in Zapier or Make) before posting to Slack.

### Input

```json
{
  "profiles": ["zuck"],
  "searchQueries": ["apify"],
  "searchSort": "all",
  "maxPostsPerSource": 25,
  "onlyNewPosts": true,
  "alertWebhookUrl": "https://hooks.example.com/threads"
}
```

| Field | Required | Description |
| --- | --- | --- |
| `profiles` | one of these two | Usernames or profile URLs. |
| `searchQueries` | one of these two | Keywords, topics or Threads search URLs. A leading `#` is dropped, because Threads searches topics without it. |
| `searchSort` | no | `all` (default: top-ranked and newest posts merged, newest first), `recent` or `top`. Logged-out Threads returns only a handful of "recent" posts, so `all` gives the best coverage. |
| `maxPostsPerSource` | no | 1 to 1,000 posts per profile or keyword (default 25). |
| `onlyNewPosts` | no | Return only posts not seen in earlier runs (default `false`). |
| `alertWebhookUrl` | no | Receives a POST for every post that is new since the previous run. |
| `proxyConfiguration` | no | Leave empty: Threads is fetched directly, falling back to Apify datacenter and then residential proxies only if Threads rate-limits the run. Set a proxy to use it for every request. |

### Output

One dataset item per post:

```json
{
  "postId": "4006434140014576097",
  "code": "DeZtp-TkQHh",
  "url": "https://www.threads.com/@zuck/post/DeZtp-TkQHh",
  "text": "Introducing Muse Wonder, our new family of frontier models…",
  "createdAt": "2026-10-12T16:56:29.000Z",
  "authorUsername": "zuck",
  "authorFullName": "Mark Zuckerberg",
  "authorVerified": true,
  "authorProfilePicUrl": "https://scontent.cdninstagram.com/…",
  "likeCount": 2121,
  "replyCount": 556,
  "repostCount": 168,
  "quoteCount": 60,
  "isReply": false,
  "mediaUrls": ["https://scontent.cdninstagram.com/…"],
  "source": "profile:zuck",
  "newSinceLastRun": false,
  "scrapedAt": "2026-10-25T13:21:14.020Z"
}
```

The webhook body is `{ "actor": "threads-mentions-monitor", "item": { ...same fields... }, "detectedAt": "<ISO time>" }`.

### API and AI agents

Run it and get the results in one call:

```bash
curl -X POST "https://api.apify.com/v2/acts/yushi3~threads-mentions-monitor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer <APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"profiles": ["zuck"]}'
```

It returns the dataset items as a JSON array. AI agents can call the Actor as a tool through the [Apify MCP server](https://mcp.apify.com).

### Pricing

| Event | Price |
| --- | --- |
| Post returned | $0.0018 |
| New-post alert delivered to your webhook | $0.002 |

With **Only new posts** on, posts you already received are neither returned nor charged, so an hourly brand monitor costs only for genuinely new mentions. Nothing is charged for a profile or keyword that fails; failed webhook deliveries are not billed either.

### Limitations

- Only public data visible to a logged-out visitor. Private profiles, followers lists and likes lists are not available.
- Threads returns about 30 posts per keyword search; for more coverage, add related keywords.
- Replies are included only when they appear in a profile's posts (for example an author continuing their own thread); other people's replies to a post are not collected.
- Like counts are `null` when the author hides them.
- A username that doesn't exist (or isn't public) is reported in `FAILED_TARGETS` as not found and is not billed.

### When a profile or keyword fails

Every profile and keyword is processed even if one fails. Failures are listed in the run's key-value store under `FAILED_TARGETS` with the reason, such as a missing profile or a Threads rate limit. The run fails outright only when Threads changed its page format in a way the Actor can no longer read (it is re-tested against the live site every 12 hours) or when every source failed.

### Questions and issues

Open an issue on the Actor's **Issues** tab.

# Actor input Schema

## `profiles` (type: `array`):

Threads usernames (zuck or @zuck) or profile URLs (https://www.threads.com/@zuck). Returns each profile's latest posts.

## `searchQueries` (type: `array`):

Keywords, topics or brand names to search on Threads (a leading # is dropped, since Threads searches topics without it), or Threads search URLs. Threads returns at most about 30 posts per keyword.

## `searchSort` (type: `string`):

All (default) merges the posts Threads ranks highest with the newest posts, newest first, which gives the best coverage for monitoring. Recent returns only the newest posts, top only the highest-ranked.

## `maxPostsPerSource` (type: `integer`):

Stop after this many posts for each profile or keyword.

## `onlyNewPosts` (type: `boolean`):

Return (and charge for) only posts not seen in earlier runs of this actor for the same profile or keyword. The first run returns everything and becomes the baseline. Turn on for scheduled monitoring.

## `alertWebhookUrl` (type: `string`):

Optional. Receives a POST with each post that appeared since the previous run.

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

Optional. By default Threads is fetched directly and only falls back to Apify datacenter, then residential proxies when it rate-limits the run. Set a proxy here to use it for every request instead.

## Actor input object example

```json
{
  "profiles": [
    "https://www.threads.com/@zuck"
  ],
  "searchQueries": [
    "https://www.threads.com/search?q=openai"
  ],
  "searchSort": "all",
  "maxPostsPerSource": 30,
  "onlyNewPosts": false
}
```

# Actor output Schema

## `results` (type: `string`):

One item per Threads post: text, author, engagement counts, media URLs and whether it is new since the previous run.

# 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 = {
    "profiles": [
        "https://www.threads.com/@zuck"
    ],
    "searchQueries": [
        "https://www.threads.com/search?q=openai"
    ],
    "maxPostsPerSource": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("yushi3/threads-mentions-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 = {
    "profiles": ["https://www.threads.com/@zuck"],
    "searchQueries": ["https://www.threads.com/search?q=openai"],
    "maxPostsPerSource": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("yushi3/threads-mentions-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 '{
  "profiles": [
    "https://www.threads.com/@zuck"
  ],
  "searchQueries": [
    "https://www.threads.com/search?q=openai"
  ],
  "maxPostsPerSource": 30
}' |
apify call yushi3/threads-mentions-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,yushi3/threads-mentions-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/2ayRVJ8fJwDIYyj8r/builds/dYki9w4EhgSavKs5I/openapi.json