The On-Demand Leads with Apify setup prompt + walkthrough

Paste this into any capable agent and it walks you through the connections, the trigger, and a supervised first run — the whole setup, in your own words. Or skip the setup and run this exact agent hosted.

Set up an agent for me, in its own chat, that does the work of a On-Demand Leads with Apify. Work from the files and facts I actually give it, rank what matters by impact rather than by how many items it found, and stop short of sending, filing, posting, or changing anything live unless I ask for that in the same run. Walk me through connecting Anthropic and Apify. Have it run whenever I hand it the work, and every weekday morning on whatever I left unfinished. Ask me where the source material lives, who should receive the output, and what good enough looks like for a first pass. Run one pass while I watch, then save it.

Already built, running in ~3 min · 30-day money-back on first purchase

#apify #claude-code #clay #gtm #lead-gen #leads #mcp #outbound #scrape

About this template

Fresh lists from a URL — not last quarter’s CSV

Apollo exports go stale. This Claude Code template uses Apify MCP to build on-demand lists: derive ICP from a URL → run Store Actors → fix work emails → rank engagers. Never auto-sends.

The undeniable demo

Fork → Claude Code login / ANTHROPIC_API_KEY.
Connect Apify (OAuth or token per Apify MCP docs) — credits are yours.
Ask:

Build a lead list from . ICP first, then scrape, fix emails, rank engagers. Do not send anything.

You should get a list artifact you own — not a chatbot saying it “would” scrape.

What lands in your fork

lead-scrape-apify skill (ICP → actors → email fix → engagers)
Secret-free .mcp.json pointed at https://mcp.apify.com
Human-gated send policy in the playbook

BYOK

You bring	Notes
Claude Code / Anthropic	Runtime
Apify account + credits	Real actor runs cost money

Who this is for

GTM engineers who prefer fresh scrapes over static lists
Claude Code users already (or ready to be) on Apify
Teams that keep a human between list and sequencer

Who this is not for

People who want free unlimited B2B emails with no Apify bill
Auto-send day-one outbound
Non–Claude Code harnesses

Risk note

jurniti 30-day money-back on first purchase. Apify actor spend is yours.

Fork it. Connect Apify. Build one list from a real URL.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

Claude Code agent
The upstream harness, pre-installed — same version the creator ran.
Starter VM
1 vCPU · 2 GiB RAM · 10 GiB disk.
Creator's /persist data
The captured persist volume is copied byte-for-byte into your fork.
BYOK — your keys, your VM
Add your model API keys after forking; they live only inside your microVM.

What this agent can do

1 skill

lead-scrape-apify
Build on-demand lead lists from a terminal via Apify MCP — no Apollo/ZoomInfo CSV. Derive ICP from a URL, pick scrapers, run Actors, fix…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

ANTHROPIC_API_KEY

MCP connections

apify

Related templates

Your own On-Demand Leads with Apify, live in about 3 minutes.

Copy the setup prompt and build it yourself — or let this exact Claude Code agent run hosted, already built, on a brand-new, fully isolated microVM on your own subdomain. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

On-Demand Leads with Apify

What's inside