Skip to main content

Overview

Webhook events for Note resources. All note events use resourceType: "Note".

Event Details

note.created

  • When starting a live-voice note recording
  • When creating a note from a recording file

note.deleted

  • When a user permanently deletes a note

note.recording.completed (Recording paused)

  • Fires after a live recording is paused and Tiro finishes processing the audio, transcript, and paragraphs captured so far
  • Can fire multiple times for the same note because a recording can be paused more than once during a meeting
  • The event name keeps completed for compatibility, but it does not mean the note has ended. Use note.ended for the final state

note.user_content.updated

  • When a user manually edits the note content

note.ended

  • Fires when all processing for the note is complete
  • Unlike note.recording.completed, it fires only once per note

note.participants.updated

  • Triggered when meeting participants are added or removed from a note
  • Does not fire when an existing participant’s name or email is updated
  • The resource field contains the full Note object with the updated participants array

Example Payload

Resource Data

Note events include the complete Note resource data. See the Note API for field descriptions. Important: Note resources contain only metadata. For transcript content, use the List Note Paragraphs API to retrieve the actual text data.

Guide

Distinguish a paused recording from an ended note

Handle interim results at each pause with note.recording.completed, and the final result with note.ended. Example scenario:
  1. Meeting starts → recording begins
  2. Recording pauses → transcript and summary processing → note.recording.completed fires
  3. Recording resumes → processing continues
  4. Recording pauses → note.recording.completed fires again
  5. Recording resumes and ends → note.ended fires
Example handling: