Medium Node: "Forbidden - perhaps check your credentials?" after update

[smdogar]

Hi everyone!

I am running into an error in my workflow and was hoping someone might be able to help me.

I am using the Medium node in n8n (self-hosted). The integration token is correct—I have verified it multiple times. The workflow used to work fine earlier, but after updating n8n, it suddenly stopped working.

I tested the same integration token in Make.com, and it works there without any issues.

I am getting the following error message:
Forbidden - perhaps check your credentials?

Information on my n8n setup

• n8n version: 1.83.2 (Self-hosted)
• Node type: n8n-nodes-base.medium (Version 1 - Latest)
• Database: SQLite
• Running n8n via: Docker
• Operating system: Debian

Any help would be appreciated! Thanks in advance.

[ThinkBot]

Hey, could you ctl a, ctl c on your entire workflow, and click the ‘</>’ button in the forums response and paste the workflow between the backticks that appear?

That would help give some more context on what is happening.

Do you mind sending a screenshot of the creds page as well (blue/remove half of keys tho)

[smdogar]

Yes ofcourse!

Here is the workflow:

I am connecting to my Medium account through an integration token. This token was working fine earlier but then suddenly stopped working. It is still working on make.com though.

Here is a picture of the credentials page:

Additionally, I get the following error everytime. Seems like cloudflare is blocking my access to Medium through n8n.

[smdogar]

Forgot to add picture of the error:

It’s not letting me copy/paste the error unfortunately.

[ThinkBot]

Medium only has an access token? Interesting.

The error leads me to believe the URL the medium node is trying to access doesnt exist or is wrong.

Does creating a request via HTTP node work with the access token instead?