update_node
Update one entity. Unspecified fields are preserved. Passing `type` performs an atomic single-node migration: every incident edge is re-inferred against the catalog and rollback applies on failure. For 3+ entities, use `batch_update_nodes`.
Nodesatomic-with-rollback (when `type` is changed); atomic for
shallow-merge patches.
Arguments
node_idstringrequiredThe node ID to update
typestringoptionalChange the entity type. Atomic single-node migration: validates against UPG_TYPES, rewrites incident edges to canonical types.
titlestringoptionaldescriptionstringoptionaltagsarrayoptionalstatusstringoptionalpropertiesobjectoptionalMerged with existing properties
unset_propertiesarrayoptionalProperty keys to DELETE. Applied after the `properties` merge, so one call can set some keys and drop others. Writing `{ key: null }` only stores a literal null; use this to actually remove a key. Unknown keys are ignored.
Returns
Shape
{ node, warning?, unknown_properties?, unset? }warning aggregates migration warnings and any unknown-property notice.unknown_properties lists property keys not in the entity's schema.unset lists the keys actually removed.Pass
strict: true to reject unknown properties instead of warning.Examples
Live call against the Notion example graph.
Input
{
"node_id": "ec3d5479-4947-4bd9-9e77-b5ee01beb851"
}Output
{
"node": {
"id": "ec3d5479-4947-4bd9-9e77-b5ee01beb851",
"type": "product",
"title": "Notion (SATURATED test graph)",
"slug": "notion-saturated-test-graph"
}
}