virtual-agent/web

Embed and control Zoom Virtual Agent campaigns on web pages with SDK events.

65|12|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/zoom/skills --skill virtual-agent-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: virtual-agent/web
Source: https://github.com/zoom/skills/tree/main/virtual-agent/web
Command: npx skills add https://github.com/zoom/skills --skill virtual-agent-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Embeds and controls Zoom Virtual Agent experiences on web pages, enabling campaign-driven interactions and entry-ID workflows.

Core Features & Use Cases

  • Campaign embed on websites to drive engagement
  • Event-driven controls and user context updates
  • Supports ready-state gating and CSP-safe deployment

Quick Start

Load the Zoom Virtual Agent Web SDK on your page, wait for the zoomCampaignSdk:ready event or waitForReady(), then call show() to display a campaign.

Frequently Asked Questions about virtual-agent/web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I embed Zoom Virtual Agent in a web app for campaign interactions?

To embed Zoom Virtual Agent, load the Web SDK on your page, wait for the zoomCampaignSdk:ready event or call waitForReady(), then invoke show() to display the campaign. This enables campaign-driven interactions and entry-ID workflows on your website.

What is ready-state gating for virtual agent web SDKs?

Ready-state gating ensures the virtual agent web SDK only displays campaigns after fully loading. You wait for the zoomCampaignSdk:ready event or call waitForReady() before triggering show(), preventing premature engagement and ensuring CSP-safe deployment.

Does the Zoom Virtual Agent Web SDK require CSP compliance?

Yes, embedding the Zoom Virtual Agent requires CSP compliance to ensure safe deployment. Your web app must configure Content Security Policy headers to allow the SDK scripts, enabling secure campaign-driven interactions and entry-ID guided flows.

How do I handle engagement lifecycle events for an embedded virtual agent?

You handle engagement lifecycle events by implementing event-driven controls after initializing the SDK. This allows you to manage user context updates and trigger specific campaign behaviors when the virtual agent interacts with users on the web page.

Can I use entry-ID guided flows with the Zoom Virtual Agent embed?

Yes, the Zoom Virtual Agent web embed supports entry-ID workflows. By initializing the SDK and configuring entry IDs, you can guide users through specific campaign interactions and control the virtual agent experience based on the entry point.