Publishing to Your Own Blog

The rest of this Social Media category is about the nine social networks Sarudo can post to through Publer (LinkedIn, X, Facebook, Instagram, TikTok, YouTube, Pinterest, Threads, Google Business Profile). This article is about the thing that sits next to those: your own blog. Social posts and blog posts are different in shape (short vs long-form), different in audience (feed-scrolling vs intentional readers), and different in the infrastructure they ship through. Publer handles the networks; a separate CMS publishing path handles your blog. They coexist — a single content strategy typically produces both, with blog posts being the longer-form anchor content and social posts driving traffic to them.

Sarudo ships with adapters for the common blog CMSes: WordPress (REST API + Application Password), Ghost (Admin API + JWT), Webflow (CMS Collections + bearer token), Shopify (Admin API + access token), and Framer (via webhook). For any CMS not in that list — Notion-backed blogs, custom Next.js setups, self-hosted platforms — the custom-webhook adapter lets you point the publisher at your own HTTPS endpoint with a documented JSON payload shape and handle the platform-specific logic inside your own code.

Blog publishing goes through a single dispatcher pattern regardless of CMS. Your AI employee hands the final article (structured sections, hero image, metadata) to an n8n workflow named `client-blog-publish-<cms>`, which owns the CMS-specific authentication and POST shape. The workflow returns the final published URL and the platform-specific post ID, which Sarudo stores alongside the article for future reference ("show me the link to the launch announcement post" works even months later). You provide the CMS URL, the auth credentials, and the CMS type during onboarding or when the first publish request fires — the credentials live in `/var/lib/sarudo/config/client-blog.env` on your dedicated server.

A common pattern is to publish a blog post and immediately cross-promote it on social. Your AI employee can chain these together in a single request — "publish this post to my blog, then draft three social posts for LinkedIn, X, and Instagram that tease the article and link to the final URL". The blog post fires first; once the final URL is returned, the social posts are drafted with the real URL embedded, and they enter the standard approval workflow before going out through Publer. This keeps the two systems cleanly separated while letting the AI orchestrate them in the right order.

If you are on a CMS without a built-in adapter, or if you want to keep publishing logic on your own infrastructure, the custom-webhook path lets you define your own publish endpoint. Sarudo sends a POST with a JSON payload containing title, slug, content (as structured sections with heading/paragraph/list/quote/image types), excerpt, tags, hero image URL and attribution, author name, and an optional publish_at timestamp. Your endpoint handles the platform-specific insertion and returns `{post_url, platform_id}` on success. Full payload shape is documented in the Content Calendar Pipeline > Supported CMS Targets article.