Publish to Strapi from Wavefront

What it does

Approved articles go to one Strapi 5 collection type as documents, on your own server or on Strapi Cloud. They're drafts by default, or published.

Only the mapped fields are sent, so fields an editor filled in survive a revision.

Before you start

• Strapi 5 at a public https address
• A collection type with Draft & Publish turned on, for drafts
• A short text field for Wavefront's ID (recommended)

How to connect Strapi

1. In Strapi's admin panel, open Settings → API Tokens and create a token (Full access, or Custom with the permissions Wavefront lists).
2. In Wavefront, open Settings → Publishing and choose Add destination. Pick Strapi.
3. Enter the server's address and the token.
4. Choose Load fields, pick the collection type and map title, slug and body.
5. Map a short text field such as wavefrontId to Wavefront ID, so a publish whose answer was lost can find its own document.
6. Choose Test connection. Wavefront reads the fields and one document, and tells you if Draft & Publish is off.

What Wavefront sends

• Title, slug, excerpt, SEO title and description, date and canonical URL
• The body as Blocks, Markdown, or HTML for a CKEditor field
• Header and body images uploaded to the media library
• Authors, categories and tags as relations matched by name, or as text

Good to know

• Strapi 4 isn't supported.
• Scheduling isn't supported, because Strapi's Releases aren't in its REST API.
• An API token can't unpublish, so by default you take the page down in Strapi. Wavefront deletes the document on withdraw only if you choose that setting.