Hashnode settings
Hashnode publishes articles, so the post’s content is the article body in Markdown.
Fields
Section titled “Fields”| Field | Required | Description |
|---|---|---|
title |
Yes | The article title. At least six characters, longer than most providers require. |
publication |
Yes | The publication id to publish into. |
subtitle |
No | The article subtitle. At least two characters when present. |
main_image |
No | Cover image, as a media object with id and path. |
canonical |
No | Canonical URL, when published elsewhere first. Must be a valid URL when present. |
tags |
Yes | Array of { "value": "...", "label": "..." } objects, where value is the tag’s id from Sharek’s built-in list of Hashnode tags and label its name. At least one is required. |
Example
Section titled “Example”"settings": { "title": "What we learned shipping in public", "subtitle": "Six months of building Sharek in the open", "publication": "publication-id", "main_image": { "id": "media-id", "path": "https://media.example.com/cover.png" }, "tags": [ { "value": "56744721958ef13879b94cad", "label": "JavaScript" } ]}Finding tag ids
Section titled “Finding tag ids”A tag’s value is its id, not its name or its slug. Sharek turns each id into the tag Hashnode
expects, so a value that is not on its list, such as startups, matches no tag. Call
trigger a channel tool with the tag-listing tool that
channel settings reports for the Hashnode channel: each
entry’s objectID is the value to send, and its name the label.
- Hashnode is the only provider that requires at least one tag.
- The six-character minimum on
titlecatches short titles that pass everywhere else. - Hashnode channels are connected with an API key you supply rather than a redirect.
Send these under settings in create a post. Read a channel’s live
schema with channel settings. Connect the channel first:
connecting your channels.