How to Use an Instagram Follower Export Tool

Export a follower sample with a coverage report that says where it stops. Paste this into your agent:

Set up https://monid.ai/SKILL.md, and then use Monid to fetch one page of NASA's Instagram followers. Export the returned rows to CSV privately, and show me only aggregate counts. Record whether a next-page token exists. Keep the profile's follower count separate. Do not label the file a complete follower export.

Budget 1 min setup · 0.5-1 hrs saved for a repeat report, planning estimate.

If you're a growth marketer copying account names into a spreadsheet, an Instagram follower export tool sounds like the answer. But a brief asking for 1,000 followers requires 1,000 follower rows. A profile with millions of followers and a download containing 51 records are different deliverables.

Manual copying leaves you with a list whose coverage is hard to explain. Switching to a scraper does not solve that problem unless you also inspect the returned rows and the signal that tells you whether another page exists.

We'll use Monid, the tool layer for AI agents, to create a bounded follower sample and a coverage report. The tested tools cover follower collection, account lookup, and search; they do not deliver a complete follower export in this workflow. Start with one account, inspect the boundary, then export only what came back.

Here is the finished report from three successful calls on October 29, 2026. It contains aggregate results rather than follower identities.

How to use an Instagram follower export tool with Monid

Use Monid to fetch one follower page, retain its collection metadata, and let your agent produce the file. An endpoint is a callable tool with a defined input and response; its name alone does not establish export coverage.

Step 1. Set up your agent or terminal

For agents, get a key at app.monid.ai and give your agent the setup instruction below. Keep the key in the agent's credential setup, outside the report.

set up https://monid.ai/SKILL.md

For humans, install the CLI and add your key. The CLI quickstart explains the same setup.

npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main

Step 2. Give your agent one account and a stop rule

Ask for one public institutional account, one page, and a separate coverage summary. Use NASA for the first test, and tell the agent to stop when the continuation token is empty rather than constructing one.

Use NASA as the source account. Fetch one follower page, count the actual items, and retain the returned total separately. Do not enrich individual followers. If there is no continuation token, stop and label this a bounded sample.

The AnyAPI follower tool explicitly describes about one page of followers and no working continuation cursor today. Its declared fields include handle, id, image, name, nextCursor, private, url, and verified; this is an inspect-only field list, not output from our tests.

That tool has route-dependent matrix pricing, so it was excluded from paid testing here. We used the fixed-per-call TikHub follower tool for the real sample instead.

Step 3. Fetch the bounded sample

Request the follower page and inspect the returned item count and continuation token. Our successful call returned 51 items, a data.total of 104,363,450, and pagination_token: null; processing took 5.167 seconds from the recorded start to completion.

No second page followed from that response. An empty token is a stop condition, not permission to repeat the same request until the row count looks large enough.

Step 4. Export rows and a coverage summary

Tell the agent to save the returned follower rows privately and create a separate report with source_account, collected_at, returned_rows, reported_total, and continuation_present. Those are report columns you create from the response and collection metadata, rather than extra fields promised by the tool.

Keep the original response alongside the CSV so you can revisit the transformation. The public version of the report should contain counts and status labels, with no follower names, handles, IDs, images, or profile links.

How do you read an incomplete follower export?

Read the export as a bounded collection of observed accounts, not as a census or a random sample. Nothing in a 51-row response establishes how those followers were selected.

Keep counts and lists in separate columns

The profile lookup returned followersCount: 104369604; the follower-list response reported data.total: 104363450. Neither number means that many rows were exported.

The Instagram follower counts and lists guide explains the distinction in more detail. For this export, the business conclusion is straightforward: you have 51 observed follower records, and you cannot describe them as the account's complete audience.

Treat account flags as labels

Of the 51 returned follower records, 27 had is_private: true and none had is_verified: true. A private flag describes an account attribute in the returned row; it does not mean the call accessed private posts.

Neither flag is a quality score. Do not convert a missing badge into a bot label, or a private account into an exclusion rule, without a separate decision process that fits your task.

Use profile lookup to check the source account

The Apify profile tool returned one NASA profile with private: false, verified: true, and followsCount: 90. It also returned biography and website fields, which help confirm you selected the intended account.

The Instagram profile enrichment walkthrough shows how to turn public profile metadata into a table of follower counts, biographies, external URLs, and verification flags. That lookup describes the source profile. It does not expand the follower sample or add biographies to all 51 follower records. If account inspection is the whole task, the Instagram profile viewer workflow is the more direct guide.

