Fast Data Actors (via Apify MCP) MCP server

Data Recipes by Fast Data

Free, ready-to-import n8n workflows that solve one small data job each: summarise a YouTube channel, get a daily news alert, track keyword trends, watch companies for new job postings, upscale product photos in bulk, turn incoming PDFs into Markdown with an AI summary.

Each recipe is one folder with:

• workflow.json: import it into n8n (cloud or self-hosted)
• README.md: what it does, step-by-step setup, cost example, ideas for changes
• devto.md: a longer write-up of the same recipe

The data comes from public Apify Actors by Fast Data (apify.com/fastdataasap). Disclosure: we build and maintain these Actors, and the recipes exist so you can try them in a real workflow in about 10 minutes.

Costs are the Actors' pay-per-result prices on the Apify Free and Starter plans (higher plans pay less). You pay only for results; there is no separate compute charge for these Actors. The Apify Free plan includes $5 of usage every month, which covers recipes 2, 3 and 4 running together every month.

Before you start (once for all recipes)

1. n8n: n8n Cloud or self-hosted. All workflows use built-in nodes only, nothing to install. Tested on n8n 2.43; recent 1.x versions (2025 or later) should work too.
2. Apify account: sign up free at apify.com. No credit card needed for the Free plan.
3. Apify API token: in Apify Console go to Settings → API & Integrations and copy your Personal API token.
4. One n8n credential for Apify: in n8n go to Credentials → Add credential → Header Auth and enter:

• Name: Authorization
• Value: Bearer YOURAPIFYTOKEN (the word Bearer, a space, then the token)

Call it e.g. Apify API token. Every recipe uses this credential in its HTTP Request nodes. Never paste the token into the URL or the workflow JSON: credentials are encrypted, workflow JSON is not.

How the recipes call Apify

Every recipe uses n8n's standard HTTP Request node against Apify's synchronous endpoint:

POST https://api.apify.com/v2/acts/fast_data_asap~<actor-name>/run-sync-get-dataset-items
Authorization: Bearer <token>
Content-Type: application/json

{ ...Actor input... }

It starts the Actor, waits until it has finished and returns the results as a JSON array; n8n turns each result into one item. The JSON body is exactly the Actor's input, so you can design an input in Apify Console (Input tab → JSON view) and paste it into the node.

Shortened. The full README is on GitHub.