# Threads Account Finder - Leads & Contacts by Keyword (`alom/threads-lead-finder`) Actor

Find Threads accounts by keyword: followers, bio, bio links, verification, plus e-mails and phone numbers when people list them in their bio. Optional e-mail-only filter. Look up usernames too. No login needed. From $1.50 per 1,000 accounts.

- **URL**: https://apify.com/alom/threads-lead-finder.md
- **Developed by:** [Alom Dev](https://apify.com/alom) (community)
- **Categories:** Lead generation, Social media
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Threads Account Finder: Leads & Contacts by Keyword

Find **Threads** (threads.com) accounts by keyword and get **one row per account** with the contact details they
show publicly: **e-mails and phone numbers written in the bio, bio links**, username, full name, follower count,
verification, bio text, profile URL and the keyword that found the account. You can also look up usernames you
already have.

- **No login needed.** It reads what a logged-out visitor sees. No account of yours is involved.
- **Only accounts with an e-mail** (optional): accounts without one are skipped and not charged.
- **Up to ~100 accounts per keyword**, each opened for its follower count and bio links.
- **Skip accounts you already have:** give your lead list a name and later runs leave out accounts earlier runs returned.
- Export to CSV, Excel or JSON, or pull results through the Apify API.

This Actor is a focused version of the [Threads Scraper](https://apify.com/alom/threads-scraper) (same code, same
prices). Use the Threads Scraper if you also need posts, replies, reposts or post search.

### What can you use it for?

- **Outreach lists:** coffee shops, real-estate agents, coaches, agencies, creators in a niche, with the e-mail they
  publish for business enquiries.
- **Influencer research:** accounts for a topic with follower counts and verification, ready to sort.
- **Enriching a list you have:** paste usernames and get followers, bio, links and contacts for each.

### Input

| Field | What it does |
|---|---|
| `searchQueries` | Keywords that describe the accounts, e.g. `coffee shop`, `marketing agency`. Threads matches usernames, names and bios. |
| `usernames` | Optional. Usernames or profile URLs (`zuck`, `@mosseri`, `https://www.threads.com/@nasa`). One row each. |
| `emailOnly` | Only return accounts with an e-mail in their bio (the rest are not charged). Default off. |
| `maxPosts` | Max accounts per keyword, 1-100. Default 50. |
| `onlyNewSinceLastRun` + `monitorName` | Skip accounts an earlier run with the same list name returned. |

```json
{ "searchQueries": ["coffee shop", "specialty coffee"], "maxPosts": 100, "emailOnly": true }
```

```json
{ "usernames": ["nasa", "@natgeo", "https://www.threads.com/@nike"] }
```

The field names are the same as in the Threads Scraper, so an input works in both.

### Output example

```json
{
    "type": "profile",
    "username": "examplecoffeeroasters",
    "fullName": "Example Coffee Roasters",
    "userId": "6312345678",
    "biography": "Small-batch roastery in Portland. Wholesale: hello@examplecoffee.com",
    "followerCount": 4821,
    "isVerified": false,
    "isPrivate": false,
    "profilePicUrl": "https://scontent…jpg",
    "bioLinks": [{ "url": "https://examplecoffee.com", "title": null }],
    "emails": ["hello@examplecoffee.com"],
    "phones": [],
    "profileTags": ["Coffee"],
    "followingCount": null,
    "searchKeyword": "coffee shop",
    "url": "https://www.threads.com/@examplecoffeeroasters",
    "source": "accounts:coffee shop",
    "scrapedAt": "2026-10-01T12:00:00.000Z"
}
```

(The account above is made up; the fields are what you get.) `searchKeyword` is `null` for rows from `usernames`.
`emails` and `phones` are empty lists when the bio has none. Values Threads doesn't show are `null`, never `0`.

### How much does it cost?

The same prices as the Threads Scraper, **from $1.50 per 1,000 accounts**, plus $0.005 per run. One result = one
account row. An account row **with an e-mail** costs an extra **$0.01**, because finding one means opening about 50
profiles. Rows without an e-mail never pay that extra.

| Apify plan | Price per 1,000 results |
|---|---|
| Free | $2.50 |
| Starter (Bronze) | $2.00 |
| Scale (Silver) | $1.75 |
| Business (Gold) and above | $1.50 |

Example: 500 accounts on the Free plan, 20 of them with an e-mail, cost 500 x $0.0025 + 20 x $0.01 = $1.45.

You pay only for rows you receive: accounts filtered out by `emailOnly`, duplicates and accounts a named list already
returned are free. Platform usage (compute, proxy) is included.

### Limitations

- **E-mails and phones come only from what people write in their bio.** Many accounts don't write one, so with
  `emailOnly` expect a small fraction of the accounts a keyword finds: in our tests about 2-5% of the accounts had an
  e-mail in their bio (businesses and agencies more often than personal accounts), so a keyword with ~100 matching
  accounts typically gives 1-5 e-mails. The Actor doesn't guess, buy or verify addresses, and it doesn't open the
  websites in bio links.
- Threads' account search returns **up to ~100 accounts per keyword** to logged-out visitors. Use several specific
  keywords for bigger lists (`coffee shop berlin`, `coffee roaster`, `cafe owner`).
- Phone numbers are recognised when written with spaces, dashes, brackets or a leading `+`.
- An unknown username fails that input only; the rest of the run is delivered.

### FAQ

**Do I need a Threads or Instagram account?** No. Nothing is logged in.

**Is it legal?** It collects data that the account owners made public. You are responsible for how you use it,
including data protection and anti-spam rules (for example GDPR and CAN-SPAM) when you contact people.

**Why fewer rows than `maxPosts` with `emailOnly`?** Only accounts that wrote an e-mail in their bio are returned.
The Actor checks every account the keyword finds before it stops.

### More scrapers from the same developer

- [Threads Scraper](https://apify.com/alom/threads-scraper): posts, profiles, replies, reposts, keyword and hashtag search, account search
- [Google Trends API & Scraper](https://apify.com/alom/google-trends-scraper): interest over time, regions, related queries and Trending Now, a pytrends alternative
- [YouTube Scraper](https://apify.com/alom/youtube-scraper): videos, channels, Shorts, comments, subtitles and community posts without the API quota
- [Bilibili Scraper](https://apify.com/alom/bilibili-scraper): videos, creators, full comment threads and danmaku from B站, no login
- [Google Hotels Scraper](https://apify.com/alom/google-hotels-scraper): hotel prices from every booking site across dates, room rates and reviews
- [Google Ads Transparency Scraper](https://apify.com/alom/google-ads-transparency-scraper): every Google ad a competitor runs, with the real ad copy
- [Threads Hashtag & Keyword Monitor](https://apify.com/alom/threads-keyword-monitor): only the new posts for your keywords and #hashtags, for scheduled runs

### Feedback

Missing a field, found a bug, or need a feature? Open an issue in the **Issues** tab and I'll take a look. If this
Actor saved you time, a short review on the Store page helps other people find it.

# Actor input Schema

## `searchQueries` (type: `array`):

Words that describe the accounts you want, e.g. <code>coffee roaster</code>, <code>real estate agent</code>, <code>marketing agency</code>. Threads' account search matches usernames, names and bios: up to ~100 accounts per keyword.

## `usernames` (type: `array`):

Accounts you already know, e.g. <code>zuck</code>, <code>@mosseri</code> or <code>https://www.threads.com/@nasa</code>. Each returns one row with the same fields.

## `emailOnly` (type: `boolean`):

Return only accounts that wrote an e-mail address in their bio. The others are skipped and <b>not charged</b>. The Actor then checks every account the keyword finds (up to ~100) until it has <i>Max accounts per keyword</i> with an e-mail, so expect fewer rows than without the filter.

## `maxPosts` (type: `integer`):

Threads returns up to ~100 accounts per keyword to logged-out visitors.

## `onlyNewSinceLastRun` (type: `boolean`):

Do not return (or charge for) accounts that an earlier run with the same list name already returned. Useful when you search new keywords for the same campaign. Applies to keyword search.

## `monitorName` (type: `string`):

Keep separate memories for different lead lists (e.g. <code>coffee-campaign</code>). Defaults to <code>default</code>.

## `maxConcurrency` (type: `integer`):

Profiles opened in parallel.

## `proxyConfiguration` (type: `object`):

The default Apify datacenter proxy works and is included in the price. If Threads starts blocking it, the run switches to residential proxies by itself (logged).

## Actor input object example

```json
{
  "searchQueries": [
    "coffee shop",
    "marketing agency"
  ],
  "emailOnly": false,
  "maxPosts": 50,
  "onlyNewSinceLastRun": false,
  "maxConcurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQueries": [
        "coffee shop",
        "marketing agency"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alom/threads-lead-finder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchQueries": [
        "coffee shop",
        "marketing agency",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alom/threads-lead-finder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "coffee shop",
    "marketing agency"
  ]
}' |
apify call alom/threads-lead-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alom/threads-lead-finder"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/vG9bDuFTelQORujCf/builds/UQt8a0Y8VLe8rtcWD/openapi.json