# Threads accounts with a contact e-mail

**Use case:** 

Only Threads accounts that publish a contact e-mail in their bio, found by keyword. Accounts without an e-mail are skipped and not charged. This example looks for marketing agencies and coaches.

## Input

```json
{
  "searchQueries": [
    "marketing agency",
    "business coach"
  ],
  "emailOnly": true,
  "maxPosts": 10,
  "onlyNewSinceLastRun": false,
  "maxConcurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

## Output

```json
{
  "username": {
    "label": "Username"
  },
  "fullName": {
    "label": "Full name"
  },
  "emails": {
    "label": "Emails"
  },
  "phones": {
    "label": "Phones"
  },
  "followerCount": {
    "label": "Follower count"
  },
  "isVerified": {
    "label": "Is verified"
  },
  "biography": {
    "label": "Biography"
  },
  "bioLinks": {
    "label": "Bio links"
  },
  "profileTags": {
    "label": "Profile tags"
  },
  "searchKeyword": {
    "label": "Search keyword"
  },
  "url": {
    "label": "Url",
    "format": "link"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Threads Account Finder - Leads & Contacts by Keyword Actor is ready to run with the inputs already set for "Threads accounts with a contact e-mail". [Sign up or log in](https://console.apify.com/create-task-from-example/bR495nCxIfKaNvdZJ) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Threads accounts with a contact e-mail" task

The Threads Account Finder - Leads & Contacts by Keyword Actor will start running based on the input automatically. You can also change all the input fields, like keywords, only accounts with an e-mail, and more, to match your specific use case.

### 3. Receive the "Threads accounts with a contact e-mail" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as username, full name, emails, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Threads accounts with a contact e-mail" task via API](https://apify.com/alom/threads-lead-finder.md).

## About this Actor

This example demonstrates how to use [Threads Account Finder - Leads & Contacts by Keyword](https://apify.com/alom/threads-lead-finder.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/alom/threads-lead-finder.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/alom/threads-lead-finder.md

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`).