# Instagram Profile Finder (`scrapecraze/instagram-profile-finder`) Actor Instagram Profile Finder helps you discover and identify relevant Instagram profiles based on keywords, names, brands, niches, or topics. Ideal for influencer research, lead generation, competitor analysis, audience discovery, and social media marketing campaigns. - **URL**: https://apify.com/scrapecraze/instagram-profile-finder.md - **Developed by:** [ScrapeCraze](https://apify.com/scrapecraze) (community) - **Categories:** Lead generation, Social media, Other - **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $4.99 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### Instagram Profile Finder 🎯 Trying to find the right Instagram accounts for outreach or research one-by-one is painfully slow. **Instagram Profile Finder** helps you discover Instagram profiles fast using niche keywords—no login required. If you’re searching for an Instagram profile finder, looking up Instagram accounts by name, or trying to find Instagram profile leads in a specific region, this is built for you. It’s a strong fit for marketers, data analysts, and researchers who need bulk profile discovery in a single run. In practice, you can collect up to thousands of candidate profiles across multiple keywords, while keeping the run streamlined and export-ready. --- ### See the Data: Sample Output Here's a real record from a single run: ```json { "keyword": "marketing", "full_name": "Jane Marketing Studio", "biography": "📈 Growth tips for modern brands | DM for collaborations", "followers": 48210, "following": 615, "post_count": 340, "external_url": "https://janemarketingstudio.example", "profile_pic_url": "https://instagram.com/static/images/avatars/default_avatar_2021.png", "source": "Search Engine", "url": "https://www.instagram.com/janemarketingstudio/" } ```` | Field | Type | What It Tells You | |---|---|---| | `keyword` | string | Which keyword triggered this profile to be collected—useful for filtering and reporting. | | `full_name` | string | The profile’s display name, so you can quickly assess relevance. | | `biography` | string | The public bio text—great for qualitative screening and keyword match context. | | `followers` | number | A quick audience-size signal for prioritizing outreach. | | `following` | number | Helps you gauge profile behavior and audience style. | | `post_count` | number | A rough engagement/active-ness proxy (how many posts they’ve published). | | `external_url` | string | Their link-in-bio destination (often where you can verify business intent). | | `profile_pic_url` | string | Direct image URL for thumbnailing or enrichment workflows. | | `source` | string | Indicates where the profile was sourced from (returned as `Search Engine`). | | `url` | string | The Instagram profile URL you can open or import into your CRM. | | `collected_at` | string | Timestamp when the record was collected (ISO 8601). | | `status` | string | This field is not present in the dataset transformation defined in the actor manifest; check your results for any run-level failures/errors in Apify logs. | | `error_message` | string | This field is not present in the dataset transformation defined in the actor manifest; review actor logs if enrichment fails for specific profiles. | Export your full dataset as JSON, CSV, or Excel from the Apify dashboard. *** ### Setting It Up Drop this into your `input.json` and you're ready to go: ```json { "keywords": ["marketing", "fitness"], "country": "United States", "max_leads": 100 } ``` | Parameter | Required | What It Does | |---|---|---| | `keywords` | ✅ | A list of niche keywords to search for relevant Instagram profiles. | | `country` | ⬜ | Select the target country for lead discovery (used to guide location filtering). | | `max_leads` | ⬜ | Maximum number of leads to collect in the run (Default: 10). | *** ### What It Does Instagram Profile Finder discovers Instagram profiles based on your keyword list, filters results by country, and writes structured profile data into your Apify dataset. It works without requiring an Instagram login and focuses on producing clean, integration-ready records. #### Keyword-driven profile discovery at scale You provide `keywords`, and the actor processes them one by one, collecting profile results as it goes. This makes it a practical Instagram account search tool for campaigns, lead lists, and research briefs. #### Country-focused lead collection Using your `country` input, the actor filters discovery toward your target region. That helps you avoid one-size-fits-all lead lists when you need an Instagram profile finder that’s region-aware. #### Clean output, ready for analysis Each collected record is shaped into consistent fields such as `full_name`, `biography`, `followers`, `following`, `post_count`, `external_url`, `profile_pic_url`, `source`, and `url`. The dataset is preconfigured to display these fields in a table view for fast review. #### Profile enrichment for usable leads After candidate profile URLs are collected, the actor enriches each profile and merges the enriched details into the dataset record. This is especially helpful when you’re doing lead qualification or building an Instagram profile tracker dataset. #### Includes resilience for real-world runs The actor includes retry logic (`max_retries`) and request pacing (`request_delay`) to improve run stability. If enrichment fails for a specific profile, it skips that profile and continues collecting others. Overall, Instagram Profile Finder turns keyword intent into a structured list of Instagram profiles you can export and use immediately. *** ### Why Instagram Profile Finder? There are plenty of ways to pull data from Instagram account listings—here’s why **Instagram Profile Finder** stands out. #### Built for fast, bulk discovery Instead of manual searching, Instagram Profile Finder uses your `keywords` to discover multiple relevant profiles in one run. This is ideal when you need an Instagram profile lookup process that doesn’t consume hours. #### Focused on usable lead fields The output includes practical profile metadata like `followers`, `following`, `post_count`, `external_url`, and `profile_pic_url`. That makes it easier to rank leads without having to open every profile page. #### No-login workflow with clean exports You don’t need to log into Instagram to run it, and the results are written directly into the Apify dataset. That means you can take your Instagram username finder output straight into analysis, outreach tooling, or CRM import steps. *** ### Real-World Use Cases Here's how different teams put Instagram Profile Finder to work: **Growth Marketers**\ A marketing team needs a fresh list of niche creators for a collaboration test. They run Instagram Profile Finder with keyword themes and a specific `country`, then use `followers` and `biography` to shortlist accounts for outreach. The dataset export becomes their starting point for campaign tracking. **Sales Teams Building Prospect Lists**\ A sales development team wants to find Instagram account search tool leads tied to a regional ICP. They use Instagram Profile Finder to generate candidate profiles, then quickly review `external_url` and bio language to prioritize the most sales-ready accounts. This cuts prospecting time significantly compared to manual profile discovery. **Freelance Researchers & Analysts**\ A researcher studying industry presence needs structured Instagram profile data across multiple niches. They run Instagram Profile Finder with several `keywords`, then analyze `post_count`, `following`, and bio text for patterns. The result is an Instagram account locator dataset that’s ready for reporting. **Agencies Running Multi-Client Discovery**\ An agency juggling multiple clients can parameterize the run per client: different keywords, different `country`, and different `max_leads` caps for testing. Instagram Profile Finder produces consistent fields per record, so deliverables stay standardized. This makes it easier to compare results across campaigns. **Automation & Data Engineers**\ A developer triggers Instagram Profile Finder as part of an enrichment pipeline and stores the dataset for downstream scoring. Because records include stable identifiers like `url` and enrichment fields like `user_id`, the pipeline can join results with other data sources reliably. The API-driven workflow supports ongoing Instagram profile tracker updates. *** ### How to Run It No code required. Here's how to get your first results in under 5 minutes: 1. **Open the actor page on Apify**\ Go to the actor listing on Apify and open it in the Apify Console: https://console.apify.com. 2. **Enter your inputs**\ Provide `keywords` (required). Optionally set `country` and `max_leads` in the Input Parameters panel. 3. **Configure proxy settings (recommended)**\ If your environment supports it, enable the actor’s proxy support for more reliable scraping behavior. 4. **Start the run**\ Click **Run actor** and monitor the live logs for progress by keyword. 5. **Open the Dataset tab**\ Your Instagram profile discovery results appear in the dataset as the run progresses. 6. **Export your results**\ Use the dataset export options (JSON, CSV, or Excel) to download the final dataset. The whole setup takes under 5 minutes — results start appearing within seconds of launch. *** ### Export & Integration Options Once your data is collected, Instagram Profile Finder fits directly into your existing workflow. You can download your results from the Apify dataset tab in your preferred format (JSON, CSV, or Excel) for use in spreadsheets, BI tools, or outreach ops. If you’re building an ongoing Instagram profile tracker, you can run it on a schedule and refresh lead lists periodically. For programmatic use, you can access actor runs and pull results via the Apify API. If you prefer automation, you can connect the workflow to your tooling using Zapier/Make-style integrations or webhook-driven pipelines (via Apify platform capabilities). *** ### Pricing Instagram Profile Finder runs on Apify, which includes a **free tier**—no credit card needed to start. On the free tier, usage is limited by Apify’s plan rules, while paid plans support heavier workloads for larger keyword sets and higher `max_leads` needs. Pay-as-you-go is handled via Apify compute units (CU), and you only scale when your workload demands it. Start free at [apify.com](https://apify.com) — scale up when you need to. *** ### Reliability & Limitations | What We Handle | How | |---|---| | Country-focused filtering | Uses your `country` input to guide discovery toward your target region. | | Retry logic | Uses `max_retries` to improve resilience when requests fail intermittently. | | Request pacing | Applies `request_delay` behavior to keep the run stable. | | Skipping failed enrichments | If enrichment fails for a profile, it skips that record and continues. | | Run result caps | Uses `max_leads` (with higher caps allowed for paid users). | Limitations: Instagram Profile Finder only works with publicly accessible Instagram profile data, and it may not return complete information for every account. Results can vary depending on how much profile information is available for each username. For enterprise-scale needs or custom configurations, reach out and we’ll help. *** ### Frequently Asked Questions #### Is there a free plan? Yes. Apify offers a free tier that you can use to test Instagram Profile Finder on real keyword inputs and verify output quality before scaling. #### Do I need to log in or create an account on Instagram? No. Instagram Profile Finder is designed to work without logging into Instagram, using publicly available profile data. #### How accurate is the extracted data? The actor returns profile fields it can read and enrich from publicly available sources. Accuracy depends on what’s actually present on each profile (for example, `biography` and `external_url`). #### How many results can I get per run? You control the run size with `max_leads` (Default: 10; Minimum: 1). Additionally, free tier runs are capped according to the actor’s paid vs free behavior. #### How fresh is the data? Data freshness reflects when the actor collected and enriched each profile during your run. If you need updates, run it again using the same `keywords` and `country`. #### Is this legal? Does it comply with GDPR / CCPA? The actor accesses **publicly available data**. It’s still your responsibility to comply with GDPR, CCPA, Instagram’s Terms of Service, and any applicable regulations when collecting, storing, and using the results. #### Can I export to Google Sheets or Excel? Yes. You can export from the Apify dataset tab as JSON, CSV, or Excel, then import into Google Sheets or your spreadsheet tool of choice. #### Can I schedule this to run automatically? Yes. You can schedule Apify actors to run automatically (using Apify scheduling features), which is useful for ongoing Instagram profile tracker workflows. #### Can I access results via the API? Yes. Apify supports programmatic access via the Apify API, so you can fetch results from your runs without manual downloads. #### What happens when the actor encounters an error? The actor uses retry logic (`max_retries`) and continues processing other profiles. If enrichment for a specific profile fails, that profile is skipped and the actor continues until it hits the `max_leads` limit. *** ### Get Help & Use Responsibly Got a question about Instagram Profile Finder or a feature you’d like added? Reach out at and we’ll help—this actor is actively maintained based on user feedback. **publicly available data** only. The actor does not access private accounts, login-gated pages, or password-protected content. You are responsible for GDPR, CCPA, and platform ToS compliance when collecting and using results. For data removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `keywords` (type: `array`): List of niche keywords to search (e.g., 'marketing', 'fitness'). ## `country` (type: `string`): Select the target country for leads. ## `max_leads` (type: `integer`): Maximum number of leads to collect (Default: 100). ## Actor input object example ```json { "keywords": [ "marketing", "fitness" ], "country": "United States", "max_leads": 10 } ``` # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "keywords": [ "marketing", "fitness" ], "country": "United States" }; // Run the Actor and wait for it to finish const run = await client.actor("scrapecraze/instagram-profile-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "keywords": [ "marketing", "fitness", ], "country": "United States", } # Run the Actor and wait for it to finish run = client.actor("scrapecraze/instagram-profile-finder").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "keywords": [ "marketing", "fitness" ], "country": "United States" }' | apify call scrapecraze/instagram-profile-finder --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapecraze/instagram-profile-finder", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Instagram Profile Finder", "description": "Instagram Profile Finder helps you discover and identify relevant Instagram profiles based on keywords, names, brands, niches, or topics. Ideal for influencer research, lead generation, competitor analysis, audience discovery, and social media marketing campaigns.", "version": "1.0", "x-build-id": "jB25Wa5EcUiNfyChu" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapecraze~instagram-profile-finder/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapecraze-instagram-profile-finder", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scrapecraze~instagram-profile-finder/runs": { "post": { "operationId": "runs-sync-scrapecraze-instagram-profile-finder", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scrapecraze~instagram-profile-finder/run-sync": { "post": { "operationId": "run-sync-scrapecraze-instagram-profile-finder", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "keywords" ], "properties": { "keywords": { "title": "Search Keywords", "minItems": 1, "uniqueItems": true, "type": "array", "description": "List of niche keywords to search (e.g., 'marketing', 'fitness').", "items": { "type": "string" } }, "country": { "title": "Target Country", "enum": [ "United States", "United Kingdom", "Canada", "Australia", "Germany", "France", "India", "Japan", "Brazil", "Italy", "Spain", "Netherlands", "Sweden", "Norway", "Denmark", "Finland", "Poland", "Czech Republic", "Hungary", "Romania", "Bulgaria", "Croatia", "Slovenia", "Slovakia", "Estonia", "Latvia", "Lithuania", "Portugal", "Greece", "Cyprus", "Malta", "Luxembourg", "Ireland", "Belgium", "Austria", "Switzerland", "Liechtenstein", "Iceland", "South Korea", "China", "Mexico", "Argentina", "Chile", "Colombia", "Peru", "Venezuela", "Ecuador", "Uruguay", "Paraguay", "Bolivia", "Guyana", "Suriname", "French Guiana", "Falkland Islands (Malvinas)", "South Georgia and the South Sandwich Islands", "Bonaire, Sint Eustatius and Saba", "Curaçao", "Aruba", "Sint Maarten (Dutch part)", "Turks and Caicos Islands", "British Virgin Islands", "Anguilla", "Montserrat", "Antigua and Barbuda", "Barbados", "Dominica", "Grenada", "Saint Kitts and Nevis", "Saint Lucia", "Saint Vincent and the Grenadines", "Trinidad and Tobago", "Jamaica", "Bahamas", "Belize", "Costa Rica", "Guatemala", "Honduras", "Nicaragua", "Panama", "El Salvador", "Cuba", "Dominican Republic", "Haiti", "Puerto Rico", "U.S. Virgin Islands", "American Samoa", "Guam", "Northern Mariana Islands", "Saudi Arabia", "United Arab Emirates", "Bahrain", "Iraq", "Iran, Islamic Republic of", "Israel", "Jordan", "Kuwait", "Lebanon", "Oman", "Qatar", "Syrian Arab Republic", "Yemen", "Afghanistan", "Bangladesh", "Bhutan", "Maldives", "Nepal", "Pakistan", "Sri Lanka", "Myanmar", "Cambodia", "Lao People's Democratic Republic", "Thailand", "Viet Nam", "Malaysia", "Singapore", "Brunei Darussalam", "Philippines", "Indonesia", "Timor-Leste", "Papua New Guinea", "Fiji", "New Zealand", "Solomon Islands", "Vanuatu", "New Caledonia", "French Polynesia", "Wallis and Futuna", "Samoa", "Tonga", "Tuvalu", "Kiribati", "Nauru", "Federated States of Micronesia", "Marshall Islands", "Palau", "Cook Islands", "Niue", "Tokelau" ], "type": "string", "description": "Select the target country for leads.", "default": "United States" }, "max_leads": { "title": "Max Leads", "minimum": 1, "type": "integer", "description": "Maximum number of leads to collect (Default: 100).", "default": 10 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```