Hashnode
Live
Hashnode is a syndication target: the copy lives on a domain you do not own. BirchSeek publishes there only once the article is live on your own site, and sends that URL as Hashnode's originalArticleURL.
What BirchSeek does
- Refuses to run without a live URL on your own site, and sends it as originalArticleURL on every post
- Publishes into the Hashnode publication you name, with the title, subtitle, markdown body and up to five tags
- Reads the GraphQL response body rather than the HTTP status, because Hashnode answers 200 even when the request failed
- Asks the publication for your slug before creating anything, and updates that post in place when it exists
- Dates the post with the publish date you approved, unless you turn on Stamp as now
Setup
Check that the account has Hashnode Pro
Since May 2026, Hashnode's GraphQL API requires a Hashnode Pro subscription for both reading and publishing. Without it the connection test fails saying so, rather than letting you find out at the first scheduled publish.
Generate a Personal Access Token
In Hashnode, open Account Settings → Developer → API tokens, generate a token and copy it. It is sent as a raw Authorization header, with no Bearer prefix, which is Hashnode's own convention.
On screen: Hashnode's Developer settings with an API tokens section and a newly generated token string.
Enter the publication id and check access
Your publication id identifies which blog to post into; it is in your Hashnode dashboard under the blog's settings. BirchSeek authenticates, echoes the id back so you can confirm it, and reports the account it connected as. The check does not create a post.
On screen: The connector form with the token and publication id fields, and a Stamp as now switch that is off by default.
Hashnode has no draft mode on its publish mutation, so posts go live when BirchSeek publishes them. If you want a review step, use the pipeline's approval gates - which is where that decision belongs anyway.
Start with BirchSeek.
30 cited articles a month.