Meeting intelligence: botless transcripts and summaries

Use Screenpipe for botless meeting memory: live transcripts, speaker naming, calendar context, summaries, transcript copy, and API automation.

Screenpipe records meetings without a bot joining the call. It captures the meeting window, microphone, optional system audio, transcript, speaker labels, calendar context, and the surrounding screen history.

Summarize in one click

Open a meeting note and hit Summarize — Screenpipe reads the transcript and the screen captured during the call, then writes decisions, action items, and follow-ups into the note. Summarize buttons sit at the top and bottom of the note dock.

one-click summary from the meeting note — decisions, actions, risks

Bring your Granola notes with you

Connect Screenpipe MCP and Granola MCP to the same AI assistant. Keep Screenpipe running, then copy this prompt into that assistant. It reads the Granola meetings you select and adds their notes to matching meetings already in Screenpipe.

Screenpipe’s MCP tools can update existing meetings, but cannot create historical meetings or import audio and transcripts. Unmatched Granola meetings stay in a separate Markdown export. Your assistant’s model processes the notes you ask it to read.

Bring selected Granola notes into matching Screenpipe meetings

CopiedCopy prompt

For future calls, follow the setup checklist below. Screenpipe captures meeting audio and screen context, so your notes can refer back to what was shown during the conversation.

What Screenpipe captures

Layer	What it adds
Screen	Slides, docs, pricing pages, dashboards, chat, and CRM screens shared or viewed during the call
Audio	Local transcript from your microphone and selected audio sources
Speakers	Speaker IDs, names, aliases, similar-speaker suggestions, and merge history
Calendar	Attendee names, meeting title, and time window for better labeling
Notes	AI summaries, action items, and follow-up context
Timeline	Frame links and time anchors you can revisit later

Setup checklist

1. Open Settings → Audio & meetings, enable audio recording, and choose the microphone and system audio sources you want.
2. Connect Google Calendar in settings -> connections if you want attendee-aware speaker naming.
3. Open the meeting app normally: Zoom, Google Meet, Microsoft Teams, Slack huddles, or another call surface.
4. Let Screenpipe record and transcribe in the background.
5. Open the meeting from the timeline or search with content_type=audio.

Quick verification (protected routes may need the local API bearer token):

curl http://localhost:3030/health
curl "http://localhost:3030/search?content_type=audio&limit=1"

Calendar context is especially strong for 1:1 meetings. When the meeting has exactly two attendees, Screenpipe can infer the other speaker more reliably.

Enable real-time transcription with Live meeting notes

1. Open Settings → Audio & meetings and enable audio recording. The meeting controls are hidden when audio is disabled.
2. Turn on Live meeting notes.
3. Choose Current transcription engine, Screenpipe cloud live, or Direct Deepgram live. The current engine must not be disabled; cloud live requires sign-in, and a direct provider needs its own credentials.
4. Start a short call and open the active meeting note. Speak a test sentence and check for new captions. Verify system audio too if you need the other participants.

Live meeting notes handles captions for the active meeting separately from background transcription. It does not restore missing audio from an earlier call or fix a failed AI summary. Cloud/direct live providers send audio to the selected service. See privacy data flow.

If a setting is missing, check your app version and available updates. Do not substitute an unrelated toggle. For missing captions or summaries, follow meeting recovery.

Live transcript workflow

Use the meeting transcript sidebar to:

• Rename a speaker once and propagate the label through the meeting
• Search for similar speakers before merging duplicates
• Copy the full transcript as plain text
• Open the related timeline moment when you need visual context
• Summarize the meeting with your default AI or a selected scheduled task

Summarize with a scheduled task

Meeting summaries can use any installed or store scheduled task. Use a scheduled task when you want a repeatable output format, CRM writeback, an Obsidian note, or a sales-call summary that always includes the same fields.

Good summary task instructions include:

Summarize the meeting in this format:

## decision
## customer pain
## objections
## action items
## follow-up email draft

Use transcript evidence and include timeline links when useful.

For customer calls, add evidence fields so the output is usable:

Summarize the meeting.
Include:
- customer goal
- current workflow
- objections or privacy concerns
- requested integrations
- next action
- exact transcript quotes only when useful

Speaker cleanup

curl "http://localhost:3030/speakers/unnamed?limit=10"

curl -X POST http://localhost:3030/speakers/update \
  -H "Content-Type: application/json" \
  -d '{"id": 1, "name": "Sarah Chen"}'

curl "http://localhost:3030/speakers/similar?speaker_id=1"

curl -X POST http://localhost:3030/speakers/merge \
  -H "Content-Type: application/json" \
  -d '{"speaker_to_keep_id": 1, "speaker_to_merge_id": 2}'

Name speakers from the UI first when you can. Use the API when building cleanup tools or recurring workflows.

Meeting APIs

List and search meetings

# list recent meetings
curl "http://localhost:3030/meetings?limit=20"

# search by title, attendees, or notes (case-insensitive)
curl "http://localhost:3030/meetings?q=customer+sync&limit=20"

# filter by date range
curl "http://localhost:3030/meetings?start_time=2026-05-01T00:00:00Z&end_time=2026-05-31T23:59:59Z"

# combine search with date range
curl "http://localhost:3030/meetings?q=sprint&start_time=2026-05-01T00:00:00Z&limit=10"

The q parameter searches across meeting title, attendees, and notes with case-insensitive substring matching.

Manage meetings

curl "http://localhost:3030/meetings/status"

curl -X POST http://localhost:3030/meetings/start
curl -X POST http://localhost:3030/meetings/stop

curl -X POST http://localhost:3030/meetings/merge \
  -H "Content-Type: application/json" \
  -d '{"meeting_ids": [12, 13]}'

Use the meetings API when an automation needs meeting lists, search, current meeting status, merge cleanup, or downstream note updates.

Zoom, Meet, and Teams tradeoffs

Tool	Best setup	Notes
Zoom	Mic plus system audio, Zoom connection when you need cloud recording metadata	OAuth can enrich meeting metadata; local capture still works without a bot
Google Meet	Mic plus system audio, Google Calendar connection	Calendar attendee context helps speaker naming
Microsoft Teams	Mic plus system audio, Teams or Microsoft 365 connection for structured context	Useful for enterprise rollouts and meeting-linked docs

Troubleshooting

Symptom	Try this
Empty transcript	Verify microphone permission, selected device, and content_type=audio search
Late transcript	Check background batch processing, or configure Live meeting notes for an active call
Summary fails or says invalid bundled pi compaction patch	Follow meeting recovery; preserve the transcript and record the exact error
Speaker names wrong	Connect calendar, rename the speaker, then merge similar speakers
Duplicated meeting	Use merge from the UI or /meetings/merge
Summary missed context	Choose a custom scheduled task that also searches screen text and accessibility context during the meeting window
Audio dropouts	Reduce batch duration, select fewer audio devices, or use a faster/cloud transcription engine

Related pages

• Meeting transcription
• Connections
• API recipes
• Scheduled task debugging