Getting started

Understand the CRISP Content Engine model, core concepts, and the content lifecycle.

This page explains how CRISP Content Engine is structured, what the major concepts mean, and how content moves from generation to publishing.

Who this page is for

New customers onboarding to CRISP Content Engine
Operators setting up integrations (Airtable, Make.com, publishing connections)
Anyone who needs a clear mental model before using the app

Core concepts

Brand profile: The workspace context for content (voice, audience, goals).
Strategy: The durable “source” CRISP uses to generate a month of content.
Content queue: Where drafts arrive for human review and scheduling.
Native publishing: CRISP publishes to a platform via API, triggered by cron.
Export-only: CRISP provides content and copy tools; you publish manually.

Content lifecycle

Generate → drafts are created via Make.com scenarios using your strategy.
Review/Approve → content is edited, approved, and optionally scheduled.
Publish → cron workers publish due items for supported platforms.
Observe → statuses and errors are surfaced so you can remediate quickly.

Native publishing vs export-only

Native publishing (cron-based): LinkedIn, Meta (Facebook + Instagram) on Growth tier and above.
Export-only (copy/paste): 𝕏, Blog.

Export-only platforms

Export-only means CRISP does not publish to the platform API yet. You’ll see copy buttons and clear guidance in the UI.

Publishing model: Publishing overview
Content system internals: Content system
Security & privacy: Security & privacy

CRISP Content Engine Docs

The premium, technical documentation hub for CRISP Content Engine — generate, approve, publish, and learn.

Publishing overview

How CRISP Content Engine schedules and publishes content — and where each platform currently sits.