Tree diagram
Create a top-down hierarchy tree diagram.
Send "type": "tree_diagram".
Create a top-down hierarchy tree diagram. Four categories: "sitemap" (website page hierarchy), "orgchart" (reporting structure of people/teams), "tree" (generic hierarchy: taxonomy, family tree, folder structure), "wbs" (project work breakdown structure).
Also available as the MCP tool render_treediagram. The same payload works through either surface.
Fields
titlestringA short title for the diagram, shown as the frame header (e.g. "Online Bookstore Sitemap").
categoryenum<string>Diagram flavor: sitemap (website pages), orgchart (reporting structure), tree (generic hierarchy), wbs (work breakdown). One of sitemap, orgchart, tree or wbs. Defaults to sitemap.
nodeDataobjectrequiredRoot node with id, name, root=true, category-specific fields, and children array
Child attributes
idstringnamestringurlstringsitemap only: relative page path like "/about"; root page is "/"
rolestringorgchart only: job title
departmentstringorgchart only: organizational unit
notestringtree only: short note line
ownerstringwbs only: responsible team or role; a person's name only when the user provides it
rootbooleanblocksobject[]sitemap only: page content sections
childrenobject[]Example
{
"type": "tree_diagram",
"data": {
"title": "Q4 Launch Planning",
"category": "sitemap",
"nodeData": {
"id": "string",
"name": "Q4 Launch Planning",
"url": "string",
"role": "string",
"department": "string",
"note": "string"
}
}
}
Add one record
POST /boards/{boardId}/items/{itemId}/records adds one of these to an item already on a board and leaves the rest of it as it is. Send the same key again to update that record instead of adding another.
Record fields
namestringrequiredparentstringThe node it goes under, by its name; made under the top when there is none. The top when left out.
rolestringdepartmentstringownerstringurlstringnotestringkeystringYour own id for this record, like an issue key. Sending the same key again updates and moves that record instead of adding another.
{
"record": {
"name": "Q4 Launch Planning",
"parent": "string",
"role": "string",
"department": "string",
"owner": "string",
"url": "string",
"note": "string"
}
}