note1-notes-and-trackers

note1 notes and topic trackers

Every tool takes an optional teamId (omit it for the active team) and acts with the signed-in user's own permissions.

Meeting notes and agenda

A meeting has two layers of notes:

• Personal notes: talking points and reminders, private to the user.
• Shared agenda: visible to the people in the meeting.

note1_get_meeting_notes (with meetingId) returns both. Every block has a ref. Find the meetingId first with note1_search_meetings, note1_list_meetings or note1_get_calendar when the user did not give one.

Edit

Always read first with note1_get_meeting_notes, then merge into what is already there. Then call note1_update_meeting_notes:

• scope: personal (default) or shared. Shared edits change what other people see and need edit access to the meeting. Use shared only when the user says agenda, shared or team notes, and mention that others will see it. If it is refused for lack of access, say so and offer to put it in their personal notes instead.
• operations (up to 60), each with op of insert, update or delete:
  • update and delete target a block by ref from the read.
  • insert places a block after a ref (or "start" / "end"), or under a heading's name so it lands at the end of that section (the heading is created when missing). type is one of p, h2, bullet, number, todo, quote, code, and defaults to bullet. checked is for todo.
• replaceWith: markdown that replaces every block. Use it only when the user asked to rewrite everything, and show or summarize what will be lost first. Prefer operations otherwise.

Use either operations or replaceWith in one call. After the call, tell the user what changed, and read the notes again before a second edit rather than reusing old refs.

Topic trackers

A topic tracker is a named set of phrases note1 watches for across meetings. Each phrase is broad (matches variations) or exact (the words as written).