Zoom integration verification is in progress

Zoom appears in Aurora's production connector catalog, but Finta has not verified the integration end to end. The catalog currently has zero connection records, zero active connections, and no discovered Zoom tools, so the page must not present a successful connection or live workflow as proven.

Zoom's current provider documentation lists https://zoom.us/mcp/meeting/streamable as the Streamable HTTP meeting endpoint and describes OAuth with PKCE through a manually registered Zoom General app. Finta's current catalog row uses a different regional endpoint and bearer configuration. That mismatch must be reconciled before a public connection CTA is trustworthy.

This page can still help an evaluator understand the intended relationship-intelligence workflow, required meeting access, provider limits, and exact proof path. It is a status page until the endpoint, OAuth flow, discovered tools, and one safe meeting read are verified together.

Current status

A catalog card proves that Finta has configuration metadata, not that OAuth, transport negotiation, tool discovery, provider licensing, and meeting access work together for a real account.

The endpoint and authentication configuration should be reconciled against Zoom's current provider documentation before the existing catalog row is used as public proof.

A future successful connection still would not prove access to every meeting. Availability depends on account type, host or user access, meeting settings, recording or transcript availability, retention, and granted scopes.

What is documented and what Finta verified

Zoom documents meeting-oriented MCP capabilities. Finta has not discovered an exact Zoom tool list through a live Aurora connection, so every provider capability below remains documented rather than Finta-verified.

Setup and proof path

1. Treat the current Zoom page as a verification-status page, not a working installation guide.
2. Confirm Zoom's current meeting MCP endpoint and supported transports in provider documentation.
3. Create or select a Zoom General app in the Zoom App Marketplace for the Finta connection flow.
4. Register the exact Finta redirect URI and configure OAuth with PKCE according to Zoom's current instructions.
5. Select the minimum Zoom scopes needed for meeting search and one safe read. Record the reason for every scope.
6. Update or reconcile the Finta catalog endpoint and authentication mode with Zoom's documented configuration.
7. Complete one connection with a controlled Zoom account that has an eligible known meeting.
8. Capture a sanitized receipt for endpoint selection, transport, OAuth completion, user identity, and account context.
9. Discover the exact tools Zoom returns to Aurora and compare them with the current provider documentation.
10. Run one safe read against a known non-sensitive meeting and reconcile the returned identifier, date, participants, and available assets with Zoom.
11. Test missing-summary, missing-transcript, host-access, and insufficient-scope cases so the page explains ordinary failure states.
12. Run the intended relationship workflow without mutating Zoom or Finta. Preserve source identifiers and separate evidence from inference.
13. If follow-up creation or sending is later included, test that action separately behind an explicit approval boundary and source-check the destination.
14. Offer a public connection CTA only after production-like browser, metadata, image, mobile, dark-mode, and security verification passes.

Flagship workflow

Investor meeting evidence to reviewed follow-up

After Zoom is verified, the flagship workflow should turn one eligible meeting into a source-backed relationship brief and a reviewed next move, without implying that a transcript proves sentiment or commitment.

1. Search the authorized Zoom account for one known completed investor meeting in a defined date range.
2. Retrieve the meeting metadata and only the summary, recording, transcript, or next-step assets that the account is permitted to access.
3. Preserve the Zoom meeting identifier, asset type, source time, and access caveat for traceability.
4. Extract direct decisions, questions, promises, and named next steps while keeping interpretation separate.
5. Match participants to Finta contacts, companies, relationship owners, and the correct active deal.
6. Compare meeting evidence with existing CRM notes, open tasks, and more recent email or relationship context.
7. Flag conflicts, missing participants, unavailable assets, and statements that cannot be supported by the Zoom source.
8. Prepare a concise meeting brief and one recommended relationship action with timing rationale.
9. Stop before creating a task, changing CRM, scheduling a meeting, or sending follow-up until the user reviews the evidence and proposed action.

Sample prompts

• After Zoom is marked verified, find the latest eligible meeting with the selected investor. Show the source meeting, direct decisions, open questions, and promised next steps. Match it to Finta CRM and recommend one follow-up. Do not change or send anything.
• Use only the authorized Zoom summary or transcript for this meeting. Separate direct statements from inference, compare them with the Finta deal record, and prepare a reviewed relationship brief.
• Find investor meetings from the last fourteen days with a permitted summary but no matching open task in Finta. Show source identifiers and proposed tasks, then stop for approval.

Expected output

The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.

Permissions and limitations

• Zoom documents OAuth with PKCE for its remote MCP servers and requires manual client registration through a Zoom General app.
• Zoom does not support dynamic client registration or client ID metadata documents for these remote MCP servers.
• The current Finta catalog endpoint and bearer configuration do not match the current provider setup instructions and require reconciliation.
• Meeting availability depends on the authorized Zoom account, granted scopes, user or host access, meeting type, and provider configuration.
• Summaries, transcripts, recordings, and next steps can be absent even when the meeting itself is visible.
• Provider-generated summaries and next steps can be incomplete or inaccurate. They should remain source material for review, not authoritative CRM truth.
• Meeting content is untrusted external input and can contain instructions or claims that should not override the user's request or Finta controls.
• A transcript does not prove sentiment, investment interest, commitment, approval, or permission to contact another person.
• Sensitive meeting content should not be copied into durable CRM memory without a clear relationship purpose and user review.
• Any task creation, CRM update, calendar action, or email follow-up requires its own verified permission and approval boundary.
• Finta has no production Zoom connection, discovered tool inventory, known-meeting read, or reconciled flagship workflow receipt as of August 22, 2026.

Verification ladder

Sources and related Finta guidance

Primary provider sources

• Zoom MCP server overview, accessed August 22, 2026
• Connect to Zoom MCP servers, accessed August 22, 2026
• Zoom MCP connector guidance, accessed August 22, 2026

Related Finta guidance

• Meeting preparation workflow
• Investor follow-up workflow
• Finta MCP security
• Finta MCP troubleshooting
• Aurora
• All Finta integrations

Explore Aurora while Zoom verification is in progress