Freelance Job Leads Monitor — LinkedIn
Pricing
from $15.00 / 1,000 results
Freelance Job Leads Monitor — LinkedIn
Watch LinkedIn Jobs for fresh freelance & contract postings in your niche and get only the NEW leads since your last run — with company website and size.
Pricing
from $15.00 / 1,000 results
Rating
0.0
(0)
Developer
David
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Share
Watch LinkedIn Jobs for fresh freelance and contract postings in your niche and get only the new leads since your last run — each one enriched with the company website, LinkedIn page and employee count.
A job posting that says "looking for a freelancer" is the warmest lead that exists: the company has budget, a need, and is actively searching this week. This Actor turns that public signal into a deduplicated lead feed you can plug into a schedule, a Google Sheet, Make, Zapier or Slack.
What it does
- Searches public LinkedIn Jobs for your keywords (e.g.
video editor,brand designer,webflow developer), bounded to a location and a freshness window (last 24h / week / month). - Keeps only postings with a real freelance/contract signal: employment type
ContractorTemporary, or phrases like freelance, independent contractor, contract basis, prestataire in the title or description. (Toggle off to monitor all jobs.) - Remembers every lead it has already seen (per search, in a persistent state store) and outputs only the NEW ones on every later run — schedule it weekly and you get a clean drip of fresh leads, never duplicates.
Why not just use a jobs scraper?
A raw scraper returns the same hundreds of postings every run, mostly full-time roles. This monitor does the lead-gen work on top: freelance-signal filtering, deduplication across runs, company enrichment, and a canonical job URL without tracking parameters.
Input example
{"keywords": ["video editor", "motion designer"],"location": "United States","postedWithin": "week","requireFreelanceSignal": true,"maxJobsPerSearch": 50}
The defaults work as-is: just add your keywords and run.
Output example
One dataset item per new lead:
{"jobId": "4436778469","jobUrl": "https://www.linkedin.com/jobs/view/4436778469","title": "Freelance AI Video Creator","companyName": "The Flex","companyWebsite": "https://theflex.global/","companyLinkedinUrl": "https://www.linkedin.com/company/the-flex","companyEmployeesCount": 49,"location": "Miami, FL","postedAt": "2026-07-03","salary": "","employmentType": "Full-time","seniorityLevel": "Not Applicable","applicantsCount": 25,"applyUrl": "https://theflex.global/careers/ai-video-creator","description": "We are looking for a creative video maker to join on a project basis...","matchedSignals": ["freelance"],"isNewSinceLastRun": true,"isBaseline": false,"firstDetectedAt": "2026-07-06T14:00:00.000Z"}
A SUMMARY record in the run's key-value store gives you the counts: jobs scanned, leads matching signals, new leads, total known.
How to use it as a lead machine
- Run once with your keywords → the first run saves a baseline (also output, flagged
isBaseline: true). - Create a weekly schedule on this Actor with the same input.
- Every week, the dataset contains only postings that appeared since last week — the freshest possible moment to apply or pitch.
- Filter on
applicantsCountlow values to prioritize postings almost nobody has seen yet.
Fair use & data
- Scrapes only the public LinkedIn jobs search (no login, no private data).
- Outputs company-level information only — recruiter/job-poster personal profiles are deliberately excluded.
- Inputs are hard-capped (5 keywords, 200 jobs per keyword) to keep runs bounded and predictable.
FAQ
Does it work outside the US? Yes — location is free text (country, region or city) and the freelance signals include French (prestataire); add your own signal phrases in any language via freelanceSignals.
Can I monitor all new jobs, not just freelance ones? Yes — set requireFreelanceSignal to false and it becomes a general new-job monitor for your keywords.
How do I reset the memory? Set a new monitorId — each ID keeps its own baseline.