Upgrade Room

matrix.upgrade_room
ActionChat & messagingconnection required

Calls the Matrix API with the connection's credentials.

Replace a room with a new one on a newer room version.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Matrix
Secret shape
the account access token, or {"access_token": "…"}
Config it needs
base_url, user_id, default_room_id
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
room_id
The room id, e.g. !AbCdEf:example.org — resolve a #alias:server with matrix.resolve_room_alias first.
stringYes——!AbCdEf:example.org
new_version
The room version to upgrade to, e.g. '11'.
stringYes——11

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "new_version": "11",
  "room_id": "!AbCdEf:example.org"
}

Output

One shape.

result

FieldTypeExample
replacement_room
The id of the room that replaces this one.
string—
room_id
The old room, now tombstoned.
string—
{
  "replacement_room": "",
  "room_id": ""
}

Notes

  • The connection's base_url is the homeserver (e.g. https://matrix.example.org), not the account's server name; the two differ whenever .well-known delegation is in use.
  • Rooms are addressed by room id (!abc:server). Resolve a #alias:server with matrix.resolve_room_alias first, or set a default room on the connection.
  • The old room is kept and tombstoned; members are not moved for you — they follow the tombstone when their client opens the room.

See Upgrade Room run in a workflow.

In a technical demo we add the Matrix connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.