Hashnode Automation

What This Skill Does

• The Hashnode Automation skill enables users to automate operations on the Hashnode blogging platform through Composio's Rube MCP.
• It is designed for bloggers and content creators who want to streamline their publishing workflow.
• The skill leverages Rube MCP to discover and execute Hashnode tools, requiring an active Hashnode connection.

When to Use

• Discover available Hashnode tools via Rube MCP.
• Check the connection status to the Hashnode toolkit.
• Execute a specific Hashnode tool with schema-compliant arguments.
• Automate posting new articles to Hashnode.
• Manage existing articles on Hashnode.
• Search for specific tools based on use case.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires active Hashnode connection via Rube MCP.
• Employs RUBE_SEARCH_TOOLS to find available tools.
• Uses RUBE_MANAGE_CONNECTIONS to check connection status.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow pattern for automation.

Hashnode Automation via Rube MCP

Automate Hashnode operations through Composio's Hashnode toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/hashnode

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Hashnode connection via RUBE_MANAGE_CONNECTIONS with toolkit hashnode Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit hashnode If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Hashnode operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Hashnode task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["hashnode"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference