Integrations · Call transcripts
Marcora + Wispr Flow
Bring recorded Wispr Flow meetings into a launch, campaign or other project. Keep the conversation behind your decisions available when shaping content plans and writing from them.
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
Carry Recorded Meeting Decisions Into the Next Brief
Revisit the decisions and questions in a recorded meeting before preparing a launch brief or campaign draft. Keep that conversation in the project alongside approved company knowledge so the writing reflects the discussion.
How it works
Keep Meeting Transcripts Distinct From Dictation
Choose recorded meeting transcripts from Wispr Flow. Dictated text is outside this call-import path.
1. Connect Wispr Flow and find recorded meetings relevant to the project. Calendar-backed attendance is supported. 2. Choose a recorded meeting and review its source details. If a search matches more than 1,000 recordings, it is refused; narrow the date range and search again. 3. File the conversation with its project and review its actual audience.
Source details
Review What the Source Provides
For your own recordings, Marcora can add participant emails and identify colleagues or external participants. A recording someone shared with you arrives with attendee names only: no emails, no internal/external labels and no automatic company details. Calendar-backed attendance is supported.
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. Automatic imports stay Only me for recordings shared with you, calls with 2 or fewer speakers or a speaker Wispr Flow doesn't list, 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 Wispr Flow
Can I import Wispr Flow calls now?
Yes. Wispr Flow recorded-meeting imports are available in Beta. Calendar-backed attendance is supported. This call-import path is for recorded meetings, not dictation.
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. Automatic imports stay Only me for recordings shared with you, calls with 2 or fewer speakers or a speaker Wispr Flow doesn't list, 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 →What are the Wispr Flow import limits?
Wispr imports recorded meetings, not dictation, and supports calendar-backed attendance. Your own recordings can include participant emails and colleague/external identification. Shared recordings arrive with names only, without emails, internal/external labels or automatic company details. A search with more than 1,000 matches is refused. Narrow the date range to search again.
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 Wispr Flow Conversations to Work
Start with the conversations that matter to your next piece of content.