with one click
apify-lead-generation
Scrape leads from multiple platforms using Apify Actors.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Scrape leads from multiple platforms using Apify Actors.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Riff a winning TikTok into your own short video — study a proven video's emotion formula and regenerate it with your product, character, and language (EN/ES). Also makes UGC ad creative.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this,"...
Triage acc's open promises and close them with honest real-world verdicts via acc_act(runtime="outcome").
Drain acc's deliberation queue — open/waiting brain_frames checkpointed by headless runs — via acc_act(runtime="continue").
Route a goal through acc's scored-memory loop via acc_act(runtime="solve"); deliberate any returned brain_frame and submit via continue.
Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
| name | apify-lead-generation |
| description | Scrape leads from multiple platforms using Apify Actors. |
| risk | unknown |
| source | community |
Scrape leads from multiple platforms using Apify Actors.
(No need to check it upfront)
.env file with APIFY_TOKEN--env-file support)mcpc CLI tool: npm install -g @apify/mcpcCopy this checklist and track progress:
Task Progress:
- [ ] Step 1: Determine lead source (select Actor)
- [ ] Step 2: Fetch Actor schema via mcpc
- [ ] Step 3: Ask user preferences (format, filename)
- [ ] Step 4: Run the lead finder script
- [ ] Step 5: Summarize results
Select the appropriate Actor based on user needs:
| User Need | Actor ID | Best For |
|---|---|---|
| Local businesses | compass/crawler-google-places | Restaurants, gyms, shops |
| Contact enrichment | vdrmota/contact-info-scraper | Emails, phones from URLs |
| Instagram profiles | apify/instagram-profile-scraper | Influencer discovery |
| Instagram posts/comments | apify/instagram-scraper | Posts, comments, hashtags, places |
| Instagram search | apify/instagram-search-scraper | Places, users, hashtags discovery |
| TikTok videos/hashtags | clockworks/tiktok-scraper | Comprehensive TikTok data extraction |
| TikTok hashtags/profiles | clockworks/free-tiktok-scraper | Free TikTok data extractor |
| TikTok user search | clockworks/tiktok-user-search-scraper | Find users by keywords |
| TikTok profiles | clockworks/tiktok-profile-scraper | Creator outreach |
| TikTok followers/following | clockworks/tiktok-followers-scraper | Audience analysis, segmentation |
| Facebook pages | apify/facebook-pages-scraper | Business contacts |
| Facebook page contacts | apify/facebook-page-contact-information | Extract emails, phones, addresses |
| Facebook groups | apify/facebook-groups-scraper | Buying intent signals |
| Facebook events | apify/facebook-events-scraper | Event networking, partnerships |
| Google Search | apify/google-search-scraper | Broad lead discovery |
| YouTube channels | streamers/youtube-scraper | Creator partnerships |
| Google Maps emails | poidata/google-maps-email-extractor | Direct email extraction |
Fetch the Actor's input schema and details dynamically using mcpc:
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 ACTOR_ID with the selected Actor (e.g., compass/crawler-google-places).
This returns:
Before running, ask:
Quick answer (display in chat, no file):
node --env-file=.env ${CLAUDE_PLUGIN_ROOT}/reference/scripts/run_actor.js \
--actor "ACTOR_ID" \
--input 'JSON_INPUT'
CSV:
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 csv
JSON:
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 json
After completion, report:
APIFY_TOKEN not found - Ask user to create .env with APIFY_TOKEN=your_token
mcpc not found - Ask user to install npm install -g @apify/mcpc
Actor not found - Check Actor ID spelling
Run FAILED - Ask user to check Apify console link in error output
Timeout - Reduce input size or increase --timeout