Meeting Notes

Produce meeting minutes, decisions, and a task list from uploaded transcripts or notes.

Meeting Notes works with written transcripts and meeting notes. It creates a concise meeting summary, decisions, and structured action items, and keeps the source available for review. The starting template processes documents; it does not record a live meeting or promise speech transcription.

Create meeting notes

1. Create Meeting Notes and open the app.
2. Upload a transcript or notes document to the managed file area.
3. Watch the ingestion run until results are available.
4. Select the meeting in the meetings table.
5. Read the minutes and review the corresponding action items alongside the original.

The meetings table shows the meeting and its action count. The action table contains meeting, task, owner, and due-date fields. The minutes include a brief summary and decisions. The document viewer lets you check whether a claimed decision or assignment is supported by the source.

Review assignments and dates

An action owner or due date may be missing or ambiguous in the notes. Review those fields before assigning work. Preserve uncertainty instead of treating an inferred date or an informal mention as a commitment. When the source uses a relative date, confirm the meeting date and intended timezone before relying on the output.

Check whether the model split a compound action into several rows or merged several tasks into one. The action count describes generated rows, not a guarantee that every commitment was identified. Use the full minutes and source to confirm coverage.

Reprocess and organise

Keep distinct meeting documents recognisable. If you upload revised notes, inspect which source revision produced the currently displayed minutes. A new ingestion can produce differently worded summaries or changed task boundaries. Check saved results before repeating an interrupted run.

Use the builder to change the table columns and presentation, or the ingestion workflow to change the summary instructions. If you add a task-management connection, explicitly map reviewed tasks to the destination and consider duplicate prevention before running external writes. The starting template’s task list does not automatically notify owners or create calendar events.

For missing pages or incorrect text, inspect document processing before changing the summarisation prompt.

Parameter reference

These are the starting template’s declared parameters. Your saved app can have its own version of the schema. A default applies when no explicit value is supplied; a required field still needs a valid value.

• title: exposed as an app interface parameter.

Connection slots

Choose compatible saved connections for user-supplied slots. Managed slots are supplied by Strive. Disabling an optional slot stops its use without necessarily deleting the saved binding. See connector policy.

Included workflows

Inspect the saved app’s workflows for changes made after creation. A workflow’s presence does not mean that every interaction runs every workflow.

Output format: meeting_summary

The minutes of one uploaded transcript: a title, a summary and the action items with owner and due date.