Configuration
| Field | Description |
|---|---|
operation | create, update, delete, or create_or_update (upsert). |
content_type | The instance type (e.g. stories, products). |
template_id | The content template to use. |
instance_id_or_slug | A field mapping locating the instance (for update/delete/upsert). |
instance_fields | Instance-level fields — title, slug, description, parent_id, and hierarchy fields. |
version_fields | The content (attribute) values for each version. |
version_matrix | The { language, environment } combinations to create/update. |
auto_publish | Publish each version after writing it. |
taxonomies / tags | Add/remove lists of taxonomy or tag references — see Taxonomies, tags and ownership. |
ownership | Add/remove lists of { user, role } entries — see Taxonomies, tags and ownership. |
On
create_or_update, when the instance isn’t found and the locator is a slug, that
slug becomes the new instance’s slug.Taxonomies, tags and ownership
Besides its fields, the action can manage the instance’s Taxonomies, Tags, and ownership. Each of the three sections takes an add list and a remove list of field mappings, with strict add/remove semantics:- Entries already on the instance that the action doesn’t name are always preserved — the lists are never replaced wholesale.
- On
createonly the add lists apply; remove lists are available onupdateand upsert. Removing an entry that isn’t present is a no-op.
- Each entry may resolve to a single id or slug, a list of them, or objects copied from the run context (for example, another record’s taxonomies) — all shapes are flattened to identifiers.
- Taxonomy values are validated against the template’s allowed taxonomies, exactly as when editing the instance by hand; the configuration picker only offers that allowed list.
- Ownership entries are
{ user, role }, withroleeitherownerorfollower(defaultowner). The user can be referenced by id or email. Adding a user who is already on the list updates their role instead of duplicating it; archived users can’t be added. - Ownership doesn’t apply to taxonomy instances, which never carry an ownership list — the section is hidden for that content type.
relations summary of what was added, removed, or had
its role updated, readable from later nodes in the flow. The same summary appears in
each run’s node detail as Taxonomies, tags & ownership changes, with ids resolved
to user emails and taxonomy/tag slugs.
Related
Content Instances
The records this action manages.
Content Templates
The blueprint each instance uses.