Zoom competitor briefings and weekly reviews, prepared by Claude

The Zoom for Claude connector lets Claude search your Zoom meetings in natural language and retrieve meeting assets. Zoom's changelog lists AI summaries, documents, recordings and whiteboards, plus transcripts, summaries, next steps and playback links for a recording. The Agent Index listing shows 9 tools: 7 reads and 2 writes.

The two writes create files from content. Zoom's support article says that when Claude drafts a list of action items it first confirms whether you want a new Zoom Canvas doc, and that the app requests a Zoom Canvas permission to generate meeting materials and agendas. It does not know what competitors did this week, so Linkeddit supplies that part.

Name the call and the competitor, and Claude builds a one page briefing from two sources. It uses search_meetings and get_meeting_assets to find what was said on earlier calls with the account, and Linkeddit's compete_brief_get to return the competitor's latest graded brief: moves, pricing signals, switch triggers and recommended actions.

Zoom's own support article gives the pattern for the meeting side. Its example prompts ask for a recap of a named meeting, what a person said about a topic and where in a recording a blocker was raised, and the connector can open the recording at that timestamp if you have access to the cloud recording.

Linkeddit's brief view returns one tracked competitor at a time, which suits a single call. If the brief is empty, say so in the briefing. On the test project, plausible.io, the monitor had analyzed nothing yet that week, and an honest gap is better than invented context.

Recordings alone do not explain outcomes. A sales manager on Reddit wrote: "But that doesn't tell you much about why a prospect ghosted after a demo or why one AE keeps closing deals while others struggle." A competitor briefing adds the outside half: what changed on the other side before the call.

Run the facts through Claude before the meeting, so the call is for decisions. Ask Claude for Linkeddit's weekly brief with compete_brief_get, then have it create a Zoom doc with create_new_file_with_markdown that you share in the invite.

On the test project, the weekly brief for the week of 2026-10-26 reported 5 competitors monitored, 2 high priority signals, 9 worth watching and 8 low signal moves. The high priority items were a Matomo security update and Fathom launching an AI assistant called Luna. That gives the meeting two items to discuss and nine to skim, with a source link on each.

After the call, Claude can read the recording summary and next steps with get_recording_resource and add the decisions to the same doc. Linkeddit supplies no meeting notes and Zoom supplies no competitor data, so each connector does what only it can.

The connector lists no alert tool. Claude can read Linkeddit's high priority signals with compete_signals_get when you ask and write them into a Zoom doc, so the alert is a page you open, not a push notification.

Linkeddit's monitors run on their own clock. All five on the test project run weekly, each with its next run on 2026-11-04. Claude acts only when you start it, so run the prompt before the weekly call or a standup. If you need a notification the moment a competitor page changes, use a page monitoring tool. If a weekly decision is enough, a prepared doc is the better fit.

Use the call as the review point. Say what you published and when, and Claude uses Linkeddit's answer_verify_start to re-check the targeted buying questions across the five engines, then answer_verify_get for the outcome. Starting a check spends credits, so Linkeddit returns an estimate first and Claude waits for your yes.

The outcome is about movement only: improved, declined, mixed, no significant change or not comparable. A check that has not finished is reported as not measured yet, which is not the same as no change.

On the test project, all three recent audit runs finished with status partial, so a review has to say that out loud. Claude can then write the result into the meeting doc with create_new_file_with_markdown, and search_meetings finds the earlier call where the change was agreed.

Claude reads only what your Zoom account can access. Zoom's support article lists the permissions the app uses: meeting assets, meeting search, cloud recording lists and cloud recording content, plus Zoom Canvas for writing docs. It also says Claude API tokens and Zoom OAuth credentials are stored encrypted at the user level.

Tell Claude which meetings it may search, and read every generated doc before you share it. Meeting recordings can contain customer names and numbers. Linkeddit never receives your meetings. It only sends competitor and answer data to Claude, and the doc you read is the only thing written in your account.