How much does a follower export cost?

The three successful test calls cost a combined $0.0051, Verified 2026-10-29. Monid makes discovery and inspection free; executing tools is the paid step, with current prices in the tool catalog.

Separate per-call and per-result billing

The TikHub follower request cost $0.002 per call, Verified 2026-10-29. The 51 follower items were inside that single billed response, rather than 51 separately billed calls.

The Apify profile lookup cost $0.0016 per result, Verified 2026-10-29. The profile search cost $0.0015 per result, Verified 2026-10-29; each returned one billed result in our tests.

For the inspect-only AnyAPI tool, the declared route prices were $0.00188 for lynx and $0.018 for fox, Verified 2026-10-29. Those are selector-specific prices, not a measured charge from this guide. The card displays the rounded range $0.0019 to $0.0180, Verified 2026-10-29; the route prices above retain the precision from inspection.

Put a budget before enrichment

Start with one source account and one page. The follower query has no declared row-limit setting, so a small test means limiting requests rather than inventing a limit parameter.

Do not automatically look up every returned follower. Profile enrichment is a separate collection job that creates more calls and a different dataset. All three tested calls succeeded; their bills establish successful-call costs, not the treatment of empty responses or failures.

How do you export the sample in your own code?

Use the CLI to obtain the response, then transform the actual follower array into the columns your sheet needs. Monid supplies the tool call; your script supplies file naming, CSV quoting, and retention rules.

Discover, inspect, and fetch one page

These commands use the same query as the paid follower test. The input belongs in --query because the TikHub tool declares query parameters rather than a JSON request body.

monid discover -q "instagram follower export" -l 8 --include-unavailable -j
monid inspect -p tikhub -e /api/v1/instagram/v2/fetch_user_followers
monid run -p tikhub -e /api/v1/instagram/v2/fetch_user_followers \
  --query '{"username":"nasa"}' -w

Read data.items for follower rows, data.count for the response count, data.total for the reported audience total, and pagination_token for continuation. The run's own billing result count is separate from the number of follower items nested inside its output.

Check the account before adding more sources

Use the Apify search tool when your input is a name rather than a confirmed handle. Our single-result search returned NASA and included searchTerm and searchSource alongside the profile fields.

monid run -p apify -e /apify/instagram-search-scraper \
  -i '{"search":"NASA","searchType":"user","searchLimit":1}' -w
monid run -p apify -e /apify/instagram-profile-scraper \
  -i '{"usernames":["nasa"],"includeAboutSection":false}' -w

Set a small limit when testing search: searchLimit: 1 bounds this discovery step. The search result's audience count remains profile metadata, and its appearance in search does not establish a follower relationship.

Preserve the boundary when writing CSV

Map each item to the returned id, username, is_private, and is_verified, adding the source account and collection date as your own metadata. Quote string values correctly, preserve IDs as text, and retain empty values rather than replacing them with fabricated names.

For repeated collection, deduplicate using the returned ID within each source account and snapshot. Retain the snapshot date so a later observation does not silently overwrite an earlier one; absence from a later bounded page is not evidence of an unfollow.

Keep the enrichment table separate from the follower relationship table so a discovered profile is never accidentally counted as an observed follower.

Which tool should you use for each export task?

Choose the Monid tool by the row you need to produce. Follower membership, profile metadata, and search discovery answer different questions.

When should you use something else?

Use another route when your acceptance criterion exceeds a bounded public-account sample. You're reading the Monid blog, and this workflow routes calls to other providers; it does not remove their collection boundaries.

For records from your own account, begin with Instagram's information export help. Define the archive you need before buying third-party collection, and keep an account-owner archive distinct from a public-account scraper response.

Use Apify's direct profile scraper when its own export and scheduling workflow fits your operations. That remains a profile-data route, not evidence that it exports an account's entire follower list.

If your campaign contract requires every follower, do not accept today's sample as completion. Specify completeness as a deliverable, require evidence of coverage, and reject a report that substitutes the profile's audience number for exported records.

Conclusion

You now have a repeatable way to export observed follower rows and explain exactly what the file covers. The three Monid calls produced a 51-row sample, a source profile, and a search result; none supplies proof of complete follower coverage. The setup budget is a planning assumption, and the 0.5-1 hrs saved estimate assumes a recurring report otherwise takes 30-60 minutes of copying and formatting, not measured collection performance. Choose the route whose returned rows satisfy your brief, and your spreadsheet will say what you actually collected.

FAQ

Published October 2026.