Bluesky Keyword Monitor
Pricing
from $0.01 / 1,000 results
Bluesky Keyword Monitor
Monitors Bluesky for your chosen keywords and returns only posts you haven't seen before — perfect for ongoing brand and topic alerts without digging through duplicate results every run.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
ajshe asllani
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Tracks keywords on Bluesky and alerts you only to new posts you haven't seen before — built for ongoing brand and topic monitoring, not one-off scraping.
What it does
Give it a list of keywords (a brand name, product, competitor, or topic). Every time it runs, it:
- Searches Bluesky for each keyword.
- Filters out posts older than your chosen lookback window and, optionally, posts with too few likes.
- Checks each matching post against a running memory of posts it has already shown you.
- Returns only the posts you haven't seen yet.
Run it on a schedule (see below) and point it — or the dataset it produces — at your alerting/notification tool of choice, and you get a running feed of new mentions instead of a pile of duplicates to sift through by hand.
Why "only new posts" matters
A normal keyword scraper returns everything matching your search on every run — so if you run it every hour, you see the same popular posts over and over, and it gets harder to spot what's actually new. This Actor keeps a memory of what it has already shown you, so each run's output is a clean list of genuinely new mentions. That's what makes it usable as a monitoring/alerting tool rather than a one-time export.
Input options
| Field | What it does | Default |
|---|---|---|
| Search terms | Keywords/phrases to watch, searched separately | ["Apify"] |
| Max posts per term | How many recent matches to check, per term, per run | 50 |
| Lookback window (hours) | Ignore posts older than this | 24 |
| Minimum likes | Skip low-engagement posts | 0 |
Example output
Each new post becomes one row in the Actor's dataset:
| postUrl | authorHandle | text | createdAt | likeCount | matchedTerm |
|---|---|---|---|---|---|
| bsky.app/profile/jane.bsky.social/post/abc123 | jane.bsky.social | "Just tried Apify for a scraping project, works great" | 2026-09-13T14:02:00Z | 12 | Apify |
| bsky.app/profile/devtools.bsky.social/post/xyz789 | devtools.bsky.social | "Anyone compared Apify vs writing your own scrapers?" | 2026-09-13T15:41:00Z | 4 | Apify |
(Full rows also include authorDisplayName, repostCount, and
replyCount.)
Suggested schedule
- Brand/reputation monitoring (time-sensitive): every 30–60 minutes, with a lookback window of 1–2 hours.
- General topic tracking (less urgent): every 4–6 hours, with a lookback window of 24 hours.
Keep the lookback window comfortably longer than your run interval — that way, if a single run runs late or fails, you won't miss posts that fell in the gap.
Bluesky login (one-time setup)
Bluesky blocks anonymous searches from cloud servers, so this Actor needs to log in with a real account to read public posts. It only ever reads — it never posts, follows, or likes anything.
- Sign in to bsky.app (create a free account if you don't have one).
- Go to Settings → Privacy and Security → App Passwords.
- Click Add App Password, name it something like "keyword-monitor",
and copy the generated password (looks like
xxxx-xxxx-xxxx-xxxx). - Paste your handle (e.g.
yourname.bsky.social) into the Bluesky handle field, and the app password into Bluesky app password.
Never use your real account password — only an app password, which can be revoked at any time from the same settings page without affecting your normal login.
Notes
- The Actor remembers post IDs across runs so it never shows you the same post twice; that memory is capped at the 5,000 most recently seen posts.