Hashnode — how to connect

Before you start

• A Hashnode account with at least one publication (blog) already created — the adapter calls the `me` query and auto-selects your first publication; if no publication exists yet, connect fails outright ('No publication found on this account').
• A Personal Access Token generated at hashnode.com/settings/developer ('Generate New Token') — this is account-level, not OAuth, and is the only auth method this integration supports.
• If you run multiple publications/teams, the Publication ID of the specific blog you want to post to (from the blog's dashboard URL) — otherwise the tool silently defaults to whichever publication comes back first, which may not be the intended one.
• Content prepared as Markdown text only — this adapter is text/Markdown-only (no cover image, tag, or series fields wired up), so anything requiring media upload at publish time isn't supported yet.

Step by step

1. 1
   Log in to Hashnode

   Sign in at hashnode.com with the account whose publication you want to publish to.

   Open
2. 2
   Open Developer Settings

   Go to hashnode.com/settings/developer, the account-level page for API tokens.

   Open
3. 3
   Generate a new token

   Click "Generate New Token", give it a label, and copy the token value immediately (it is shown only once).

4. 4
   Confirm you have a publication

   Make sure the account has at least one Hashnode publication (blog); the app uses the first one automatically if you don't supply a Publication ID.

5. 5
   Paste the token into the app

   In the Hashnode connect form, paste the token into "Personal Access Token"; leave "Publication ID" blank to auto-use your first publication, or fill it in with a specific publication's ID (e.g. 64xxxxxxxxxxxxxxxxxxxxxx) if you have more than one.

Paste when you connect

• Personal Access Tokensecret
• Publication ID (optional — first publication used if blank)

Troubleshooting

Connect fails with 'Hashnode token did not resolve a user (invalid PAT?)' or an unauthorized/401-style GraphQL error even though the token was pasted correctly.

Hashnode's endpoint expects the raw PAT in the Authorization header with NO 'Bearer ' prefix. If you generated the token through a copy-paste that added quotes/whitespace, or regenerated the token on hashnode.com/settings/developer (old tokens are invalidated immediately), re-copy the exact raw token and reconnect.

Connect succeeds but publish fails with 'Account has no Hashnode publicationId' or posts land on the wrong blog.

The tool only auto-picks your FIRST publication at connect time. If you own/co-author multiple publications (or the token belongs to a team member, not the owner), explicitly set the Publication ID field (copy the ID from the target blog's dashboard URL) before connecting, or reconnect after adding it.

publishPost mutation returns a GraphQL error like 'You are not the owner of this publication' or a permission/authorization error on the input.

The PAT's user must actually be a member (owner or editor) of the target publicationId — a token generated on a personal account cannot publish into a team publication you're not added to. Add the user as a contributor on that Hashnode publication first, then retry.

Frequent publish/edit calls start failing or timing out, especially when bulk-publishing or retrying quickly.

Hashnode's GraphQL endpoint (gql.hashnode.com) sits behind the Stellate edge cache/rate-limiter, so bursts of requests can get throttled. Space out retries and back off rather than hammering the endpoint immediately after a failure.