Live web data, plated for your agent.

Pick a website and where the data should land. You get a working config or workflow wired to an Apify Actor, ready to paste.

Ingredient: a website
Dish: where it goes
  • 394 Actors with configs
  • 166 websites
  • 65 recipes
Google Maps Apify Actor Google Maps Business Lead Finderwith Email & Social Links Claude Code

Recipes

A source, a destination and a method you can follow in ten minutes. All 65 recipes

  • Google Maps leads to Google Sheets

    Pull local business leads from Google Maps into a Google Sheet on a schedule, with phone, website, rating and address…

    Google MapsGoogle Maps Business Lead…Google Sheets
  • Reddit mentions to Slack

    Monitor public Reddit posts for a keyword and send only the posts you have not seen before to a Slack channel.

    RedditReddit Keyword Search with…Slack
  • YouTube transcripts to Notion

    Turn public YouTube transcripts into Notion pages for a research library or RAG corpus.

    YouTubeYouTube Caption & Whisper AI…Notion
  • Zillow new listings to Slack

    Post the Zillow listings added in the last day for a search area to Slack, with price, beds, baths and the listing link.

    ZillowZillow For-Sale, Rent & Sold…Slack
  • LinkedIn jobs to Google Sheets

    Export public job postings into a Sheet so a recruiter or researcher can filter by role, company and location.

    LinkedIn JobsLinkedIn Jobs Scraper with…Google Sheets
  • Amazon prices to Google Sheets

    Log the price, rating and stock of the Amazon products you watch in a Google Sheet every day.

    AmazonAmazon Multi-Domain Product…Google Sheets

MCP servers by website

Every catalogue Actor for one site, bundled into a single Apify MCP URL. All websites

One request, one answer

13 Actors also work as plain HTTP APIs: send the input, get the results in the response. All one-request APIs

The pantry

Every Actor has its own page with an MCP config, an n8n workflow, an example input and a SKILL.md. Browse all 394

Validated, not executed

Each file is generated from the Actor's published input schema. Before a page ships, the build checks that the MCP URL and client formats match the current docs, that every n8n node type and version exists in n8n, that the Actor input passes the schema, and that no token is embedded.

Nothing here runs the Actor for you, so there are no made-up results. What the checks cover

For agents reading this

Every Actor's MCP URL, n8n workflow, skill file and example input is listed in one machine-readable index.

Open agents.json