Skip to main content
skill CX Codex

finding-instagram-creators-by-location — Claude Code skill: local

Finds Instagram creators who post from a given city, venue or neighborhood. Useful for geo-targeted campaigns and regional partnerships.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add apidojo-io/apidojo-skills --skill finding-instagram-creators-by-location -a claude-code
Open on GitHub

What finding-instagram-creators-by-location does

The skill runs the apidojo/instagram-location-scraper actor on Apify and groups posts by author. You get a table with handle, post count at the location, follower estimate, engagement and recent content.

The workflow has steps. First resolve the numeric location ID from a page like instagram.com/explore/locations/[LOCATION_ID]/[name]/. Then run the actor through scripts/run_actor.js, the apify:run-actor MCP tool, or the REST API. After that the skill computes a local_score from repeat posts, likes, comments, a linked website and follower count, and sorts creators into tiers A, B and C.

You need an APIFY_TOKEN environment variable set — none of the run methods work without it. Small venues may have no location ID at all, so the skill suggests falling back to the city or neighborhood and filtering by caption mentions. One-off tourist accounts rank below repeat posters, and business accounts get flagged separately.

What it helps with

  • build a list of creators posting from a specific city
  • separate real locals from tourists by post count at the location
  • check engagement before a geo-targeted campaign
  • find micro-influencers for a local brand
  • break creators down by niche within one place

Example prompts for the agent

  • find Instagram creators posting from Berlin
  • pull local influencers from Kreuzberg for a campaign
  • show creators who post from this venue often

How to install finding-instagram-creators-by-location

1Skills CLI (Vercel)

npx skills add apidojo-io/apidojo-skills --skill finding-instagram-creators-by-location -a claude-code

2Manually: put the files in place

~/.claude/skills/finding-instagram-creators-by-location/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/finding-instagram-creators-by-location/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about finding-instagram-creators-by-location

How do I install finding-instagram-creators-by-location in Claude?

Run npx skills add apidojo-io/apidojo-skills --skill finding-instagram-creators-by-location -a claude-code. The skill then lands at ~/.claude/skills/finding-instagram-creators-by-location/SKILL.md.

What does finding-instagram-creators-by-location do?

It runs an Instagram location scraper on Apify and collects creators posting from a chosen place. You get handle, location post count, follower estimate and engagement.

What do I need for this skill to work?

An APIFY_TOKEN environment variable. Optionally install the Apify MCP server, which lets the skill run the actor through the apify:run-actor tool.

Source text

SKILL.md · Apache-2.0
---
name: finding-instagram-creators-by-location
description: >
  Finds Instagram content creators and influencers posting from a specific location using
  apidojo's Instagram location scraper on Apify. Triggers when the user asks to: find Instagram
  creators based in a city, discover local influencers in a geographic market, find content
  creators who post from a specific venue or neighborhood, identify local Instagram micro-influencers
  for geo-targeted campaigns, find creators in a country for regional brand partnerships, or
  discover influencers who have visited or are based in a specific location.
  Returns creator handle, post count at location, follower estimate, engagement, and recent content.
  Ideal for regional brand campaigns, local business marketing, and geo-targeted influencer programs.
license: Apache-2.0
metadata:
  author: apidojo
  version: "1.0"
  apify-actor: apidojo/instagram-location-scraper
---

# Finding Instagram Creators by Location

Identifies Instagram creators who actively post from a specific location — city, venue, or region. Creators with repeated location posts have genuine local presence and authentic ties to the place.

## Prerequisites

- `APIFY_TOKEN` environment variable set
- Optional: Apify MCP server installed

## Inputs

| Parameter | Type | Required | Default | Notes |
|-----------|------|----------|---------|-------|
| `startUrls` | array | Optional | `[]` | Instagram location page URLs |
| `locationIds` | array | Optional | `[]` | Instagram location IDs |
| `maxItems` | number | Optional | Unlimited | Maximum posts to return |
| `until` | string | Optional | — | Date filter (YYYY-MM-DD) |
| `customMapFunction` | string | Optional | — | JavaScript function to transform each output object |

## Workflow

```
Progress:
- [ ] Step 1: Resolve location ID
- [ ] Step 2: Run instagram-location-scraper
- [ ] Step 3: Identify repeat creators
- [ ] Step 4: Score creator quality
- [ ] Step 5: Deliver local creator list
```

### Step 1: Resolve Location ID

Instagram uses numeric location IDs. To find the ID:
1. Search for the location on Instagram (mobile or desktop)
2. Open the location page — URL format: `instagram.com/explore/locations/[LOCATION_ID]/[name]/`
3. Extract the numeric ID

If the user only provides a name, run a Google search:
`site:instagram.com/explore/locations "[LOCATION_NAME]"`

### Step 2: Run the Actor


