teams-meeting-pipeline

Automating Microsoft Teams meeting summarization is handled by creating, managing, and summarizing meetings via the Hermes CLI, which processes meeting notes, transcripts, and action items automatically.

Managing Microsoft Graph webhook subscriptions involves using the Hermes CLI to create, renew, and delete subscriptions, ensuring timely notifications for your Microsoft Teams meeting pipeline.

Checking the status of a failed Teams meeting summary job requires inspecting stored jobs and pipeline status using the Hermes CLI, which also allows you to replay failed jobs for fresh summaries.

Using the Hermes CLI is required to process Microsoft Teams meeting transcripts, as it handles the Graph subscriptions, job status inspection, and the actual meeting summarization pipeline operations.

Validating configuration and token health before summarizing a meeting is done by running the 'hermes teams-pipeline validate' command, ensuring your environment variables for Microsoft Graph access are correctly configured.

A Microsoft Graph subscription failing to generate summaries often indicates a configuration issue; you must validate token health and environment variables, then inspect and replay the failed job using the Hermes CLI.