← ZoomCONTENT HISTORY

Update to Zoom

Snapshot Nov 17, 2026 · 06:10 UTC · version 2.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Zoom and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build, demo, test, deploy, run, list, inspect, or turn off Zoom Workflows through the connected Zoom MCP server. Use for recurring or event-driven work whose data or trigger is a Zoom product (after each meeting, before each meeting, a weekly digest of meetings or Zoom Chat), even without the words \"Zoom Workflow\", and for a workflow that did not run. The five Workflow shortcut prompts (this skill followed by, for example, \"send meeting summary\" or \"my zoom zodiac\") ask to deploy that pinned workflow and run it once.",
  "included_files": [],
  "name": "zoom-workflows",
  "skill_md_contents": "---\nname: zoom-workflows\ndescription: >-\n  Build, demo, test, deploy, run, list, inspect, or turn off Zoom Workflows through the connected\n  Zoom MCP server. Use for recurring or event-driven work whose data or trigger is a Zoom product\n  (after each meeting, before each meeting, a weekly digest of meetings or Zoom Chat), even without\n  the words \"Zoom Workflow\", and for a workflow that did not run. The five Workflow shortcut prompts\n  (this skill followed by, for example, \"send meeting summary\" or \"my zoom zodiac\") ask to deploy\n  that pinned workflow and run it once.\n---\n\n# Zoom Workflows\n\nThis plugin builds and runs Zoom Workflows: automations that live in the user's Zoom account and\nkeep running after the conversation. Resolve every path below from the directory containing this\n`SKILL.md`; `../../Workflow` is the plugin's Workflow tree, not the shell's current directory or a\n`Workflow` folder inside `skills/`. If a relative read fails, locate this file and resolve from its\nactual path before concluding that the builder is missing.\n\n## The connection\n\nEverything live goes through the connected **Zoom MCP server** (the Zoom connector):\n\n- **Workflow operations** (list, inspect, test run, deploy, undeploy, resume) are capabilities\n  behind its discovery gateway: `capabilities_discover` with `paths: [\"workflow\"]`, then\n  `capabilities_describe` and the read or write invoker. Some connections expose the `workflow_*`\n  tools directly instead. `../../Workflow/skills/workflow-core/references/lifecycle.md`,\n  *Reaching the tools*, covers both. The absence of literal `workflow_*` names in the tool list\n  does not mean Workflow is unavailable.\n- **Meeting data** for a one-time run comes from the same server's own tools: `search` on the\n  `zoom_meeting` datasource for the meeting, `get_meeting_assets` only when a hit cannot show what\n  the run needs. `../../Workflow/skills/workflow-demo/references/hero-fast-path.md`, *Find a test\n  meeting*, has the procedure.\n\nThe plugin declares one MCP server, `zoom`, at `https://mcp.zoom.us/mcp/zoom/streamable`: the same\nserver as the **Zoom for Claude** directory connector, so a user who has both sees one set of\ntools. If no Zoom MCP tools are available, or the server is not connected or rejects a call, say so\nbefore anything else and how to fix it, for the host you are running in. In Claude: connect Zoom\nfor Claude with your Zoom account (Claude's Settings → Connectors, or the plugin's Connectors tab),\nthen start a new conversation (in Claude Code, check `/mcp`); on a Team or Enterprise plan where it\nis not listed, the Claude admin has to add it. In Codex or ChatGPT: connect this plugin's Zoom\nconnection with your Zoom account from the plugin's settings or when the host asks, then start a\nnew conversation; in a workspace where the plugin is not available, the workspace admin has to\nenable it. Do not call Zoom APIs directly outside the connected MCP tools. The host owns OAuth; never read, print, or\ncache tokens, or ask the user to paste them or a callback URL into chat.\n\n## Scope\n\nTake an automation request when its data or trigger is a Zoom product (meetings, recordings,\ntranscripts, Zoom Chat) or a connected app the generator indexes (Jira, Salesforce, and others in\n`resources/app_scope_index.json`), and the vendored generator supports both what starts it (its\ntrigger catalog, `scripts/trigger_lookup.py --list`) and the apps its steps use (a phone call or\ntext to the user is the generator's own voice/SMS step, not an app). When either is missing, say\nso and leave it to the host's own scheduling. A request the host's scheduled task already handles\nstays there. If the user has said not to use Zoom Workflow, or `lifecycle.md`'s credit and license\nsection has moved this conversation off Workflow, use the host's scheduling instead.\n\nA one-time question about Zoom content (find, summarize, answer) is not a workflow: answer it with\nthe Zoom MCP tools directly. If the user selected this plugin for a one-time write that the\nconnected tools cannot complete, check the generator's `SKILL.md` and `app_scope_index.json`; with\na grounded destination and content rule, build it through `workflow-create` as a manual-trigger\ndraft and say clearly that compiling the draft has not performed the write.\n\n## Capability menu and shortcuts\n\nWhen the user asks what this plugin can do, run\n`../../Workflow/skills/workflow-demo/scripts/hero_context.py --quick-menu --markdown --host <host>`\n(`codex` in Codex, `claude` in Claude Code) and reproduce the table it prints exactly, header row\nincluded. Its wording is reviewed product copy (the Zodiac entertainment note is required), and\neach prompt carries the host prefix so the user can copy it as is. Keep any summary of your own\noutside the table. Do not load every template.\n\nThen offer to start one: ask once with this host's question tool which shortcut to try, one option per\nshortcut in menu order, each labelled with the shortcut's name and a few words from its row, and no\nrecommended default. If the tool allows fewer options than there are shortcuts, make the last option\n\"More…\" and ask again with the rest. Picking an option is the same request as sending that\nshortcut's prompt: match it with `--match` and follow the fast path, including its destination\nquestion. A free-text answer is a new request. If the host has no question tool, put each prompt in\nits own fenced code block under the table so it can be copied.\n\nTo tell whether a message is a shortcut, run the same script with `--match \"<the user's message>\"`\nand the host flag. It accepts the host prefix or the bare suffix the host passes when this skill is\ninvoked.\n\n- A returned `template` is an explicit request to **deploy that pinned workflow and run it once**.\n- A returned `needs_destination` (a shortcut with several destinations, such as \"send meeting\n  summary\" or \"meeting reminders\", sent without one) is still that shortcut; the fast path asks for\n  the destination.\n\nFor either, read `../../Workflow/skills/workflow-demo/references/hero-fast-path.md` and follow its\nshortcut procedure without asking again whether to deploy or run. Required inputs, live\nentitlement, and trigger schemas still need checking; never invent a channel, phone number, or\nevent payload. An explicit demo request or a template picked from the demo menu also goes to the\nfast path. A concrete automation request other than an exact shortcut goes to `workflow-create`,\neven when it resembles a pinned example; a saved workflow goes to inspection.\n\n## Routing\n\nRead the child skill under `../../Workflow/skills/` for what the user came for:\n\n- a concrete automation to create or change: `workflow-create/SKILL.md`;\n- a saved workflow's status or runs, or a run that did not happen: `workflow-inspect/SKILL.md`;\n- first contact, \"what can this do\", or a goal that is still unclear: `workflow-onboard/SKILL.md`.\n\nBefore any live Workflow call, read `../../Workflow/skills/workflow-core/references/lifecycle.md`\non its own.\n"
}

SHA-256 of public snapshot: 7704ba1d8d4d56a614c5dac2bed7f69882c8b562059ed05971204ae85075025a