**Recommended — run_actor.js (handles waiting, output, and file saving automatically):**
```bash
# Quick answer (prints table to chat)
node scripts/run_actor.js \
  --actor "apidojo~instagram-location-scraper" \
  --input '{"param": "value"}'

# Save as CSV
node scripts/run_actor.js \
  --actor "apidojo~instagram-location-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.csv --format csv

# Save as JSON
node scripts/run_actor.js \
  --actor "apidojo~instagram-location-scraper" \
  --input '{"param": "value"}' \
  --output YYYY-MM-DD_results.json --format json
```
> `APIFY_TOKEN` must be set in environment or `.env` file.

**If Apify MCP is available:**
```
Tool: apify:run-actor
Actor: "apidojo~instagram-location-scraper"
Input:
{
  "locationIds": ["[LOCATION_ID]"],
  "maxItems": 100
}
```

**REST API fallback:**
```bash
curl -X POST   "https://api.apify.com/v2/acts/apidojo~instagram-location-scraper/runs?token=$APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"locationIds": ["[LOCATION_ID]"], "maxItems": 100}'
```

### Step 3: Score Creator Quality

From location posts, group by `ownerUsername`. For each creator:

```
local_score = min(post_count_at_location / 5, 1) * 0.30  # repeat presence
            + (avg_likes / 100) * 0.25  # engagement quality
            + (avg_comments / 10) * 0.20  # comment depth
            + (has_website ? 1 : 0) * 0.15  # professional creator signal
            + (follower_count > 1000 ? 1 : 0) * 0.10
```

Clamp to [0, 1]. Tier: A ≥ 0.70 | B 0.40–0.69 | C < 0.40

### Step 4: Edge Cases

- **Location ID not found for small venue**: Try the city or neighborhood instead; scrape and filter by caption mentioning venue name
- **Tourist accounts dominate results** (one-time visitors): Filter by `post_count_at_location = 1` being lower priority than repeat posters
- **Business accounts posting from location**: If `is_business_account = true`, flag separately — these are brand accounts, not creator UGC
- **< 30 posts at location**: Small or new venue — lower `min_followers` threshold to 500; include more results

## Output Format

```
# Instagram Local Creators: [LOCATION_NAME]
Posts scraped: [N] | Unique creators: [N] | Repeat locals (2+ posts): [N] | Date: [DATE]

## TIER A — Established Local Creators (2+ Location Posts)
| Creator | @Handle | Location Posts | Avg Likes | Avg Comments | Content Theme | Score |
|---------|---------|---------------|-----------|--------------|---------------|-------|
| [name] | @[handle] | [N] | [N] | [N] | [food/lifestyle/travel] | [0.XX] |

## TIER B — Active Local Voices
| Creator | @Handle | Location Posts | Avg Likes | Last Post |
|---------|---------|---------------|-----------|----------|

## Niche Breakdown at [LOCATION]
| Content Theme | # Posts | Top Creator |
|--------------|---------|------------|
| [food] | [N] | @[handle] |
| [travel] | [N] | @[handle] |
```

## Troubleshooting

**Very few results for city**: City-level location IDs return general "in [city]" tags. Look for neighborhood or landmark IDs for denser results.
**Results are mostly tourist accounts**: Focus on the `post_count_at_location >= 3` tier — locals post from the same location repeatedly.
**Wrong city matches location name**: Some city names are duplicated globally. Verify the location page on Instagram before running.

© apidojo · Apache-2.0 · apidojo-io/apidojo-skills

Similar skills

Everything for Marketing and content →

From the same set22

scraping-tiktok-profile-data Pulls TikTok profile stats and metadata for a batch of accounts: followers, following, total likes, video count, bio. Handy when you need to vet a creator list. CX Codex +1 834installs scraping-instagram-location-content Pulls public Instagram posts tagged at one place and returns post URLs, captions, handles, likes and dates. Useful when you want to see what visitors post about a venue. CX Codex +1 810installs analyzing-competitor-instagram-content-strategy This skill pulls a competitor's recent Instagram posts and shows which formats and themes earn them engagement. Useful when you need to read someone else's content plan. CX Codex +1 796installs extracting-youtube-comments-for-research Pulls YouTube comments from videos and channels through Apify, then sorts them into themes, questions and sentiment. Useful when you need to know what viewers actually say. CX Codex +1 794installs monitoring-vc-investor-activity-on-twitter This skill pulls investor tweets through apidojo's scraper, classifies the accounts and scores deal signals. Useful when you are raising. CX Codex +1 789installs tracking-twitter-thought-leaders Finds Twitter/X accounts whose posts on a topic actually get shared, then hands back a ranked list for PR and partnerships. CX Codex +1 786installs monitoring-twitter-for-competitor-job-posts Tracks competitor hiring tweets on X and turns them into growth signals: who is hiring, for what role, and when. CX Codex +1 786installs analyzing-competitor-twitter-profile-content This skill pulls a competitor's or brand's tweet history through Apify and ranks posts by engagement. Useful when you need to see what a rival actually posts. CX Codex +1 784installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor