Build Zoom Phone Integration

From the author

Use when building Phone.

— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to building integrations with Zoom Phone. It covers the architectural requirements for implementing CTI, CRM dialers, and Smart Embed components. The skill emphasizes modular design, separating call control from data management, and provides guidance on handling OAuth scopes, webhook processing, and event contracts to ensure robust and maintainable phone integrations.

What it does

Classifies integration types including REST API automation, webhooks, and Smart Embed.
Provides architectural patterns for call handling, record management, and number management.
Offers guidance on validating Smart Embed postMessage event contracts.
Outlines the lifecycle for CRM-based click-to-call and call history synchronization.
Includes troubleshooting steps for common issues like scope mismatches and permission errors.

When to use it

When developing custom CRM dialers or CTI applications using Zoom Phone.
When implementing Smart Embed components for embedded phone functionality.
When setting up automated call handling workflows or webhook event processing.
When debugging integration issues related to phone entitlements, OAuth scopes, or event payloads.

Advantages

Promotes a modular architecture that separates call control from business logic.
Provides clear patterns for handling complex CRM-to-Phone state mapping.
Reduces integration errors by emphasizing pre-implementation checks for scopes and permissions.
Offers migration-safe strategies for handling evolving API response shapes.

Usage examples

“How do I implement a click-to-call feature in my CRM using Smart Embed?”: The agent will guide you through rendering the Smart Embed iframe, setting up the client-side event listener for click-to-call commands, and configuring the server-side OAuth flow.
“What is the recommended pattern for updating call handling settings via API?”: The agent will provide a workflow to read current settings, build typed patch payloads, and apply updates for business or holiday hours while ensuring E.164 number validation.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/build-zoom-phone-integration/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip build-zoom-phone-integration.zip -d .agents/skills

Documentation by Zoom

Use this skill when the target workflow is Zoom Phone, CTI, CRM calling, call events, or Smart Embed behavior.

Workflow

Classify the integration: REST API automation, webhook event processing, Smart Embed, URI launch, CRM dialer, or call-handling workflow.
Confirm the actor, account settings, phone entitlements, and OAuth scopes before implementation.
Keep call control, call records, number management, and webhook processing as separate modules.
For Smart Embed, validate postMessage event contracts, embedding constraints, and CRM state mapping.
Debug by checking scopes, phone license, role permissions, number ownership, webhook subscriptions, and event payload shape.

References

Full preserved guide: references/full-guide.md
Architecture and lifecycle: concepts/architecture-and-lifecycle.md
Phone API service pattern: examples/phone-api-service-pattern.md
Smart Embed bridge: examples/smart-embed-postmessage-bridge.md
Event contract: references/smart-embed-event-contract.md
Common issues: troubleshooting/common-issues.md

Files

ATTRIBUTION.mdAdded by AutoGineer880 B
LICENSELicence file added by AutoGineer1.1 KiB
RUNBOOK.md1.6 KiB
SKILL.md1.4 KiB
agents/openai.yaml145 B
concepts/architecture-and-lifecycle.md1.4 KiB
examples/phone-api-service-pattern.md1.3 KiB
examples/smart-embed-postmessage-bridge.md1.2 KiB
references/call-handling-patterns.md961 B
references/crm-sample-validation.md1.4 KiB
references/deprecations-and-migrations.md1.2 KiB
references/environment-variables.md1.3 KiB
references/forum-top-questions.md3.7 KiB
references/full-guide.md3.8 KiB
references/smart-embed-event-contract.md1.0 KiB
references/source-map.md888 B
scenarios/high-level-scenarios.md1.2 KiB
troubleshooting/common-issues.md1.2 KiB

concepts/architecture-and-lifecycle.md

Zoom Phone Architecture and Lifecycle

Architecture

User/Agent UI
  |
  | (A) Smart Embed postMessage events
  v
Smart Embed Iframe (applications.zoom.us)
  |
  | event stream + call controls
  v
CRM Web App (event bridge + UI state)
  |
  | OAuth token on server only
  v
Backend API Layer
  |\
  | \-- Zoom Phone REST APIs (call history, call handling, contacts)
  |
  \---- Webhook endpoint (phone.* events)

Lifecycle Workflow

Provision:

Account has Zoom Phone and optional SMS enablement.

Authorize:

OAuth app installed and scoped for required Phone operations.

Initialize UI:

Load Smart Embed iframe/script.
Wait for onZoomPhoneIframeApiReady.
Send zp-init-config and register event handlers.

Engage:

Start calls/SMS via zp-make-call or zp-input-sms.
Receive events (zp-call-*, zp-sms-log-event, optional AI/contact/notes events).

Persist:

Save event snapshots keyed by callId.
Reconcile to call history/call element records after completion.

Post-call:

Save call notes/disposition and optional recording/voicemail links.

Operate:

Track deprecations and apply endpoint/event mapping updates.

Version Drift Strategy

Normalize inbound payloads in one adapter layer.
Keep endpoint constants centralized by version target.
Feature-flag optional payload fields.
Keep webhook + Smart Embed event handlers tolerant to added fields and enum expansion.

Requirements and compatibility

Written for: OpenAI Codex

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Build MCP App
AnthropicOfficial
Build interactive UI widgets for MCP servers to render forms, pickers, and dashboards directly within the chat interface.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
MCP Integration
AnthropicOfficial
Comprehensive guide for integrating Model Context Protocol (MCP) servers into Claude Code plugins.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository46.3k
Social Publishing
Seth Hobson· Community
Programmatically schedule and publish content across 13 social media platforms using the SocialClaw API.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Hermes Tweet
Seth Hobson· Community
Integrates X/Twitter research and action capabilities into the Hermes Agent framework with strict approval-gated security.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Paypal Integration
Seth Hobson· Community
A guide to integrating PayPal payment processing, including checkout flows, subscriptions, and IPN webhook handling.
Automation and integrationsClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Social Publishing Publisher
Seth Hobson· Community
An agent-driven social media publishing specialist for multi-platform campaign management via the SocialClaw API.
Automation and integrationsClaude Code
MITGitHub stars of the source repository42.3k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download build-zoom-phone-integration.zip