meeting-ingestion

You can ingest meeting transcripts by running the ingestion workflow on your transcript file or event stream, which creates dedicated meeting pages with attendees, summaries, decisions, and action items. It automatically enriches attendee pages and propagates entities to related people, companies, and projects with bidirectional backlinks.

Using a meeting ingestion workflow is the best way to parse notes and automatically update entity timelines. It merges timeline entries across all mentioned entities, maintaining cross-linking and timeline consistency for auditability and knowledge discovery.

Yes, you can create brain pages from meeting recordings by running the ingestion workflow on the event stream. The workflow applies attendee enrichment, entity propagation, timeline merge, and bidirectional back-links to meetings, people, and companies.

Bidirectional backlinking works by propagating entities from the meeting transcript to related people, companies, and projects, then creating reciprocal links. This ensures meeting pages link to attendees and entities, while those entity pages link back to the meeting for full traceability.

You need a meeting transcript file or event stream from notes or recordings before ingesting into brain pages. The ingestion workflow requires this source data to parse meetings, create pages, enrich attendees, and propagate entities across your knowledge-management workflow.