Blog publisher channel

This pack gives an agent tools for publishing, updating, listing, cross-posting, scheduling and retrieving article analytics on Dev.to, Hashnode, Medium and WordPress through axios.

Installation

npm install @framers/agentos-ext-channel-blog-publisher

Peer dependency: @framers/agentos >=0.10.40.

Usage

import { AgentOS } from '@framers/agentos';

const agentos = await AgentOS.create({
  extensionManifest: {
    packs: [
      {
        package: '@framers/agentos-ext-channel-blog-publisher',
        options: {
          devto: { apiKey: process.env.DEVTO_API_KEY },
          hashnode: {
            apiKey: process.env.HASHNODE_API_KEY,
            publicationId: process.env.HASHNODE_PUBLICATION_ID,
          },
          medium: {
            accessToken: process.env.MEDIUM_ACCESS_TOKEN,
            authorId: process.env.MEDIUM_AUTHOR_ID,
          },
          wordpress: {
            url: process.env.WORDPRESS_URL,
            username: process.env.WORDPRESS_USERNAME,
            appPassword: process.env.WORDPRESS_APP_PASSWORD,
          },
        },
      },
    ],
  },
});

Configuration

Credentials resolve from options, then options.secrets, then environment variables. A platform is enabled by its primary credential, or its URL for WordPress.

Tools

blogPublishArticle

blogUpdateArticle

blogListArticles

blogAnalytics

blogSchedule

blogCrossPost

Channel adapter

The adapter registers platform devto. Initialization checks for configured platforms and marks the adapter connected. Sending publishes the first text block as an article. The conversationId selects all, a platform name or comma-separated platform names. platformOptions accepts title, tags, published, coverImage, canonicalUrl and series; the title defaults to Untitled. The adapter does not receive events.

Notes

Publishing, updating, cross-posting and scheduling create or modify remote articles. Without configured credentials, activation logs a warning and skips adapter initialization. Accessing an unconfigured platform fails.

Scheduling adds an HTML comment to the body and requires a future time and an external scheduler. Hashnode uses its publish mutation regardless of published, including for scheduled articles. Its update path ignores publish status and series. Medium does not support updating or listing through this service. Analytics is restricted to Dev.to.

Cross-posting extracts raw HTML from an article, main or body element without converting it to Markdown. Source requests time out after 15000 ms. WordPress receives the body directly as content, tag strings as tags and the cover image value as featured_media. Its publish and update paths do not forward the canonical URL. Hashnode listing ignores limit. Listing all configured platforms discards failed platform results; publishing returns per-platform errors.

Releases

New versions are published from framerslab/agentos-extensions by GitHub Actions through npm trusted publishing, with a provenance statement.

License

Apache-2.0