Read LinkedIn comment threads as a corpus. Start with LinkedIn post or video URLs; each returned comment keeps comment, text, authors, handles, and publication dates.
1
Users / 90d
29
Runs / 30d
—
Rating
Updated 15 Sept 2026
Apify builder
@reapx
Leaderboard position
out of 6,248
New Actors / 90d
#26
Total Actors
#69
Active users / 90d
#417
Total users
#700
Runs / 30d
#490
Total runs
#215
Portfolio stats
New Actors / 90d
196
Total Actors
196
Active users / 90d
221
+138 since first snapshot
Total users
419
Runs / 30d
5.3K
+4.5K since first snapshot
Total runs
406.5K
Portfolio history
Daily publishing
196
Each bar represents one UTC day.
Actor portfolio
196 matching of 196 Actors · page 8 of 9
Read LinkedIn comment threads as a corpus. Start with LinkedIn post or video URLs; each returned comment keeps comment, text, authors, handles, and publication dates.
1
Users / 90d
29
Runs / 30d
—
Rating
Build a lead file from LinkedIn. Start with LinkedIn page URLs; each returned lead keeps handles, names, headlines, roles, and employers.
1
Users / 90d
29
Runs / 30d
Read RedNote comment threads as a corpus. Start with RedNote post or video URLs; each returned comment keeps comment count, titles, last updated at, author identifiers, and author nickname.
1
Users / 90d
18
Runs / 30d
Compare Shopify products, offers, and identifiers. Start with Shopify product URLs; each returned product keeps titles, prices, ratings, review volume, and identifiers.
1
Users / 90d
33
Runs / 30d
Keep Telegram channels, profiles, and visible publishing records together. Start with Telegram URLs; each returned record keeps date, text, authors, channel username, and videos count.
1
Users / 90d
29
Runs / 30d
Read Threads publishing patterns across posts. Start with Threads post URLs; each returned post keeps repost count, post identifiers, text, author handles, and reply count.
1
Users / 90d
32
Runs / 30d
Build a contact file from the open web. Start with web page URLs; each returned contact keeps contact emails, contact sources, phone numbers, site title, and response status.
1
Users / 90d
30
Runs / 30d
Keep YouTube speech as searchable text beside the video that issued it. Preserve segments, timing, language, video identity, title, channel, and source URL for research or publishing work.
1
Users / 90d
30
Runs / 30d
Collect published contact emails from Google Maps. Start with Google Maps page URLs; each returned email record keeps email addresses, names, titles, addresses, and phone numbers.
0
Users / 90d
37
Runs / 30d
Read Indeed reviews as a source-linked corpus. Start with Indeed review or listing URLs; each returned review keeps text, authors, ratings, titles, and review URL.
0
Users / 90d
50
Runs / 30d
Create a comparable file of LinkedIn companies. Keep company identity, industry, size, location, website, description, and source profile together for account research.
0
Users / 90d
29
Runs / 30d
Build a clean file of LinkedIn people from profile URLs, public identifiers, or searches. Keep names, roles, employers, locations, audience size, experience, and education together for prospecting and company research.
0
Users / 90d
33
Runs / 30d
Collect image results and source links from AliExpress. Start with AliExpress image URLs; each returned image keeps product identifiers, position, media type, sku image, and source links.
0
Users / 90d
83
Runs / 30d
Keep Crunchbase companies and market records together. Start with Crunchbase URLs; each returned record keeps titles, authors, names, investments headline, and company financials highlights.
0
Users / 90d
24
Runs / 30d
Compare Etsy products, offers, and identifiers. Start with Etsy product URLs; each returned product keeps titles, prices, ratings, review volume, and original price.
0
Users / 90d
20
Runs / 30d
Build a lead file from Google Maps. Start with Google Maps page URLs; each returned lead keeps names, titles, addresses, phone numbers, and email addresses.
0
Users / 90d
22
Runs / 30d
Keep Google coverage in a source-linked news file. Start with Google news result URLs; each returned news result keeps titles, authors, source links, article identifiers, and publication dates.
0
Users / 90d
29
Runs / 30d
Follow Indeed search results for a role or market. Keep job title, employer, location, summary, salary signals, dates, and application source together for hiring research.
0
Users / 90d
42
Runs / 30d
Read Instagram comment threads without losing the post or author context. Keep comment text, author, date, likes, reply structure, post identity, and source link in one corpus.
0
Users / 90d
31
Runs / 30d
Keep Instagram search results in rows you can compare. Start with Instagram searches or result URLs; each returned search result keeps names, media count, query, media count label, and source links.
0
Users / 90d
29
Runs / 30d
Collect Instagram user records for account research. Start with Instagram user URLs and timeline depth; each returned user keeps handles, titles, user identifiers, authors, and descriptions.
0
Users / 90d
27
Runs / 30d
Map company employees from LinkedIn records. Start with LinkedIn employee URLs; each returned employee keeps handles, names, headlines, roles, and employers.
0
Users / 90d
29
Runs / 30d
Follow open roles on LinkedIn by URL and location. Keep the job, employer, function, location, description, and application link in one file for hiring research or market mapping.
0
Users / 90d
31
Runs / 30d
Read Reddit posts as dated community records. Keep title, body, author, score, comments, community, outbound links, and source URL attached to each post.
0
Users / 90d
36
Runs / 30d
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating
—
Rating