CMS

The CMS module manages sites, collections, entries, revisions, marketing campaigns, and marketing posts for content and go-to-market workflows.

What it does

CMS is an app-plane module for structured content operations. It supports headless CMS records and marketing planning records inside the same workspace boundary as CRM, Tasks, Assets, Activity Log, and Data & Insights.

Public capabilities:

• Create and list CMS sites.
• Create and manage content collections.
• Create, search, and update richer entries.
• Move entries through draft, review, published, and archived states.
• Create and list marketing campaigns.
• Create and list marketing posts for campaign channels.
• Keep all CMS operations tenant-scoped, audited, and available through REST and MCP.

Resource model

CMS entries use fields for content schema data and custom_fields for workspace-specific query metadata, such as persona, product area, lifecycle stage, or experiment key.

Production website delivery

Slab5 CMS REST reads are metered API reads. They are intended for builders, server-side applications, previews, content tooling, agents, and controlled publish flows.

Production websites should not fetch published CMS entries from Slab5 on every pageview. Use build-time reads, server-side caching, route-level revalidation, or a publish pipeline that writes a cached website artifact. This keeps websites fast, protects workspace usage, and avoids turning every visitor request into a CMS API request.

Recommended launch patterns:

For public marketing sites, use build-time or server-side cached reads before launch. Publish-to-CDN delivery can be added later as a separate publishing layer.

Next.js caching examples

Use a server-only CMS client and set an explicit cache policy for published content reads.

// lib/slab5-cms.ts
import 'server-only'

const SLAB5_API_URL = process.env.SLAB5_API_URL ?? 'https://api.slab5.com/v1'
const SLAB5_WORKSPACE_ID = process.env.SLAB5_WORKSPACE_ID
const SLAB5_API_KEY = process.env.SLAB5_API_KEY

export async function readPublishedEntries(query: string) {
  if (!SLAB5_WORKSPACE_ID || !SLAB5_API_KEY) {
    throw new Error('Slab5 CMS is not configured')
  }

  const url = new URL(`${SLAB5_API_URL}/cms/entries`)
  url.searchParams.set('status', 'published')
  url.searchParams.set('query', query)
  url.searchParams.set('limit', '10')

  const response = await fetch(url, {
    headers: {
      Authorization: `Bearer ${SLAB5_API_KEY}`,
      'x-slab5-workspace-id': SLAB5_WORKSPACE_ID,
    },
    next: {
      revalidate: 300,
      tags: [`slab5-cms:${query}`],
    },
  })

  if (!response.ok) {
    throw new Error(`Unable to load published CMS content: ${response.status}`)
  }

  return response.json()
}

For pages that can tolerate a fixed refresh interval, call the helper from a server component:

// app/products/page.tsx
import { readPublishedEntries } from '@/lib/slab5-cms'

export const revalidate = 300

export default async function ProductsPage() {
  const entries = await readPublishedEntries('products')
  const products = entries.data?.[0]?.fields?.products

  return <ProductsView products={products} />
}

For content that should refresh immediately after publish, add a protected revalidation route in the website and call it from the publish workflow:

// app/api/revalidate/route.ts
import { revalidateTag } from 'next/cache'
import { NextResponse } from 'next/server'

export async function POST(request: Request) {
  const secret = request.headers.get('x-revalidate-secret')
  if (secret !== process.env.REVALIDATE_SECRET) {
    return NextResponse.json({ error: 'unauthorized' }, { status: 401 })
  }

  const { tag } = await request.json()
  revalidateTag(tag)

  return NextResponse.json({ revalidated: true })
}

Set downstream response caching for server-rendered routes where appropriate:

export async function GET() {
  const body = await renderCachedContent()

  return new Response(body, {
    headers: {
      'content-type': 'text/html; charset=utf-8',
      'cache-control': 'public, s-maxage=300, stale-while-revalidate=3600',
    },
  })
}

Keep the Slab5 API key on the server. Do not expose workspace API keys in browser JavaScript.

Marketing workflow

A marketing/content agent can run a launch workflow:

1. create_marketing_campaign for the launch or customer cohort.
2. create_cms_site if the site does not exist yet.
3. create_collection for the content type.
4. create_entry for the draft page, post, or case study.
5. create_asset_upload_intent for images, PDFs, or video attachments.
6. create_marketing_post for LinkedIn, email, blog, or changelog distribution.
7. log_activity to preserve planning and publish activity.
8. create_bi_dashboard or run_bi_query for campaign tracking when the Data & Insights module is enabled.

Permissions

Use cms:read to list sites, campaigns, posts, and search entries. Use cms:write to create or update CMS resources.

Recommended scoped agent credentials:

cms:read
cms:write
assets:read
assets:write
activity:write
bi:read
bi:write

MCP tools

{
  "name": "Blog Posts",
  "key": "blog_posts",
  "schema": {
    "fields": [
      {
        "key": "title",
        "type": "string",
        "required": true
      },
      {
        "key": "slug",
        "type": "string",
        "required": true
      },
      {
        "key": "body",
        "type": "markdown",
        "required": true
      }
    ]
  }
}

{
  "collection": {
    "id": "col_123",
    "key": "blog_posts",
    "name": "Blog Posts"
  },
  "request_id": "req_135"
}

{
  "key": "slab5_com",
  "name": "slab5.com",
  "primary_domain": "slab5.com"
}

{
  "site": {
    "id": "site_123",
    "key": "slab5_com"
  },
  "request_id": "req_212"
}

{
  "limit": 10
}

{
  "sites": [
    {
      "id": "site_123",
      "name": "slab5.com"
    }
  ],
  "request_id": "req_213"
}

{
  "collection_id": "col_123",
  "title": "AI follow-up workflows",
  "status": "draft",
  "fields": {
    "slug": "ai-follow-up-workflows",
    "body": "Draft content..."
  }
}

{
  "entry": {
    "id": "ent_123",
    "collection_id": "col_123",
    "status": "draft"
  },
  "request_id": "req_136"
}

{
  "query": "follow-up",
  "status": "draft",
  "limit": 10
}

{
  "entries": [
    {
      "id": "ent_123",
      "title": "AI follow-up workflows",
      "status": "draft"
    }
  ],
  "request_id": "req_137"
}

{
  "entry_id": "ent_123",
  "status": "review"
}

{
  "entry": {
    "id": "ent_123",
    "status": "review"
  },
  "request_id": "req_138"
}

{
  "entry_id": "ent_123",
  "title": "AI follow-up workflows",
  "fields": {
    "slug": "ai-follow-up-workflows",
    "body": "Updated draft content..."
  },
  "status": "review"
}

{
  "entry": {
    "id": "ent_123",
    "title": "AI follow-up workflows",
    "status": "review"
  },
  "request_id": "req_138"
}

{
  "key": "slab5_beta_launch",
  "name": "Slab5 beta launch",
  "channel": "website"
}

{
  "campaign": {
    "id": "camp_123",
    "key": "slab5_beta_launch"
  },
  "request_id": "req_214"
}

{
  "status": "active"
}

{
  "campaigns": [
    {
      "id": "camp_123",
      "name": "Slab5 beta launch"
    }
  ],
  "request_id": "req_215"
}

{
  "channel": "linkedin",
  "title": "Beta launch",
  "body": "We are opening Slab5 private beta."
}

{
  "post": {
    "id": "post_123",
    "channel": "linkedin"
  },
  "request_id": "req_216"
}

{
  "channel": "linkedin",
  "status": "draft"
}

{
  "posts": [
    {
      "id": "post_123",
      "channel": "linkedin"
    }
  ],
  "request_id": "req_217"
}