Skip to content

UpdateJourneyInput ​

Type: Input

Patch input for updateJourney — every field is optional and an omitted field leaves that aspect of the journey unchanged. The journey is identified by the mutation's id argument, not by this input.

Fields ​

NameTypeDefaultDescription
definitionStringA replacement definition (verbatim JSON document, spec schema 2). Omitted leaves the current version untouched; provided replaces the open draft, or opens a new draft over the published version. The journey's handle is never reassigned, even if the document's id differs.
scopeJourneyScopeNew distribution scope. Omitted leaves the journey's current scope. Moving a journey out of PERSONAL requires journey:write; a PERSONAL journey can only ever be touched by its owner.
teamIds[TeamID!]Team TypeIDs (prefix tea) to assign when the resulting scope is TEAM. Patch semantics: omitting it leaves existing assignments untouched (unlike upsertJourney, which always replaces them). Each must belong to the caller's tenant.

Connect machines, automate workflows, and build custom apps for print production.