Skip to content

Granola: enable auto schedule + emit lightweight new-meeting activity#883

Open
harshithmullapudi wants to merge 2 commits into
mainfrom
granola-schedule-audit
Open

Granola: enable auto schedule + emit lightweight new-meeting activity#883
harshithmullapudi wants to merge 2 commits into
mainfrom
granola-schedule-audit

Conversation

@harshithmullapudi
Copy link
Copy Markdown
Member

Summary

  • Add schedule.frequency (*/15 * * * *) and enableAutoRead: true to Granola spec so the scheduler registers the Trigger.dev schedule.
  • Change Granola SYNC to emit a lightweight activity (Gmail-style): New meeting: <name> and avoid calling get_meeting during scheduled sync; include a stable meeting identifier when available.
  • Preserve lastSyncTime semantics so we only announce newly-seen meetings.

Files touched

  • integrations/granola/src/index.ts
  • integrations/granola/src/schedule.ts

Notes

This PR intentionally reduces activity payload size; the main agent can fetch full meeting details on demand using the meeting id/reference.

harshithmullapudi and others added 2 commits May 28, 2026 07:18
Add `schedule` and `enableAutoRead` to the Granola spec so the
scheduler creates a Trigger.dev cron (every 15 min) on account
install — previously both gates were missing so SYNC was unreachable.

Rewrite handleSchedule to emit one lightweight single-line activity
per meeting using only list_meetings data (no get_meeting call),
mirroring Gmail's createActivityMessage pattern. State is now only
pushed when meetings are actually found, matching Gmail behavior.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Simplify the emitted activity message from the verbose
`Meeting in Granola: "Title" (meeting_id: ..., attendees: ...)` format
to the concise `New meeting added: <title> (id: <id>)` form, preserving
the stable meeting identifier when available so the main agent can fetch
full details on demand.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant