Instagram Creator Email Finder

Instagram Creator Email Finder turns a list of Instagram usernames or profile URLs into lead rows with publicly available emails, profile details, websites, social links and contact evidence. Use this Instagram email finder to enrich a creator shortlist. It does not search for creators by keyword or verify email deliverability.

Use it to qualify influencer lists without manually opening every bio and linked website. With includeNoContact enabled, processed profiles without an email or accessible profile receive a status row. A run deadline can leave later inputs unprocessed. Inspect RUN_SUMMARY for partial coverage.

Quick start

1. Add Instagram usernames or full profile URLs to profiles.
2. Choose how many linked website pages to inspect with maxLinkedPagesPerProfile.
3. Run the Actor and export the dataset as CSV, JSON, Excel, XML, or through the API.

Start with a small input:

{"profiles":["natgeo"],"maxLinkedPagesPerProfile":0,"includeNoContact":true}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

Every dataset row can include the username, full name, biography, profile URL, avatar, follower and following counts, post count, verification and privacy flags, category, public business email, public phone number, linked website, additional emails, social links, source URLs, confidence, status, and collection time. Optional values remain nullable when the public profile does not expose them.

Who is it for?

• Creator-partnership teams reviewing known account shortlists before outreach.
• Agencies collecting public contact evidence and profile context for manual qualification.
• Brand researchers comparing available public creator categories and audience sizes.
• Sales-operations and data teams importing source-linked lead records with explicit coverage statuses.

How you can use the data

• Qualify a profile-only roster. Use the existing natgeo/nasa recipe with zero linked pages and no-contact rows enabled. Keep username, profile URL, available audience fields and status together, without assuming every profile supplies an email.
• Inspect bounded public contact evidence. Use the existing natgeo profile URL with three linked pages. Retain emails, contactSourceUrls and contactConfidence so someone can open the evidence before attributing an address. A linked agency or shop address is not automatically the creator's personal email.
• Reconcile a processed shortlist. Keep found, no_public_contact and profile_unavailable outcomes alongside summary counts. No-contact rows preserve processed-profile coverage, while later inputs may remain unprocessed at the shared deadline. Missing contacts do not prove that none exist.
• Compare your own later checks. Retain collectedAt and normalized usernames when joining exports in your CRM or spreadsheet. The Actor does not discover creators by keyword or verify email deliverability, and the confidence field describes where evidence was found rather than whether an address accepts mail.

Input settings

Setting	JSON key	Description
Instagram usernames or profile URLs	profiles	Add 1–100 public Instagram usernames such as natgeo or full profile URLs.
Maximum linked pages per creator	maxLinkedPagesPerProfile	Inspect up to this many public pages on the creator's linked website for emails and social links. Set to 0 for profile-only extraction.
Save profiles without a public email	includeNoContact	Save one truthful status row even when no public email is visible, so outreach lists preserve coverage and profile metadata.
Run time limit in seconds	runTimeSecs	Stop admitting new profiles before this shared run deadline. Use 30–270 seconds.
Proxy configuration	proxyConfiguration	Existing managed or custom proxy settings. See field help for omission and explicit opt-out behavior.

Input recipes

Profile-only qualification:

{"profiles":["natgeo","nasa"],"maxLinkedPagesPerProfile":0,"includeNoContact":true}

Public contact enrichment:

{"profiles":["https://www.instagram.com/natgeo/"],"maxLinkedPagesPerProfile":3,"includeNoContact":true}

Output data

Illustrative shape-only excerpt, not a collected creator record:

{
  "username": "examplecreator",
  "fullName": "Example Creator",
  "primaryEmail": "hello@example.com",
  "businessPhoneNumber": null,
  "externalUrl": "https://example.com",
  "followersCount": 125000,
  "category": "Digital creator",
  "contactConfidence": "profile_declared",
  "status": "found",
  "profileUrl": "https://www.instagram.com/examplecreator/",
  "contactSourceUrls": ["https://www.instagram.com/examplecreator/"],
  "collectedAt": "2026-08-11T20:00:00.000Z"
}

More output fields

Field	JSON key	Description
Username	username	Instagram username.
Full name	fullName	Visible profile name.
Profile URL	profileUrl	Canonical public Instagram profile URL.
Profile image	profilePicUrl	Public profile image URL when available.
Biography	biography	Visible creator biography.
Category	category	Visible business or creator category.
Followers	followersCount	Visible follower count.
Following	followingCount	Visible following count.
Posts	postsCount	Visible post count.
Verified	isVerified	Whether the profile is visibly verified.
Private	isPrivate	Whether the profile is private.
Business account	isBusinessAccount	Visible business-account flag when available.
Profile email	businessEmail	Public business email declared by the profile.
Profile phone	businessPhoneNumber	Public business phone declared by the profile.
External website	externalUrl	First public website linked from the profile.
Emails	emails	Unique public emails found on the profile or bounded linked pages.
Primary email	primaryEmail	Declared business email when present. Otherwise the first email found in the biography or linked pages.
Social links	socialLinks	Other public social profile URLs found on linked pages.
Contact sources	contactSourceUrls	Public URLs where contact evidence was found.
Contact confidence	contactConfidence	profile_declared, linked_website, or none. Source classification, not deliverability verification.
Status	status	found, no_public_contact, or profile_unavailable. Unavailable does not prove a profile is private or deleted.
Error	error	Input-specific diagnostic when the public profile was unavailable.
Collected at	collectedAt	UTC collection timestamp.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once per run and result for each saved creator row, including saved status rows. These rows retain the requested-profile outcome even when contact information is missing or the profile was unavailable.

See the live Instagram Creator Email Finder Pricing tab for current rates for your plan.

Tips for best results

• Use a small known-profile list initially. The maximum is one hundred profiles, with at most five linked pages per creator.
• Choose profile-only or linked-page inspection deliberately. A zero-page cap restricts the search to profile evidence.
• Keep no-contact rows when coverage matters. They describe processed profiles, not a guarantee that every input was reached before the deadline.
• Open contact evidence before attributing ownership. A public address on a linked organization page is not necessarily a personal creator address.
• Check the summary before repeating missing profiles. Input-specific outcomes and bounded errors explain more than an absent email alone.

Limits and caveats

Only publicly exposed profile and linked-website information is used. No private contacts are guessed, and an extracted address is not deliverability verification or proof of personal ownership. Linked pages can belong to an agency, store or another organization. Public email and phone fields depend on what those pages expose.

Source pages can change, disappear or restrict access. Missing optional values are not fabricated, and an unavailable outcome does not establish privacy or deletion. A zero-row run with lookup errors fails. A completed lookup without contacts can return an empty dataset when no-contact rows are disabled.

The shared deadline can stop before later profiles are processed. RUN_SUMMARY records requested profiles, saved rows, contacts and bounded errors. Normalized duplicate usernames are processed once, and results follow normalized input order rather than follower count or contact quality. There is no built-in sorting or keyword discovery.

The run accepts at most one hundred profiles and inspects at most five linked pages per creator. Review public evidence and statuses before importing records into outreach systems. Repeat-check comparisons and scheduled integrations are your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~instagram-creator-email-finder/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "profiles": [
    "natgeo"
  ],
  "maxLinkedPagesPerProfile": 0,
  "includeNoContact": true
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/instagram-creator-email-finder').call({
  "profiles": [
    "natgeo"
  ],
  "maxLinkedPagesPerProfile": 0,
  "includeNoContact": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/instagram-creator-email-finder').call(run_input={'profiles': ['natgeo'], 'maxLinkedPagesPerProfile': 0, 'includeNoContact': True})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Instagram Creator Email Finder and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Instagram Creator Email Finder. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/instagram-creator-email-finder"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Instagram Creator Email Finder by Fetch Cat, or give it the identifier fetch_cat/instagram-creator-email-finder.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Instagram Creator Email Finder to retrieve natgeo and nasa with zero linked pages and no-contact rows enabled. Show public profile context and statuses without assuming an email is available.”
• “Collect public contact evidence for https://www.instagram.com/natgeo/ with at most 3 linked pages and no-contact rows enabled. Keep contact-source URLs and source classifications without verifying deliverability or assuming personal ownership.”
• “Retrieve natgeo with zero linked pages and no-contact rows disabled. Keep any returned contact evidence and explain a completed empty lookup separately from lookup errors or unfinished coverage.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it require an Instagram login?

No Instagram login input is required. The Actor works with publicly available profile and linked-site information.

Why is primaryEmail empty?

The creator may not publish an email, the profile may be private or unavailable, or the linked website may not expose one within the selected page limit. Check status and contactSourceUrls.

Can it process profile URLs and usernames together?

Yes. A single run can contain either format, and duplicate normalized usernames are processed once.

Can I schedule repeated lead checks?

Yes. Use Apify schedules, webhooks, API clients, or MCP workflows and compare collectedAt and status fields between runs.

Related Actors

More Instagram scrapers

• Instagram AI Transcript Extractor — Retrieve available transcript text from known public Instagram Reel or video URLs.
• Instagram Profile & Posts Scraper — Collect public profile details and available post or Reel metadata from known accounts or media URLs.
• Instagram Stories & Highlights Scraper — Collect accessible story and highlight records using your own authorized Instagram session. This does not bypass private-profile permissions.
• Instagram Post Details Scraper — Collect available captions, author details, dates and visible engagement from known public post URLs.
• Instagram Related Profiles Scraper — Collect direct related-profile suggestions from seed accounts, with available public identity fields.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