Threads Monitor: Public Post Changes avatar

Threads Monitor: Public Post Changes

Pricing

from $1.31 / 1,000 post changes

Go to Apify Store
Threads Monitor: Public Post Changes

Threads Monitor: Public Post Changes

Monitor public Threads profiles and post URLs for new or changed post records. Emit compact change-only datasets by default and keep reusable monitoring state for schedules and automations.

Pricing

from $1.31 / 1,000 post changes

Rating

0.0

(0)

Developer

GetAScraper

GetAScraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

🧡 Threads Monitor: Public Post Changes

Monitor exact public pages
Track chosen Threads profiles and posts without broad search.
Receive useful changes
Get new and changed records by default.
Keep scheduled history
Reuse a state key to compare each run with the last one.
Send data anywhere
Use Apify schedules, webhooks, exports, and integrations.

πŸ” What does Threads Monitor do?

Threads Monitor checks specific public Threads profile and post URLs. It returns structured public post records and labels each one as new, changed, or unchanged.

By default, unchanged posts stay out of the dataset. This keeps scheduled alerts and downstream workflows focused on real changes.

Use it for brand mention review, creator tracking, public statement monitoring, research, or an internal watchlist. This v1 accepts direct URLs only. It does not offer broad keyword search.

🎯 Why use it?

  • Communications teams can watch selected public accounts for new statements.
  • Researchers can build a dated record from the moment monitoring starts.
  • Automation builders can send only new or changed posts into another workflow.
  • Analysts can see mentioned public accounts alongside the surrounding post text.

βš™οΈ How it works

1. Add URLs
Paste public Threads profile or post links.
2. Choose a limit
Keep the default five posts or set a bounded run size.
3. Run or schedule
Reuse the same state key to receive later changes.

πŸ“₯ Input

FieldTypeRequiredDescription
targetUrlsarray of URLsYesDirect public Threads profile or post URLs. Up to 20 targets per run.
maxItemsintegerNoMaximum unique post records inspected across all targets. Defaults to 5 and is capped at 100.
includeUnchangedbooleanNoIncludes unchanged records when enabled. Defaults to false.
stateKeystringNoSelects the saved comparison history. Reuse it for the same monitor.
proxyConfigurationobjectNoOptional connection settings. Direct access is the default.

Example input:

{
"targetUrls": [{ "url": "https://www.threads.com/@zuck" }],
"maxItems": 5,
"includeUnchanged": false,
"stateKey": "executive-watch"
}

πŸ“€ Output

The first successful check labels discovered records as new. Later checks compare each canonical post URL and its public content with saved state. A changed content identifier produces changed; an identical one produces unchanged.

You can download the dataset as JSON, CSV, Excel, XML, or HTML. A simplified record from a public Threads page looks like this:

{
"postUrl": "https://www.threads.com/@zuck/post/DZpPDXbCeTt",
"profileUrl": "https://www.threads.com/@zuck",
"authorUsername": "zuck",
"text": "500M monthly actives on Threads in less than 3 years. Thanks for making this platform what it is. πŸ™",
"publishedAt": "2026-06-16T10:59:56.000Z",
"changeType": "new"
}

🧾 Data table

FieldTypeDescription
targetUrlstringCanonical input URL that produced the record.
postUrlstringCanonical public post URL.
profileUrlstringPublic author profile URL.
authorUsernamestringPublic Threads username.
textstringVisible post text when present.
publishedAtstringSource publication timestamp when available.
imageUrlsarrayPublic post image URLs when present.
videoUrlsarrayPublic post video URLs when present.
mentionsarrayPublic account usernames mentioned in the post.
changeTypestringnew, changed, or unchanged.
fingerprintstringIdentifier for the current public URL and content.
previousFingerprintstringPrevious identifier when a record was already known.
firstSeenAtstringTime this monitor first observed the post.
lastSeenAtstringMost recent successful observation time.
collectedAtstringTime this output record was collected.

Missing source values are omitted. The Actor does not insert placeholder data.

πŸ’° Pricing

Pricing is pay per result. There is no subscription. Runs with no emitted changes create no result charges, though normal platform compute usage can still apply. Keeping includeUnchanged off usually produces the smallest recurring dataset.

⭐ Enjoying Threads Monitor?

Rate this Actor on Apify to help other teams find a focused public Threads monitoring tool.

❓ FAQ

Can it search all Threads posts for a keyword?

No. v1 monitors only the direct public profile and post URLs you provide.

Does it need a Threads login?

No. It reads pages available publicly without authenticated access. Private, deleted, restricted, or login-only content is not collected.

Why is a repeated run empty?

That is expected when nothing changed and includeUnchanged is false. Enable it when you need a full current snapshot.

Does it provide history from before my first run?

It reads currently visible public records. Monitoring history begins when you first use a state key.

Rules vary by country and use case. Review applicable laws, Threads terms, and your obligations before collecting or using data.

πŸ”— Other actors