|
| 1 | +# Zapier Integration Playbook: Standard Operating Procedure |
| 2 | + |
| 3 | +## 1. Overview |
| 4 | + |
| 5 | +**Workflow Name:** |
| 6 | +Zaps: Zoom Recording to Google Drive & YouTube |
| 7 | + |
| 8 | +**Template:** |
| 9 | +https://zapier.com/shared/1cf48789b958c3e2bf8cae14ed25c6943f193a7f |
| 10 | + |
| 11 | +**Purpose:** |
| 12 | +Automates the flow of Zoom cloud recordings into Google Drive for backup, and then uploads them to YouTube, assigning them to the correct playlist. |
| 13 | + |
| 14 | +**Owner:** |
| 15 | +[@youtube-admins](https://github.com/kubernetes/community/blob/master/communication/moderators.md#owners) |
| 16 | + |
| 17 | +**Last Updated:** |
| 18 | +Oct 29, 2025, 09:15 AM CET |
| 19 | + |
| 20 | + |
| 21 | +## 2. Workflow Diagram |
| 22 | + |
| 23 | +**High-level visual sequence:** |
| 24 | + |
| 25 | +1. Zoom: Detects new cloud recording |
| 26 | +2. Formatter: Normalizes the recording date |
| 27 | +3. Google Drive: Uploads the file to a shared drive folder |
| 28 | +4. YouTube: Uploads the video with title, description, and privacy settings |
| 29 | +5. YouTube: Adds uploaded video into the correct playlist |
| 30 | + |
| 31 | + |
| 32 | + |
| 33 | + |
| 34 | +## 3. Step-by-Step Breakdown & Rebuild |
| 35 | + |
| 36 | +**Template:** |
| 37 | +https://zapier.com/shared/1cf48789b958c3e2bf8cae14ed25c6943f193a7f |
| 38 | + |
| 39 | +**Zap Name:** |
| 40 | +[SIG-NAME]-Integration: Zoom Recording → Google Drive → YouTube |
| 41 | + |
| 42 | +### 3.1 Trigger – Zoom |
| 43 | + |
| 44 | +- **App:** Zoom (v2.24.7) |
| 45 | +- **Event:** New Cloud Recording |
| 46 | + |
| 47 | +**Setup inside Zapier:** |
| 48 | +- Connect the correct Zoom account |
| 49 | +- Choose trigger: New Cloud Recording |
| 50 | +- Configure filters if needed (e.g., only for your user or specific meeting topics) |
| 51 | +- Test trigger: Zapier should return a sample recording object |
| 52 | + |
| 53 | +**Fields to note:** |
| 54 | +- Recording Start Time → used in Formatter step |
| 55 | +- Download URL → used later for file upload |
| 56 | + |
| 57 | + |
| 58 | +### 3.2 Action – Formatter by Zapier (Date/Time) |
| 59 | + |
| 60 | +- **App:** Formatter by Zapier |
| 61 | +- **Event:** Date/Time → Format |
| 62 | + |
| 63 | +**Setup inside Zapier:** |
| 64 | +- Input: Recording Start Time (from Zoom) |
| 65 | +- From Format: Auto-detect |
| 66 | +- To Format: YYYY-MM-DD |
| 67 | + |
| 68 | +**Example Output:** |
| 69 | +2025-09-04 |
| 70 | +(This clean date string will be inserted into file names and YouTube titles.) |
| 71 | + |
| 72 | + |
| 73 | +### 3.3 Action – Google Drive (Upload File) |
| 74 | + |
| 75 | +- **App:** Google Drive |
| 76 | +- **Event:** Upload File |
| 77 | + |
| 78 | +**Setup inside Zapier:** |
| 79 | +- Connect Google Drive account |
| 80 | +- Folder: Select destination folder (e.g., `/Team/Meetings/Recordings/`) |
| 81 | +- File: Map Zoom’s Download URL |
| 82 | +- File Name: `WG Node Lifecycle Meeting – {{Formatter Output}}.mp4` |
| 83 | +- Test: Zapier should upload a sample file into your Drive folder |
| 84 | + |
| 85 | + |
| 86 | +### 3.4 Action – YouTube (Upload Video) |
| 87 | + |
| 88 | +- **App:** YouTube |
| 89 | +- **Event:** Upload Video |
| 90 | + |
| 91 | +**Setup inside Zapier:** |
| 92 | +- Connect your YouTube channel |
| 93 | +- Video File: Map to the Google Drive file from Step 3 |
| 94 | +- Title: `WG Node Lifecycle Meeting – {{Formatter Output}}` |
| 95 | +- Description: (Include structured details, e.g.) |
| 96 | + - Weekly WG Node Lifecycle meeting |
| 97 | + - Date: {{Formatter Output}} |
| 98 | + - Agenda: |
| 99 | + - Updates |
| 100 | + - Open issues |
| 101 | + - Next steps |
| 102 | +- Privacy: Choose Public / Unlisted / Private |
| 103 | +- Tags: (Optional, e.g., Kubernetes, Working Group, Node Lifecycle) |
| 104 | + |
| 105 | + |
| 106 | +### 3.5 Action – YouTube (Add Video to Playlist) |
| 107 | + |
| 108 | +- **App:** YouTube |
| 109 | +- **Event:** Add Video to Playlist |
| 110 | + |
| 111 | +**Setup inside Zapier:** |
| 112 | +- Playlist: Select the target playlist (e.g., WG Node Lifecycle Meetings) |
| 113 | +- Video: Map video ID from Step 4 (YouTube Upload) |
| 114 | + |
| 115 | + |
| 116 | +## 4. Testing the Zap |
| 117 | + |
| 118 | +- Run the Zap manually with a sample Zoom recording |
| 119 | +- Confirm: |
| 120 | + - File appears in Google Drive with correct filename |
| 121 | + - Video uploads to YouTube with correct title, description, privacy |
| 122 | + - Video appears in the right playlist |
| 123 | + |
| 124 | + |
| 125 | +## 5. Error Handling |
| 126 | + |
| 127 | +- **Large files:** If file upload fails, check Zoom → Drive connection limits |
| 128 | +- **Retries:** Zapier retries failed steps automatically; confirm retry settings |
| 129 | +- **Notifications:** Ensure error emails are enabled in Zapier account |
| 130 | +- **YouTube Upload:** If YouTube rejects upload (e.g., quota exceeded), Zapier shows an error in Zap History |
| 131 | +- **Email Notifications:** Set up email notifications for failed runs |
| 132 | + |
| 133 | + |
| 134 | +## 6. Accounts & Connections |
| 135 | + |
| 136 | +This section details the accounts and connections used within our Zapier integrations. |
| 137 | +Maintaining accurate and secure connections is vital for uninterrupted workflows. |
| 138 | + |
| 139 | +| Application | Account Name | Connected By | Last Reviewed | |
| 140 | +|--------------------|--------------|--------------|--------------| |
| 141 | +| Zoom Account | Person | Person | Date | |
| 142 | +| Google Drive Account| Person | Person | Date | |
| 143 | +| YouTube Account | Person | Person | Date | |
| 144 | + |
| 145 | + |
| 146 | +## 7. Change Management Note |
| 147 | + |
| 148 | +Any edits to this Zap must be documented in this SOP and reviewed by [@youtube-admins](https://github.com/kubernetes/community/blob/master/communication/moderators.md#owners). |
| 149 | +Export a new PNG of the flow when changes are made. |
| 150 | + |
| 151 | + |
| 152 | +## 8. Team Implementation Notes |
| 153 | + |
| 154 | +- All team members should have access to the Google Drive destination folder and YouTube playlist |
| 155 | +- Test workflow with a small sample recording before enabling full automation |
| 156 | +- Keep a version history: save screenshots or JSON export of Zap for version tracking |
| 157 | + |
| 158 | + |
| 159 | +## 9. Testing Checklist |
| 160 | + |
| 161 | +- Trigger fires when a new Zoom recording is created |
| 162 | +- File uploads to correct Google Drive folder |
| 163 | +- Filename uses YYYY-MM-DD format |
| 164 | +- Video uploads to YouTube with title & description |
| 165 | +- Video is assigned to correct playlist |
0 commit comments