Medium Feed Lookup: Latest Posts by Author, Tag, Publication

Get the latest Medium posts for any author, tag or publication as clean rows, and get alerted to new ones. Each feed you list returns its most recent posts with title, link, author, publish and update dates, tags, a text excerpt and the lead image. Turn on monitoring mode and run it on a schedule to receive only the posts that are new since your last run, charged per post and free on a quiet day.

Who uses it. Content and competitor-research teams tracking a company's engineering blog, newsletter writers curating a tag, analysts watching which publications cover a topic, and agents or n8n/Clay flows that need "what did this author publish this week" as structured data.

What it reads. Medium's own public RSS feeds (medium.com/feed/@author, /feed/tag/<tag>, /feed/<publication>). A feed holds the 10 most recent posts, so this is a latest-posts and new-post alert actor, not an archive scraper. Claps and responses are not in the feed and are not returned. Full text is only in author and publication feeds, so wordCount is null on tag feeds (never 0).

How to use

1. In the Apify Console. Open the actor page and click Start — the feeds field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~medium-feed-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"feeds":["@netflixtechblog","tag/data-science"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "feeds": [
    "@netflixtechblog",
    "tag/data-science"
  ]
}

One per line: an author (@netflixtechblog), a tag (tag/data-science) or a publication (towards-data-science). A medium.com profile, tag, publication or feed URL works too. Each feed returns its latest posts, newest first. Accepted formats: @netflixtechblog, tag/data-science, towards-data-science, https://medium.com/@netflixtechblog.

One feed per line. A bare word is read as a publication slug (towards-data-science); put @ in front for an author and tag/ in front for a tag. Medium profile, tag, publication and feed URLs are accepted and reduced to the same three forms. Custom-domain publications are reached by their Medium slug.

Output

One row per item, for example:

query	found	status	feed	feedType	feedTitle	feedUrl	postCount	truncated	monitorStatus	posts	postId	title	url	author	publishedAt	updatedAt	tags	excerpt	imageUrl	wordCount	isNew	firstSeenAt	scrapedAt
@netflixtechblog	true	OK								<all posts (full list)>											<is this post new?>		1970-01-01T00:00:00.000Z

Example rows (real output, trimmed):

{
  "query": "tag/data-science",
  "found": true,
  "status": "OK",
  "feed": "tag/data-science",
  "feedType": "tag",
  "feedTitle": "Data Science on Medium",
  "postCount": 10,
  "postId": "bcfe74cd8d1a",
  "title": "When AI Is Unsure: Rethinking Health Misinformation Detection in Nigerian Pidgin",
  "url": "https://medium.com/@destinifeoluwa/when-ai-is-unsure-rethinking-health-misinformation-detection-in-nigerian-pidgin-bcfe74cd8d1a",
  "author": "Olayode Racheal Oluwayemisi",
  "publishedAt": "2026-10-11T16:45:34.000Z",
  "tags": ["healthtech", "research", "data", "data-science"],
  "excerpt": "Why reliable AI should know when to make a prediction and when to step back.",
  "wordCount": null,
  "isNew": null,
  "scrapedAt": "2026-10-11T17:00:00.000Z"
}

A feed that does not exist comes back as a row with "found": false (NOT_FOUND) and is never charged. A quiet monitoring run returns one row with "postCount": 0 and is never charged either.

Pricing

$4 per 1,000 posts on the Free plan, less on paid plans, plus a $0.00005 start fee per run. You pay only for posts actually returned.

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

Latest posts from one company engineering blog.

{
  "feeds": ["@netflixtechblog"],
  "maxItems": 5
}

A tag and a publication side by side.

{
  "feeds": ["tag/data-science", "towards-data-science"]
}

New-post alert: schedule this daily and only new posts come back.

{
  "feeds": ["@netflixtechblog", "tag/machine-learning"],
  "onlyNewSinceLastRun": true,
  "deltaName": "my-medium-alerts"
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~medium-feed-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"feeds":["@netflixtechblog","tag/data-science"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~medium-feed-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"feeds":["@netflixtechblog","tag/data-science"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~medium-feed-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"feeds":["{{feed}}"]}, mapping the row's feed into the feeds array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "medium scraper by author or tag" — the agent will find and run this actor.