Zoom Automation Developer (VDS, Web SDK, Browser)

Job Title: Zoom Automation Developer (VDS Environment, Web SDK, Browser Automation) Overview We need a fully automated Zoom meeting system running on a Windows 11 VDS (Ultahost). The system should: Start Zoom meetings every night at 8 PM (KST) Automatically play a Google Drive video (via screen sharing) Post scheduled chat messages (e.g., announcements or instructions) Maintain presence so the meeting doesn’t appear “empty” Stop/close automatically at 11 PM Run unattended (365 days) once set up Scope & Deliverables Zoom API Integration Use the Zoom REST API to create/modify recurring or daily meetings. Must handle meeting start/end times automatically (e.g., 8 PM–11 PM). Web SDK or Browser Automation Host session must be launched (via start_url or Web SDK) to make the meeting “live.” If Web SDK is chosen, be able to handle screen sharing and timed chat messages programmatically. If browser automation is used (Puppeteer/Selenium), manage UI elements (e.g., “Share Screen” button). Video Playback (Google Drive) Auto-play the video (stream or local) in Zoom screen sharing. Verify smooth playback and minimal buffering on the VDS. Chat Scheduling & Participant Management Scheduled chat messages during the meeting (e.g., at 8:10, 8:30, 8:55) for announcements or links. Keep at least one “additional connection” active (or multiple connections) without violating Zoom policies. VDS Setup (Windows 11) Install/Configure Chrome, Node.js/Python, and relevant drivers. Use Windows Task Scheduler (or an equivalent) to run scripts at specific times. Ensure reliability (retry logic, logging, error handling). Testing & Deployment Provide thorough testing to confirm all automated features work nightly. Deploy onto the Ultahost Windows 11 VDS. 2-3 days initially for a proof-of-concept (if feasible), then finalize for full operation. Key Requirements (Skill Checklist) Zoom REST API Meeting creation/deletion/scheduling Understanding Server-to-Server OAuth or OAuth App Familiarity with rate limits and error handling Zoom Web SDK If used for in-meeting features (chat, screen sharing, permission management) Handling events like onChatMessage or onShareScreen Setting up signatures and authentication flow Browser Automation Puppeteer or Selenium in Node.js/Python Automated clicks for screen sharing, Google Drive playback buttons Managing headless browsers (multi-tab, pop-ups, etc.) Screen Sharing & Google Drive Auto-playing pre-uploaded videos nightly Verifying bandwidth/quality for smooth playback on the VDS Participant Management Ensuring the meeting never shows “0 participants” Additional user sessions or connections (within Zoom policy) Monitoring CPU/RAM usage on the VDS Scheduled In-meeting Chat Timed chat messages (host or participant mode) Possibly using Web SDK’s [login to view URL]() or UI automation Windows 11 VDS Environment Chrome, Node/Python setup Windows Task Scheduler or other orchestration Logging and retry logic if errors occur Unattended Operation (365 days) Orchestration (CRON-like scheduling, pm2, etc.) Exception handling (Zoom login errors, network issues) Logging/monitoring (email alerts, Slack messages, etc.) (Optional) AI or CRM Integration If advanced chat response (AI) or marketing automation is relevant Not mandatory, but beneficial for future expansions Additional Details Deadline: Within 3 days for an initial proof-of-concept (if feasible). A fully stable solution may take longer. Budget: Starting at $1000+ Policy Note: The solution must comply with Zoom’s terms, focusing on legitimate user sessions or Web SDK approaches. How to Apply Please confirm your experience in Zoom REST API, Web SDK, and/or browser automation. Provide past examples of related automation or meeting scheduling projects. Clarify your approach to: Automatic screen sharing (Google Drive playback) Timed chat messages within Zoom Unattended operation on a Windows 11 VDS If you have any questions or need clarifications, feel free to ask. We look forward to your proposal.