Integrations · Call transcripts
Marcora + Google Meet
Bring eligible Google Meet transcripts into a launch, campaign or other project. Keep meeting decisions and open questions close when shaping the content plan and writing from it.
Selected imports and scheduled import rules are available in Beta. Call-generated plans and Follow-ups are available; you control generation and publication.
How it flows · Beta
Why this source
Bring Eligible Google Meet Transcripts Into Context
A launch meeting can settle a message and leave important questions open. Bring its eligible transcript alongside the project brief and approved company context so the next document starts with those decisions.
How it works
Two Source Paths With Different Requirements
Import recent native Google Meet transcripts or eligible historical transcripts saved in Google Docs. The two paths have different requirements.
1. Connect Google Meet to discover every conference you organized within the 30-day window, recorded or not. Only a conference with a finished recorded transcript can be imported. Google provides no meeting title, so Marcora names each imported Meet call by its start time. Participant emails and attendance filtering are unavailable. 2. For historical transcripts saved in Google Docs, connect your own Drive and Docs as the same user. Browse by document creation window. A transcript must include a date, speaker labels and timestamps; notes-only documents do not qualify. 3. Choose an eligible recorded transcript and file it with the launch, campaign or other project it should inform.
Source details
Choose Calls Without an Attendee Filter
Google Meet cannot verify who attended a call. “Calls I attended” and the import rule’s “Attended by: Me / Specific people” options are unavailable for Meet. Organizer-only discovery is not proof of attendance; review the transcript before using it as evidence.
Repeatable workflow
Define How Calls Come In
Use an import rule to keep the source, filters and project filing together. Rules for all five Beta providers can run on selected days and times or use as-ready polling every 15 minutes. Run now is also available. Every automatic Google Meet import is saved Only me, regardless of the rule’s audience.
Put it to work
From Meeting to Plan, Writing and Reference
Keep the meeting with its project while shaping the content needed. When enabled, automatic content-needs processing suggests new plans and matches existing readable content; it does not recommend targeted document updates. You can edit, accept, dismiss or generate directly from Pending. Revisions to existing writing are user-directed, and nothing publishes automatically.
• Use meeting details alongside the launch/campaign brief and approved company knowledge. • New plan suggestions appear as Pending; acceptance is optional before generation, and Produced is not publication. External requests become Follow-ups and are matched against readable existing content first. • Explicitly copy a call summary to Reference Library, or create a blueprint-based reference document, review it, mark Ready and add it. These flows do not auto-sync existing documents. • See the grounding FAQ for the current limits on using conversations as evidence.
Related capability
See the Full Call Transcripts Workflow
Follow one connected meeting through project context, content planning, writing/reference documents and deliberate sharing.
Explore Call transcripts →Questions About Google Meet
Can I import Google Meet calls now?
Yes. Google Meet imports and scheduled import rules are available in Beta. Native discovery lists every conference you organized within the 30-day window, recorded or not; importing requires a finished recorded transcript. Google provides no meeting title, so Marcora names each imported Meet call by its start time. Historical saved Docs need the same user’s Drive and Docs connections, a date, speaker labels and timestamps.
Does this automatically import every meeting?
No. Import rules use your filters and filing choices, with selected days and times or as-ready polling every 15 minutes. The first run uses a recent 14-day discovery window. Every automatic Google Meet import is saved Only me, regardless of the rule’s audience. The Call transcripts page explains Only me and Team sharing.
Can a meeting create or update my content plan?
The call processor suggests new plans and matches existing readable content first; it does not make targeted update recommendations for existing documents. External requests become Follow-ups. Plan suggestions appear as Pending. Generate can run directly from saved Pending or Accepted plans; writing revisions are user-directed, and nothing publishes automatically.
How does Marcora treat a call as evidence?
Calls can appear among a claim’s supporting sources, with a caution note when calls are its only support. A customer’s experience is not company authority. Conversation detection is limited today and does not link to the supporting passage; an improved engine is in development. See the capability page for the current grounding limits.
Explore Call transcripts →Can I filter Google Meet calls by who attended?
No. Google Meet cannot verify attendance. “Calls I attended” and “Attended by: Me / Specific people” are unavailable. Google provides no meeting title, so Marcora names each imported Meet call by its start time. Participant emails are unavailable. Browse historical saved Docs by document creation window; a date, speaker labels and timestamps are all required. Notes alone do not qualify.
Can meeting details become a reference document?
Yes, through explicit user actions using eligible call context. Copy a summary to Reference Library with confirmation, or generate a blueprint-based document, review it, mark Ready and choose Add to Reference Library. A copied summary is not continuously synced, and ingestion does not automatically rewrite existing library documents.
Put Selected Google Meet Conversations to Work
Start with the conversations that matter to your next piece of content.