Social Creator Scraper — daily LinkedIn + X discovery of partnership candidates
Every day, find creators posting about your space on LinkedIn + X — filter for 1k+ followers and topic-relevance, enrich with verified emails, save to a deduped partnerships table. Pair with the creator outreach writer to actually pitch them.
The outcomes on their scorecard
LLM-driven topic-relevance gate after profile + recent posts fetch — drops people whose actual content is off-topic even if they surfaced in keyword search.
Multi-vendor email-finder waterfall runs only on candidates that pass the cheap filters. people_email_verifier gates the final write — undeliverable creators don't land in the table.
Same creator on LinkedIn AND X? Merged into one row with both handles tracked. No duplicate outreach.
Filters early, enriches late. The expensive email waterfall only runs on candidates that already passed follower + topic + language gates.
How the work gets done
Creators with audiences in your space are one of the most underused outbound surfaces in B2B. They already explain the problem you solve to your buyers — they just don't know you exist. This agent finds them daily: it searches LinkedIn and X for posts about your topic terms, walks the top-engaging results, fetches profile data + recent posts for each candidate, filters by follower count + topic relevance + language, and runs an email-finder + verifier waterfall on the survivors. New creators land in `social_creators` with `status='new'`, ready for the downstream outreach writer to pitch. The whole motion runs once a day on cheap filters first (dedup, follower count) before any paid email-finder calls. Pair with `social-creator-outreach-writer` for personalized free-account / sponsorship / partnership pitches.
Creators in your space are already explaining your category to your buyers. This agent finds them — daily scrape across LinkedIn + X by topic, with cheap filters first (dedup, followers) and expensive ones last (email verification). Output is a deduped table of partnership candidates ready for the downstream outreach agent.
Your new teammate
Social Creator Scraper
Daily scheduled agent that searches LinkedIn + X for creators posting about my topics, filters for meaningful audiences and topic-relevance, enriches with verified emails, and writes new creators to social_creators. Pairs with the social-creator-outreach-writer blueprint downstream.
What it runs on
This hire is assembled from the public toolkit. Every piece below is a tool your own agents can call too.
How setup works
- 01
Claim the hire
One click. No questionnaire. The brief is already written from your business, and you can edit it before you build if you want to.
- 02
Your hire deploys itself
Agents, tools, schedules, memory, hand-off queues and the database schema are provisioned into your workspace automatically, then the first real run fires while you watch.
- 03
Hand it the keys it still needs
You land in chat with your hire and its findings. 1 setup tasks — connecting your outreach tools, picking where it reports — are done conversationally, whenever you want.
Other hires that pair well
Outbound Research Analyst
Turn the people writing about your problem on LinkedIn — and the ones quietly liking and commenting on posts about your space, including your competitors' — into a qualified outbound pipeline: scraped daily, enriched with verified email, scored against your ICP, and added to both your LinkedIn outreach (HeyReach) and cold email (Instantly) campaigns — automatically and deduped.
LinkedIn engager scraper for outbound lead capture
Turn the people quietly liking and commenting on LinkedIn posts about your space into a deduped pipeline of warm leads — refreshed every day, no manual scrolling.
X (Twitter) engager scraper for outbound lead capture
Turn the people quietly replying under hot posts in your topic space on X into a deduped pipeline of warm leads — refreshed every day, no doom-scrolling required.
Every hire is assembled from the same toolkit.
Same data sources, same database, same memory, schedules and queues. Point your own agent at the MCP endpoint and wire it your way instead.