Append a flow to a workspace
add_to_workspaceAppends a new self-contained flow of blocks and links to an existing workspace without altering its current content. Use it to add flows safely; the server assigns non-colliding ids.
Instructions
APPENDS a self-contained flow (new blocks + links among them) to a workspace WITHOUT touching its existing blocks — the SAFE way to add to a workspace that already has content. Unlike set_workspace_content it cannot wipe existing flows and needs no read-modify-write: the server assigns fresh non-colliding ids and lays the new flow out below the existing blocks. Links here may only connect your NEW blocks to each other; to wire INTO an existing block, use get_workspace_content + set_workspace_content instead. Returns the added blocks with their assigned ids + signalRGuid. zones adds new canvas areas alongside the flow; an id that already exists is kept as it is, so appending cannot redefine somebody else's zone either.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workspaceId": "<workspaceId>",
"blocks": "<blocks>"
},
"name": "add_to_workspace"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| seo | No | How much to report about the HTML pages being written: "full" (default) everything, "minimal" only what an indexed page cannot do without, "none" to say nothing. Never blocks the write; a page with <meta name="robots" content="noindex"> is exempt either way. | |
| files | No | New code files to add (existing names are kept, not overwritten). | |
| links | No | ||
| zones | No | New canvas areas (an id that already exists is kept, not redefined). | |
| blocks | Yes | ||
| workspaceId | Yes |