Discover and track emerging trends using Apify Actors to extract data from multiple platforms.
Verify prerequisites before any paid run.
.env file with APIFY_TOKEN--env-file support).env untracked and private; configure the token locally without pasting it into chat or command arguments.Copy this checklist and track progress:
Task Progress:
- [ ] Step 1: Identify trend type (select Actor)
- [ ] Step 2: Fetch Actor schema via an approved connector or Console
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the analysis script
- [ ] Step 5: Summarize findings
Select the appropriate Actor based on research needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Search trends | apify/google-trends-scraper | Google Trends data |
| Hashtag tracking | apify/instagram-hashtag-scraper | Hashtag content |
| Hashtag metrics | apify/instagram-hashtag-stats | Performance stats |
| Visual trends | apify/instagram-post-scraper | Post analysis |
| Trending discovery | apify/instagram-search-scraper | Search trends |
| Comprehensive tracking | apify/instagram-scraper | Full data |
| API-based trends | apify/instagram-api-scraper | API access |
| Engagement trends | apify/export-instagram-comments-posts | Comment tracking |
| Product trends | apify/facebook-marketplace-scraper | Marketplace data |
| Visual analysis | apify/facebook-photos-scraper | Photo trends |
| Community trends | apify/facebook-groups-scraper | Group monitoring |
| YouTube Shorts | streamers/youtube-shorts-scraper | Short-form trends |
| YouTube hashtags | streamers/youtube-video-scraper-by-hashtag | Hashtag videos |
| TikTok hashtags | clockworks/tiktok-hashtag-scraper | Hashtag content |
| Trending sounds | clockworks/tiktok-sound-scraper | Audio trends |
| TikTok ads | clockworks/tiktok-ads-scraper | Ad trends |
| Discover page | clockworks/tiktok-discover-scraper | Discover trends |
| Explore trends | clockworks/tiktok-explore-scraper | Explore content |
| Trending content | clockworks/tiktok-trends-scraper | Viral content |
Inspect the current Actor details and input schema using the authenticated Apify connector available in the session, or its Console page. Discover actual tool names and parameters before calling them. Do not parse .env with shell substitution or pass a token as a CLI header argument. Treat the Actor table as discovery candidates, not verified availability or schemas.
This returns:
Before running, ask:
Quick answer (display in chat, no file):
node --env-file=.env "<resolved-skill-directory>/reference/scripts/run_actor.js" \
--actor "ACTOR_ID" \
--input 'JSON_INPUT'
CSV:
node --env-file=.env "<resolved-skill-directory>/reference/scripts/run_actor.js" \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.csv \
--format csv
JSON:
node --env-file=.env "<resolved-skill-directory>/reference/scripts/run_actor.js" \
--actor "ACTOR_ID" \
--input 'JSON_INPUT' \
--output YYYY-MM-DD_OUTPUT_FILE.json \
--format json
After completion, report:
APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_tokenConnector unavailable - Inspect the schema through the Console; do not claim an unavailable tool was called.Actor not found - Check Actor ID spellingRun FAILED - Ask user to check Apify console link in error outputTimeout - The local timeout does not abort the remote run. Inspect the printed run ID in Console before retrying to avoid duplicate charges.
Before launch, confirm the selected Actor, authorized public-data scope, current input schema, result limits and pricing with the user’s request. Respect source terms and access controls; do not collect private group data or unnecessary personal contact information. Start with a small Actor-supported input limit. --max-items limits downloaded output only (default 1000); it does not cap Actor work or billing. The helper sends a skill-identifying User-Agent to Apify. Resolve the installed skill directory in the command placeholders. Output files must be new paths; exports preserve long values and heterogeneous fields. Quick answers fetch at most five records; minimize or redact personal fields before sharing.
Use for comparing search interest, public hashtags, sounds or content over defined time windows and regions. Keep normalized trend indices distinct from absolute audience or sales counts; state collection dates, sample bias and platform coverage.