How to Convert a Canvas Literal Into a Resource

This guide shows you how to promote a literal node on a Canvas into a first-class Schema or Experience.

Prerequisites

Canvas must be available in your Space. See How to Check Whether Canvas Is Available in a Space.
You must be an admin of the Space. See Canvas Access.
You need a literal node on the Canvas. Deriving one is covered in How to Get Content Onto a Canvas.

Steps

Open the literal node's actions menu.
Select Convert to resource.
Select the destination folder, or leave it unset for the Space root.
Confirm.

Result: On success, the literal node is replaced in place by a reference node pointing at the new resource, the Canvas gets a new version summarised Converted <type> literal <nodeId>, and you are offered the resource's editor at:

Schema — /spaces/<spaceId>/settings/schemas/<resourceId>
Experience — /spaces/<spaceId>/settings/experiences/<resourceId>

Troubleshooting

Conversion Fails

Conversion is all-or-nothing. If it fails, no resource is created and the Canvas is not changed.

Message	Meaning
`Canvas head changed`	Someone else saved the Canvas while you were converting. Reload and retry.
`Literal candidate must be accepted before conversion`	The node has generated content that has not been accepted.
`A <type> named "<name>" already exists in this space`	Rename the literal, or the existing resource, and retry.
`Definition artifact pin is invalid`	The node points at an artifact this Space does not own.
`Invalid <Type> definition artifact`	The pinned artifact is not a valid definition of that type.
`Flow conversion requires explicit confirmation`	See above. Flow literals cannot be converted.

Limitations

Convert to resource is not offered on flow:literal nodes. Flow literals cannot be converted. If a Flow conversion is attempted anyway, it fails with Flow conversion requires explicit confirmation.
After conversion, authoring authority moves to the dedicated editor. Editing the Canvas reference node does not edit the resource, and editing the resource does not change the Canvas.
Conversion is idempotent per source node and definition artifact. Converting the same literal twice returns the same resource rather than creating a duplicate.

Canvas Conversion

Conversion turns a literal node — a definition held only as an artifact — into a first-class Schema, Experience, or Flow, and replaces the literal node with a reference node.

Canvas Editor Actions

Canvas actions are available in the Studio Canvas editor. They are not part of the public REST API or the ligantic CLI. Access rules are in Canvas Access.

How to Use Generated Content on a Canvas

This guide shows you how generated content on a Canvas is accepted, and what you can and cannot do with it.