Create a series
Overview
Some topics are too large for one post. “What changes with e-invoicing” is not one story but five — one per hurdle. Until now that meant opening the same form five times, setting five dates and hoping the five texts fit together.
A series turns that into a single task. You describe the topic once, say how many posts you want and on which days they should appear — and get the finished plan before anything is saved.
Core tasks
1. Topic
Pick the content type, describe the topic, set the targets if needed. The more precise the topic, the less the posts resemble each other: “Six posts about our move to e-invoicing, one per hurdle” yields six different texts; “posts about e-invoicing” yields the same one six times.
2. Rhythm
Count (two to thirty), start date and the weekdays. The time of day comes from the start and applies to every date. “Mon/Wed/Fri from the third” is the default most editorial teams begin with.
3. Preview
The suggestion is written in one go so the posts build on each other: the first introduces, the middle ones each go deeper on one point, the last one closes. You then see both — the calendar and the list. In the calendar you drag single posts to another day; in the list you untick the one that does not work.
4. Take them over
“Take all n” creates the posts as drafts. All or nothing: if one entry fails, none is created, and the message names the post that is stuck. Four created and two failed posts would be the worst answer — the calendar would look full, the series would not be.
Fields in detail
The wizard writes in two places: it fetches the suggestion (POST /v1/content/ai with kind = series) and adopts it as a series (POST /v1/content/items/bulk). The fields of a single item are documented under content items; what follows steers the series. The grey name behind each label is the API field.
Step 1 — Topic
| Field | Required | Values / format | What it does |
|---|---|---|---|
Content type typeKey | yes | a configured content type | What the series consists of. All items get the same type — that is what makes them a series. The type also determines which fields an item has. |
What should the series be about? brief | yes | text, capped at 1000 characters in the wizard | The brief for the suggestion. The more precise the angle, the less alike the items: "one per obstacle" yields different texts, "about e-invoicing" yields the same one repeatedly. Without a brief the suggestion is rejected. |
Targets targets | no | channels | Where every item of the series is published. The field only appears for types that leave the target open; where the type decides the targets itself, this would be a setting that does nothing. |
Step 2 — Cadence
| Field | Required | Values / format | What it does |
|---|---|---|---|
How many posts? count | yes | 2 to 30 | How many items are suggested. Beyond that it is no longer a suggestion but an import. If the interface sends nothing, it is four. |
Language locale | no | language code, at most 5 characters | Language of all items of the series. Without it the default language applies. |
Start time and weekdays are not API fields. They are arithmetic inside the wizard: "Mon/Wed/Fri from the 3rd, 9 a.m." produces the planned publication dates, which then travel per item as plannedPublishAt. At least one weekday must be chosen; the time of day comes from the start and applies to every date. In the preview calendar each date can be dragged individually before anything is saved.
Step 3 — Adopt
| Field | Required | Values / format | What it does |
|---|---|---|---|
The ticked items items | yes | 1 to 30 entries, each with fields and plannedPublishAt | What is actually created — as drafts, not as publications. Without a single tick nothing is created. All or nothing: if one entry breaks, none is created, and the message names its position. |
Interface and automation only
| Field | Values / format | What it does |
|---|---|---|
brandId | one of your brands | Brand of the series. It decides which instruction, which budget and which storage apply to the suggestion — and it requires the write permission in that brand. The wizard does not send the field; without it the series is created without a brand. |
categories | categories | Categories for every item of the series. Not set in the wizard; through the interface they apply to the whole batch. |
kind | draft · series · seo · image | Which kind of suggestion is fetched. The series wizard always sends series; the other kinds belong to the single content item. |
itemUlid | an item | Only for kind = seo: the item for which search-engine details are suggested. |
size | 1024x1024 · 1024x1536 · 1536x1024 | Only for kind = image: the edge size of the generated image. |
Without an active AI the answer comes back empty with a note that no AI is active — not an error. The series can then still be written by hand.
Settings & permissions
- You need the write and plan posts permission (
content.item.manage). That does not publish the
series; publishing is a separate step with its own permission.
- The suggestion requires AI to be set up. Without it the page says so plainly — and you can still
write the series by hand.
- Header data applies to the whole series: content type, language, brand, targets and categories.
That is what makes the posts a series.
FAQ & troubleshooting
All posts land close together. Then only one weekday is selected. The wizard lays out as many dates as there are suggested items — with a single weekday that spans several weeks, with five weekdays a single one. Going without a weekday is not possible: step two demands at least one.
The suggestion repeats itself. The topic is too broad. Name the aspect that separates the posts (“one per hurdle”, “one per region”).
“No post selected.” Every tick in the list has been removed. Without at least one tick nothing is created.
A post of the series is missing after taking them over. That cannot happen: a series is created all or nothing. If posts are missing, their tick was removed beforehand.