Threads Lead Finder | Public Service Requests (Unofficial)

Find public English-language Threads posts that may indicate a need for a freelancer or agency. Search for web development, Shopify/WordPress, logos and branding, graphic design, marketing/SEO, SaaS/app development, or enter your own service and optional niche.

Every result is a candidate for manual review, not a verified client. This tool is unofficial and is not affiliated with Meta or Threads.

What you get

A simple lead table with: Account, Requirement, Posted (UTC), Post URL, Profile URL, Status, Notes. Open the original post and profile to decide whether a request is relevant. The table is available to export from the run's dataset as JSON, CSV, or Excel.

The tool attempts to remove duplicates and obvious promotional/job-board content. These checks are heuristic; they can wrongly include suspicious posts or exclude real prospects.

How to use

1. Choose Service category (all six services or one).
2. For a service not listed, enter Custom service and optionally comma-separated Related custom terms. Custom service overrides the category choice.
3. Optionally specify a Niche (e.g., dentist, restaurant) and Narrow focus (e.g., landing page). Narrow combinations often return zero leads.
4. Keep Search depth: Quick for a first test. Increase limits only when needed.
5. Run and review results by opening the Post URL and Profile URL. Contact people only where appropriate and without mass unsolicited messaging.

Example input:

{
  "category": "all",
  "depth": "quick",
  "maxQueries": 6,
  "maxAuthors": 10,
  "hours": 24,
  "delaySeconds": 3,
  "previewOnly": false,
  "excludedAccounts": ""
}

Custom service example: set customService to landing page design and customTerms to need a sales page,landing page redesign,looking for landing page designer.

Outputs

• Candidate leads: Default dataset, seven straightforward fields, one item per selected post.
• Run summary: Search coverage and filtering statistics stored in the default key-value store as SUMMARY.
• Search plan: When previewOnly is true, the run stores PLAN instead of scraping posts.

Limits and important notes

• Only publicly accessible posts are considered. Search is not exhaustive, and results depend on source availability. A successful run can return zero records.
• Filtering is heuristic. Neither the post author nor project authenticity, contactability, budget or buying readiness are independently verified.
• The Actor does not contact users, log in to Threads, or retrieve nonpublic user data.
• Search may be unavailable or restricted. Respect website rules and access limits; do not use it to bypass restrictions.
• excludedAccounts must be passed in each cloud input; exclusions in a private local excluded_accounts.txt are not synced.
• Dataset records are independent per run. The service does not store outreach progress between runs; exported Status and Notes are starting fields for the user's own lead sheet.
• Do not use results for spam, unlawful profiling, or collection of sensitive information. Follow privacy, platform and marketing regulations.

Attribution and rights

Built on the MIT-licensed OmkarCloud Threads Scraper. Its copyright notice and LICENSE are retained in the deployed source. The open-source software license does not grant permission to collect, redistribute or sell Threads content. The publisher and users must separately establish necessary authorization and compliance with Meta/Threads terms and applicable law.

Support and maintenance

Public website behavior changes over time. If queries fail, reduce request volume, verify available access and report the reproducible error. Do not aggressively retry blocks. This tool provides no guarantee of continuous availability.