Configuration
| Field | Description |
|---|---|
operation | create, update, delete, or create_or_update. |
template_id | The document template. |
document_id_or_slug | A field mapping locating the document (required for update/delete/upsert). |
contact | The owner contact — required for every operation (document slugs are unique per contact). |
field_mappings | The attribute values. |
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. |
The document’s required attributes are only enforced on
create and upsert — an
update that only touches taxonomies, tags, or ownership saves without filling them in.Taxonomies, tags and ownership
Besides its attribute values, the action can manage the document’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 document 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 — all shapes are flattened to identifiers.
- 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.
When the document template’s ownership mode
is Sync with contact, ownership adds are skipped on
create — the new document
inherits its contact’s ownership — and the run detail marks the section as skipped.
Ownership changes on update apply normally.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
Documents
The records this action manages.
Document creation
The contact-side create equivalent.