Skip to main content

​
Fill a template (content remix, same brand)

When to use: The user has a source canvas they like — usually a designed template — and wants a new canvas that keeps the structure and styling but swaps in new content. “Make this for our Q3 launch”, “fill this template with our customer story”. The original canvas is preserved.

​
Tool call

​
What the server does

The server:
  1. Copies the source canvas into the caller’s team (original untouched).
  2. Applies the resolved brand kit to the copy. When it matches the source’s brand kit (or is omitted with no session preference, so the source’s kit is preserved), the agent runs the within-team-remix skill — content-only changes.
  3. Returns a task handle for the new canvas. Poll get_task_status as usual.

​
Source canvas access

The source must be readable by the caller’s team. template_canvas_id accepts any canvas the team can read — it doesn’t need to be flagged as a template type.

​
Mutually exclusive

template_canvas_id is mutually exclusive with both canvas_id and conversation_id. Passing either combination raises a tool error.

​
Prompt notes

The agent reads the prompt as a content-edit brief over the existing layout. Be specific about what to replace (headline, body, image, data) and what to keep. If the prompt asks for a rebrand (“change everything to dark mode”) you actually want rebrand-template.md — pass a different brand_kit_id. The selector is the brand kit, not the prompt wording. Omitting brand_kit_id (or passing the source’s) is what picks the content-only path; adding “keep the existing colors” to the prompt buys nothing. Conversely, writing “rebrand this” into the prompt does not trigger a rebrand when the kit matches — pass a different brand_kit_id (rebrand-template.md).

​
See also