Hashnode setup

Hashnode is a syndication target: the copy lives on a domain you do not own, so the same canonical rule applies as for dev.to. BirchSeek will not publish here until the article is live on your own site, and it sends that URL as Hashnode’s originalArticleURL.

Before you start

Since May 2026, Hashnode’s GraphQL API requires a Hashnode Pro subscription for both reading and publishing. Without it the connection test fails with a message saying so, rather than letting you discover it at the first scheduled publish.

Step 1 - get a Personal Access Token

1. In Hashnode, open Account Settings → Developer → API tokens.
2. Generate a token and copy it.

Step 2 - find your publication id

Your publication id identifies which blog to post into. It is in your Hashnode dashboard under the blog’s settings. The connection test echoes back the id you entered so you can confirm it.

Step 3 - configure

Setting	What it does
Publication id	The Hashnode blog to publish into.
Stamp as now	On: Hashnode dates the post “now”. Off (default): the post carries the publish date you approved, so an article that waited in the queue overnight does not claim to be newer than it is.

Hashnode posts go live when BirchSeek publishes them. There is no draft option: Hashnode’s publish mutation has no draft mode, and their drafts are a separate flow that never produces a URL. If you want a review step before anything is public, use the pipeline’s approval gates, which is where that decision belongs. This differs from dev.to and Medium, which can both create drafts. Tags are sent as Hashnode expects them, as objects with a name and a slug, generated from the article’s tags.

The copy ends with a ## Sources block, the same one your own site’s article carries: each verified claim paired with the page it was checked against. The project setting that can switch that block off for your own site does not reach this copy, and deliberately so - Hashnode’s API has no citation field, so the body is the only place the evidence can travel. The canonical link back to your page goes with it.

Turn cross-posting on

Connecting Hashnode is not the same as asking for copies. Automatic cross-posting is off on every new project, and while it is off nothing is ever sent here. Switch it on under Settings → Project; it applies to every syndication connector on the project at once, and turning it back off is never refused.

Troubleshooting

• “requires a Hashnode Pro subscription” - the API is gated behind Pro. Nothing else will work until that is resolved on Hashnode’s side.
• “article must be live on your own site first” - no live URL yet. Publish to your primary connector first.
• Errors that look like successes - Hashnode’s GraphQL API answers HTTP 200 even when the request failed, with the problem in an errors array. BirchSeek inspects the body rather than the status, so a failure is reported as a failure.