
Strapi (CMS) integration
Publish posts not only to social media but straight into your Strapi CMS — into the right collections (content types).
1What it gives you
Strapi is a popular headless CMS. Connecting it as an integration gives you destination “channels” for posts, just like Telegram:
- 🗓️ Approved posts are created on schedule as entries in the chosen Strapi content types (e.g. the “posts” collection).
- 🧩 You can publish into several collections at once.
- 📣 And even into different sub-types (categories) of one collection.
Strapi channels are listed and managed in «Каналы».
2Step 1. Create an API token in Strapi
In the Strapi admin:
- Settings → API Tokens → Create new API Token.
- Grant the token write access (create entries) to the needed collections — access type
Full access, orCustomwithcreatefor your types. - 🔒 Copy the token right away — it’s shown once.
3Step 2. Add the integration
- ➕ “Add” → choose “Strapi integration”.
- Enter your Strapi URL (e.g.
https://cms.example.com) and the API token from step 1. - Click “Check connection”.
🔒 The token is stored encrypted.
4Step 3. Pick content types
Enter the collections’ API ids comma-separated — exactly as they appear in the REST API path: for the /api/posts endpoint that’s posts. From there the service figures it out:
- 🔍 Reads a few entries from these collections and detects their fields.
- 🧠 With the model, suggests which field is the title and which is the body.
- 🧩 Finds a sub-type/category field (e.g.
typeorcategorywith valuesnews/blog/wiki). - 📝 Finds a media field for the image (cover/image).
In the collection card pick the image field (or “— don't upload —”): then each post's image is uploaded to Strapi and linked to the entry. Check the types you need (and optionally specific sub-types — one channel per checked value). Confirming creates channels in the system.
5Why you name the collections manually
It’s a Strapi limitation: a regular API token can’t list content types (that’s admin-only). So you name the collections yourself, and the service reads their fields via REST.
If a collection can’t be read, check:
- 📝 The name (exactly as in
/api/…). - 🔗 The Strapi URL.
- 🔒 The token’s read/write rights.
6How posts are published
From there it’s as usual: posts are prepared and approved in «План и очередь постов», and at the scheduled slot the service publishes them to Strapi:
- 📝 Creates an entry (
POST /api/<collection>) with the title and body in the chosen fields; if a sub-type is set, with its value. The entry is created already published. - 📣 If a media field is set, the post image is first uploaded to the media library (
POST /api/upload) and then linked to that field of the entry.
If no media field is selected or the upload fails, the entry is still published — just without the image.
Didn't find an answer? Write to us — we'll help.
Contact support