Skip to main content
Hashnode
Hashnode moved its GraphQL API onto a paid plan on 13 May 2026. Their changelog entry states that the Pro plan now covers both sides of the API: “Queries against your publication now require Pro, the same as publishing.”PostQueen reaches Hashnode through that API and nothing else, once to connect the channel and once for every article. So a publication without Pro is a publication she cannot publish to. Hashnode says the upgrade is self-serve from your blog dashboard, under Billing.

​
What she can post to Hashnode

Hashnode wants a home for every article before it will take one. You pick the publication in the settings panel, she attaches the title, the tags and the Markdown, and the piece lands on that blog under your name. Ten thousand characters is the ceiling, which is generous for an essay and tight for a book chapter.

Character limit

10,000 characters. The editor is Markdown.

Media

One cover picture. She sends it as a web address and Hashnode fetches the file itself.

Post types

One article in one publication. A title, a subtitle and tags, with a cover picture and a canonical link if you want them.

Analytics

None. Ten connectors report numbers back to her, and Hashnode is not one of them.
Two things catch people out.
  • A cover picture has to be reachable from the public internet. She does not upload the file to Hashnode. She sends a URL, built from your NEXT_PUBLIC_BACKEND_URL and NEXT_PUBLIC_UPLOAD_STATIC_DIRECTORY when the picture lives on your own instance, and Hashnode fetches it from the outside. That second variable falls back to uploads when you leave it unset. A PostQueen running on localhost or behind a private network serves an address Hashnode cannot open, so the article arrives with no cover.
  • She sends the first block only. The composer offers Add comment underneath the article, and Hashnode receives the first block. Anything below it goes nowhere.
One more, on the connection itself: “Invalid credentials” comes back when the token does not answer at https://gql.hashnode.com.

​
Set up Hashnode

1

Generate a personal access token

Open Hashnode developer settings and click Generate New Token.Copy the token straight away. Hashnode calls it a Personal Access Token, and it is the value that travels in the Authorization header on every call she makes.
2

Add Hashnode as a channel

In PostQueen, click Add Channel and pick Hashnode. A modal titled Add Provider opens with a single field:Press Connect. She runs a me query against https://gql.hashnode.com, and the channel lands on your dashboard with your Hashnode name and profile picture.
3

Pick a publication and write

Open a new post, select the Hashnode channel and fill the settings panel:
  • Title: required, at least six characters.
  • Subtitle: optional, at least two characters when you use it.
  • Canonical Link: optional, for a piece that lives elsewhere first.
  • Cover picture: optional, and it has to be publicly fetchable.
  • Select publication: required. She reads your first fifty publications.
  • Tags: at least one, drawn from the Hashnode tag list bundled with PostQueen.
Schedule it and walk away. Autopilot sends it at the time you set.
The channel is in the left sidebar with its avatar and name. That is the whole confirmation: if it is in the list, she can post to it.

​
Troubleshooting

  • “API key is invalid” in the connect modal: the field rejects anything under three characters. Paste the whole token.
  • “Invalid credentials” after pressing Connect: Hashnode did not accept the token. Generate a fresh one under developer settings and try again.
  • No publication picker in the settings panel: she found no publications on the account behind that token. Create a blog on Hashnode first, then reopen the post.
  • The article published without its cover: Hashnode could not fetch the address she sent. Check that your PostQueen upload directory answers on a public URL.
  • The channel connects but publishing fails: check the Pro plan on the publication you are posting to. See the note at the top of this page.