← All integrations

Publishing integration

Publish to Strapi

Publishes to any Strapi content type via REST, field-mapped to your schema.

How it works

Publishes through Strapi's REST API using an API token. Every Strapi project's content model is different, so field names are mapped once during setup.

Before you start

  • Strapi v4 or v5, self-hosted or Strapi Cloud
  • An API token with create/publish permission on the target content type
  • The content type's plural API ID (shown in Content-Type Builder)

Setup

Three steps to connect

Step 1

Get your api token

Settings -> API Tokens -> Create new API Token, with write access to the target content type.

Step 2

Enter your site details

  • Strapi URL *
  • Content type (plural API ID) *Content-Type Builder -> open the target type -> API ID (Plural), shown in the type's settings.
  • Field map (JSON, optional)Maps our post fields to your content type's field names.

Step 3

Connect and publish

Once connected, approved posts publish straight to Strapi automatically. No export, no import, no copy-pasting into a CMS. Setup runs from your own client portal, so credentials for Strapi stay with you; the agency never has to hold or request them separately.

Troubleshooting

If something doesn’t connect

Connection test fails with a 404

The plural API ID has to match exactly, it's usually the lowercase, pluralized version of the content type name, but custom naming can differ. Check Content-Type Builder if unsure.

Posts land as drafts instead of publishing live

This only happens automatically if Draft & Publish is enabled on the content type. If it's off, every entry Strapi creates starts live-only, no explicit publish step exists.

Frequently asked questions

Yes, both are supported.

If your content type has Draft & Publish enabled, yes. Otherwise it lands as a draft for you to publish.

Field names are mapped once (title, slug, content, description by default), so a differently named schema just needs that mapping updated during setup.

Credentials are encrypted at rest and only ever used server-side to publish. Nobody, including us, can view them again once saved.

Nothing changes on Strapi itself. Everything already published stays exactly as it is. New posts just stop syncing until it's reconnected.

Still have questions? Talk to our team.

Ready to connect Strapi?

Book a call and we'll get your site's publishing integration set up together.