Delete Meeting Recordings

zoom.delete_meeting_recordings

ActionChat & messagingconnection required

Calls the Zoom API with the connection's credentials.

Move a meeting's cloud recordings to the trash, or erase them.

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Zoom
Secret shape: {"account_id", "client_id", "client_secret"} — Server-to-Server OAuth
Config it needs: account_id
Resolved by: config.connection_id, else node.connection_id

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

Field	Type	Required	Default	Constraints	Example
meeting_id The meeting number, as a string — an int64 read as a number loses digits. The spaced form Zoom's UI shows ('812 3456 7890') is accepted.	string	Yes	—	—	81234567890
action trash keeps them recoverable for 30 days; delete is permanent.	string	No	trash	one of "trash", "delete"	—

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

{
  "action": "trash",
  "meeting_id": "81234567890"
}

One shape.

Field	Type	Example
ok True when Zoom accepted the deletion.	boolean	true
id The meeting number whose recordings were removed.	string	—
action Whether they were trashed or erased.	string	—

{
  "action": "",
  "id": "",
  "ok": true
}

This removes every file for the instance at once, not one file.
action=delete cannot be undone; put it behind an approval step, and archive the files first with List Meeting Recordings.

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