Hashnode

Syncs your developer blog activity to your CRM, automates comment moderation, and distributes your technical posts across other social channels the moment they go live.

Try Hashnode in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Hashnode integration

    • Describe the outcome and Ceven picks the right Hashnode calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Hashnode data, across all 67 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Hashnode access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Hashnode, when, and on whose behalf.
    • The agent pauses and asks when Hashnode is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Hashnode.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Hashnode action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Hashnode, and when to use it.

Accept publication invite
Use this when you have a valid invite token and want to join a specific publication.
Add reply
Post a reply to an existing comment after you have confirmed the comment ID.
Check domain availability
Verify if a custom domain is available for mapping to your Hashnode publication.
Fetch invitations
Pull a list of pending publication invitations for a team managed account.
Fetch popular tags
Pull a paginated list of trending tags to identify high traffic technical topics.
Fetch publication posts
Pull a paginated list of all posts from a specific publication host.
Fetch series posts
Retrieve all posts belonging to a specific series within a publication.
Fetch single article
Pull the full content and metadata of a specific post using its slug.
Fetch user details
Pull public or authorized profile information for a specific username.
Get publication info
Pull the ID, title, and about section of a publication using its hostname.
Add comment
Post a new comment to a story using the story ID and content.
Fetch stories feed
Pull the global home feed of stories with optional filters applied.
Hashnode Accept Publication Invite
Tool to accept a publication invitation. Use when you have a valid invite token and want to join the publication.
Hashnode Add Reply
Tool to add a reply to an existing comment. Use after confirming comment ID and reply content.
Hashnode: Check Custom Domain Availability
Tool to check if a custom domain is available for your Hashnode publication. Use when verifying domain mapping before setup.
Hashnode: Fetch Invitations
Tool to fetch pending publication invitations. Use when you need to list current pending invites for a team managed publication before taking further actions.
Hashnode: Fetch Popular Tags
Tool to fetch a paginated list of popular tags. Use when you need to browse popular tags page by page.
Hashnode: Fetch User Details
Tool to fetch detailed user profile information by username. Use when you need public or authorized profile data.
Get Publication by Hostname
Tool to fetch details (id, title, about) of a publication by hostname. Use when you need metadata for a given publication host. Example: 'blog.developerdao.com'.
Hashnode Add Comment
Tool to add a comment to a Hashnode post. Use after obtaining story ID and content, optionally provide a parent comment ID for replies.
Hashnode: Get Current User
Tool to retrieve details of the currently authenticated user. Use after confirming authentication.
Hashnode: Like Reply
Tool to like a reply on Hashnode. Use when you have a reply ID and want to add a like to that reply.
Hashnode: List Publications
Tool to list all publications of the authenticated user. Use when you need your publication hostnames for downstream actions.
Hashnode Remove Reply
Tool to remove a reply from a comment. Use after confirming comment and reply IDs. Returns the removed reply details.
Hashnode Update Comment
Tool to update an existing comment on a Hashnode post. Use after preparing updated content details.
Hashnode Update Reply
Tool to update a reply. Use when editing an existing reply to a comment after confirming the comment and reply IDs.

26 actions · scroll to see them all

Frequently asked questions

Ceven connects to Hashnode using a secure API token provided by the user. When you add your token, we store it in an encrypted vault that is isolated from other users. The agent only uses this token to make requests to the Hashnode GraphQL API on your behalf. You can rotate your token at any time within the Hashnode settings page, and updating it in Ceven immediately restores access. We never share this token with any third party or use it for any purpose other than executing the workflows you have explicitly defined in the composer.
Yes, the agent can create drafts or publish posts if the authenticated user has the required permissions for that publication. You can set up a workflow that takes a markdown file from GitHub or a doc from Notion and pushes it directly to Hashnode. We recommend setting these to draft mode first so you can review the formatting and tags before they go live to your audience. This allows you to maintain a consistent publishing schedule while using AI to handle the initial upload and metadata tagging process.
Hashnode uses a GraphQL API which implements pagination for lists of posts and comments. Ceven handles this pagination automatically by walking the cursors until it finds the data you requested. However, you should be aware that Hashnode imposes rate limits on their API to prevent abuse. If you attempt to sync thousands of posts in a single second, you may encounter a 429 Too Many Requests error. Ceven includes built in retry logic with exponential backoff to handle these limits gracefully without failing your workflow.
Yes, as long as the API token you provide has access to those publications. The agent can list all publications associated with your account and then perform actions on a per hostname basis. You can build a workflow that cross posts content across different blogs or aggregates comments from multiple sources into a single dashboard. Just specify the hostname in your prompt, and the agent will route the request to the correct publication ID using the Get Publication by Hostname tool.
The agent can distinguish between a top level comment and a reply. When using the Add Reply tool, the agent requires a parent comment ID to ensure the response is nested correctly. This allows you to build complex moderation bots that can follow a conversation thread and provide contextually relevant answers. If a parent ID is not provided, the agent will default to creating a new top level comment on the story, which is useful for general feedback or high level summaries.
Ceven can poll the stories feed or your specific publication posts at regular intervals to detect new activity. While Hashnode does not provide a push based webhook for every single action, you can set up a scheduled Ceven workflow to check for new comments or posts every hour. The agent then compares the current state with the last known state stored in the workflow memory and triggers an alert or action only when new content is detected, effectively mimicking a real time notification system.
The agent can check if a domain is available using the Check Custom Domain Availability tool, but the actual DNS mapping and final verification must be done within the Hashnode dashboard for security reasons. This is a hard limitation of the Hashnode API to prevent unauthorized domain hijacking. The agent can guide you through the process by providing the necessary CNAME or A records you need to add to your DNS provider, but it cannot programmatically finalize the domain ownership transfer.
If a post is deleted, any subsequent attempt by the agent to fetch that article by slug will return a not found error. If you have a sync workflow running, Ceven can detect this missing record and trigger a cleanup action in your downstream systems, such as removing the link from a CRM record or updating a content calendar. This ensures that your internal data stays in lockstep with your live blog and you do not send users to broken links.

Alternatives to Hashnode

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Dev.to logoDev.toMedium logoMediumGhost logoGhost

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Hashnode and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free