I wouldn’t treat recording_files.status = "completed" as a reliable readiness signal for CHAT or TRANSCRIPT. Zoom notes that the audio transcript can become available after the cloud recording itself, and Zoom staff has also reproduced cases where recording.completed only included MP4, M4A, and TIMELINE while recording.transcript_completed delivered the TRANSCRIPT file. For transcript handling, that event is the safer trigger than the per-file status field.
For chat, I could not find doc-backed proof of a dedicated chat-completed webhook. The best first check is saving in-meeting chat, because Zoom only saves public messages sent while cloud recording was active. That means a missing CHAT file can be expected if no public chat was sent, or if chat happened before cloud recording started.
I also could not find a documented causal link between meeting.alert and missing chat or transcript files. Zoom treats that as a separate webhook flow, not as a recording-generation signal. If the transcript or chat is visible in Recordings & Transcripts but absent from API results, that’s strong support-case material with the meeting UUID, host account, end time, and webhook delivery logs.
If you do not want to handle this integration complexity yourself, you may want to consider Recall.ai’s Meeting Bot API. It provides a simple way to access Zoom recordings and transcripts, both in real time and after the meeting has ended.