Hashnode
Ship your articles to Hashnode as soon as they go live
Keep writing on your LookMyBio blog. Each post you pick reaches your Hashnode publication in Markdown, code blocks and players intact, already marked as a republished piece.
Pick Hashnode alongside your other connected blogs on any post, from Starter.
- Connect with an access token
- Sent as Markdown
- Canonical URL to your post
- Up to 5 tags
- Later edits sent on request
The blog editor in the app with a post by Estúdio Norte, a brand studio: cover, title, subtitle and text. Then its Cross-post window, sending the post to each of the blog's destinations one after another.
Your developer audience reads on Hashnode
Republishing a tutorial there by hand means reformatting the Markdown, checking every code fence, re-adding the video and digging through the article settings to say where it first ran.
Your digital presence doesn't have to be this fragmented
LookMyBio brings the whole flow into one platform, so you produce in a more organized way and stay in control of what gets published.
How it works
Generate a token
On Hashnode, open your account settings, go to Developer and create a personal access token.
Choose the publication
Then add that token on LookMyBio, where your blog keeps its destinations. If the account runs several publications, pick the one that should receive posts.
Select Hashnode on a post
Tick Hashnode in the Cross-post window. Hashnode receives the article at the moment your post publishes, or once its scheduled slot arrives.
A personal access token, nothing more
Hashnode's API works with a token tied to your account, so you never hand over a password. Delete the token in Hashnode's developer settings and the connection stops working.
- Hashnode now asks for its own Pro plan on the publication before its API accepts posts; without it, the Cross-post window tells you so
- Hashnode has no draft option here: the copy is published right away
Markdown that Hashnode reads natively
The article goes over as Markdown. Players from YouTube or X are written in Hashnode's own embed syntax, so it renders as a player, and links that are not players stay plain links. Hashnode keeps up to 5 tags per article; extra ones are dropped.
- Your cover image becomes the Hashnode cover
- Title and subtitle are carried over
Marked as a republished article
Hashnode has a field for the address where an article first appeared. Your post's URL goes into it, which sets the canonical link and tells search engines the original lives on your blog.
- The article body stays as you wrote it, with no line added at the end
Update the Hashnode copy after a fix
Once you revise your own post, the Cross-post window lists the Hashnode article as behind. Push the update and Hashnode gets the new text, tags and cover.
- Comments left on Hashnode show up in your comments inbox, read only
- To answer or moderate one, the inbox links you to the article on Hashnode
The blog editor in the app with a post by Estúdio Norte, a brand studio: cover, title, subtitle and text. Then its Cross-post window, sending the post to each of the blog's destinations one after another.
Tutorials for readers in other languages
Have a published tutorial translated into a linked draft for readers of another language; after you check it, Hashnode gets that version as a separate article.
Hashnode at a glance
| Connect with | A personal access token from developer settings |
|---|---|
| Sent as | Markdown, players in Hashnode's embed syntax |
| Tags | Up to 5 |
| Original credit | The original article URL field on Hashnode |
| Drafts | Not offered: copies are published live |
| Later edits | Delivered once you push them |
| Comments | Visible in the inbox; replies on Hashnode |
| Plan | Starter or above, starting at $27 a month |
Hashnode questions
For developers who keep a publication on Hashnode.
Keep your Hashnode publication current
Paste a token once, choose the publication, and send each finished article there with its origin recorded.