Resources · n8n integration

Medium n8n integrationAutomate Medium with n8n.

Publishing on Medium can be the last step of a workflow instead of another browser tab. The Medium n8n integration covers 2 resources and 2 operations: it creates a post, and it reads publications. There is no Medium trigger, so the run starts somewhere else, on a schedule or on an event from another app.

Try the Medium integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Medium n8n integration actually give you?

The Medium n8n integration is a node shipped inside n8n that calls the Medium API with a credential you save once. A credential is the stored login n8n reuses everywhere, so the token sits in one place instead of in every node. Two things happen through it: a post gets created from content the workflow already holds, and publications come back as items you can read further down the flow.

Start with the case that brings most people here. The writing happens elsewhere, and the piece should land on Medium too. A row arrives in Google Sheets with a headline and a body, n8n maps them onto Title and Content, sets Content Format to markdown, and the article exists without anyone opening the editor.

Second pattern: nothing goes out unreviewed. The workflow assembles the article, sets Publish Status to draft inside Additional Fields, then drops a message in Slack for whoever signs off. The same shape works for a team that already sends its issues through SendGrid and wants the archive copy on Medium.

Third, the housekeeping one. Get many publications pulls publications into the run, and Return All decides whether every page of results comes back or whether n8n stops at Limit. Handy when several people write under the same brand and the workflow has to pick the right destination before anything is created.

For an endpoint that is outside these 2 operations, the HTTP Request node calls it directly and reuses the very same credential through predefined authentication, so nothing has to be stored twice.

One thing to read before you build: Medium has stopped supporting the Medium API. The node still appears in n8n, but new API keys can no longer be configured to authenticate with, and the credentials page covers setting up existing API keys only. Worth knowing where the effort goes before you plan a publishing chain around it. If you are still weighing platforms, the n8n review goes through the trade-offs, and the n8n training covers building this kind of flow end to end.

Connect

How do you connect Medium to n8n?

  1. 01

    Create a Medium account and pick a method

    An account on Medium is the prerequisite for both supported authentication methods: API access token and OAuth2. In n8n, credentials live in the Credentials menu, and the Medium node offers them in a dropdown once they exist. For OAuth2 there is an extra step before anything else: access to credentials is requested by emailing yourfriends@medium.com.

  2. 02

    Generate an Access Token

    The simpler route. Inside Medium, open Settings, then Security and apps, then Integration tokens, and generate a token there. That integration token is what you paste into the n8n credential as the Access Token. Nothing else is asked for, and the same credential then serves every workflow that touches Medium, no matter how many nodes end up using it.

  3. 03

    Or register an OAuth2 application

    The OAuth2 credential asks for a Client ID and a Client Secret. Both come from the Developers menu in Medium, where you create a new application. Two settings matter while you fill that form: select OAuth 2 as the Authorization Protocol, and copy the OAuth Callback URL that n8n displays into the Callback URL field on the Medium side.

Actions

What can the Medium node do?

The Medium node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGet Many
Post✓
Publication✓

Post

1 operation
01

Create a post

post.create

What you see in n8n

Notes & use cases

Creates the post on Medium from content the workflow already carries.

Key parameters

  • Title: the post title, 100 characters maximum.
  • Content Format: html or markdown, how the body should be read.
  • Content: the body, as a valid semantic HTML fragment or as Markdown.
  • Publication: on when the post goes to a publication, then set Publication Name or ID from the list or an expression like {{ $json.field }}.
  • Publish Status: in Additional Fields, public, draft or unlisted, next to Tags (comma separated, 5 maximum, 25 characters each), Canonical Url, License and Notify Followers.
Use cases
a weekly product note ships as a post with its tags already set, while a longer piece lands as draft and waits for a reader.

Publication

1 operation
02

Get many publications

publication.getAll

What you see in n8n

Notes & use cases

Brings publications back into the workflow as items, which is what you want before deciding where a post should go.

Key parameters

  • Return All: switched on, n8n walks through every page of API results; switched off, it stops at Limit.
  • Limit: the maximum number of results returned when Return All stays off.
Use cases
a monthly run lists the publications and writes them into a sheet so the editorial calendar always has current destinations, and the same list feeds the dropdown logic of a posting flow that serves several brands.
Need help

Need help automating Medium with n8n?

A person reads every message.

FAQ

Medium and n8n, the questions that come next

01Is the Medium n8n integration free?
Yes. The Medium node ships with n8n, so there is nothing to install and nothing extra to pay on the n8n side. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves identically on both, so you can build on one and move it to the other without rewriting the node. What Medium itself costs is a separate question that this page does not cover. The only real setup cost is creating the credential once in the Credentials menu, after which every workflow that touches Medium picks it from a dropdown.
02What credentials do you need for the Medium node?
Two authentication methods are supported: an API access token, and OAuth2. Both need a Medium account first. For the token route, you generate an integration token under Settings, then Security and apps, then Integration tokens, and paste it into the n8n credential as the Access Token. For OAuth2, you need a Client ID and a Client Secret, created from a new application in the Developers menu, with OAuth 2 selected as the Authorization Protocol and the OAuth Callback URL copied from n8n into the Callback URL field. Access to OAuth2 credentials is requested by emailing yourfriends@medium.com. Note that Medium has stopped supporting the Medium API, so new integrations can no longer be configured with these credentials.
03What are the limits of the Medium node in n8n?
The catalogue is deliberately small: 2 resources and 2 operations, one to create a post and one to get many publications. For an endpoint outside that pair, the HTTP Request node calls the Medium API directly and reuses the same credential through predefined authentication, so you are not blocked and you are not storing a second token. Inside the node, a few values are fixed: Title stops at 100 characters, Tags allows 5 tags of at most 25 characters each, and on Get many publications, Return All off means Limit caps the results. The bigger constraint sits upstream: Medium has stopped supporting the Medium API, and new API keys cannot be configured to authenticate with.
04Does the Medium node react in real time?
There is no Medium trigger node in n8n, so nothing is listening on the Medium side and the question of real time moves elsewhere. A workflow that involves Medium starts with another starting point: the Schedule Trigger, which fires at a fixed interval, the n8n Webhook node, which exposes a URL that a third-party service calls when something happens on its side, or the trigger of another tool you already automate. In practice that is rarely a problem here, because publishing is the end of a chain rather than the start of one. The event that matters usually happens in the tool where the writing or the review lives.
05n8n or Make for Medium?
It depends on four things, and neither tool is the wrong answer. Hosting comes first: n8n runs self-hosted with Docker or npm, or on n8n Cloud, while Make is a hosted platform with no self-hosting option. Data control follows from that, since a self-hosted instance keeps article content on infrastructure you own. The cost model differs too, as Make bills per operation, which matters once a publishing flow fans out across many items. Last, visual logic: both build flows on a canvas, and the right choice is usually the one your team reads faster.
Same platform

Other docs you might need on this stack.

Browse all integrations