apify-market-research
Original:🇺🇸 English
Translated
1 scripts
Analyze market conditions, geographic opportunities, pricing, consumer behavior, and product validation across Google Maps, Facebook, Instagram, Booking.com, and TripAdvisor.
98installs
Sourceapify/agent-skills
Added on
NPX Install
npx skill4agent add apify/agent-skills apify-market-researchTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Market Research
Conduct market research using Apify Actors to extract data from multiple platforms.
Prerequisites
(No need to check it upfront)
- file with
.envAPIFY_TOKEN - Node.js 20.6+ (for native support)
--env-file - CLI tool:
mcpcnpm install -g @apify/mcpc
Workflow
Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify market research type (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findingsStep 1: Identify Market Research Type
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Market density | | Location analysis |
| Geospatial analysis | | Business mapping |
| Regional interest | | Trend data |
| Pricing and demand | | Market pricing |
| Event market | | Event analysis |
| Consumer needs | | Group research |
| Market landscape | | Business pages |
| Business density | | Contact data |
| Cultural insights | | Visual research |
| Niche targeting | | Hashtag research |
| Hashtag stats | | Market sizing |
| Market activity | | Activity analysis |
| Market intelligence | | Full data |
| Product launch research | | API access |
| Hospitality market | | Hotel data |
| Tourism insights | | Review analysis |
Step 2: Fetch Actor Schema
Fetch the Actor's input schema and details dynamically using mcpc:
bash
export $(grep APIFY_TOKEN .env | xargs) && mcpc --json mcp.apify.com --header "Authorization: Bearer $APIFY_TOKEN" tools-call fetch-actor-details actor:="ACTOR_ID" | jq -r ".content"Replace with the selected Actor (e.g., ).
ACTOR_IDcompass/crawler-google-placesThis returns:
- Actor description and README
- Required and optional input parameters
- Output fields (if available)
Step 3: Ask User Preferences
Before running, ask:
- Output format:
- Quick answer - Display top few results in chat (no file saved)
- CSV - Full export with all fields
- JSON - Full export in JSON format
- Number of results: Based on character of use case
Step 4: Run the Script
Quick answer (display in chat, no file):
bash
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT'CSV:
bash
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.csv \
--format csvJSON:
bash
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.json \
--format jsonStep 5: Summarize Findings
After completion, report:
- Number of results found
- File location and name
- Key market insights
- Suggested next steps (deeper analysis, validation)
Error Handling
APIFY_TOKEN not found.envAPIFY_TOKEN=your_tokenmcpc not foundnpm install -g @apify/mcpcActor not foundRun FAILEDTimeout--timeout