A recurring project meeting starts, and the first ten minutes disappear into reconstructing what changed since the last one. The updates exist across the project tracker and company conversations, but nobody has assembled them yet.
Thirty minutes before the meeting, a Glean calendar trigger wakes Cursor Automations to gather the changes and update the right project—so the meeting starts with the brief instead of building it live.
Google CalendarAn indexed calendar event approaches its start time
Glean TriggerDelivers the event 30 minutes before with bearer auth
Cursor AutomationFilters the meeting and reads what moved since the last briefScaffold the automation kit
npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/pre-meeting-brief pre-meeting-briefConfigure the Cursor Automation
Create a webhook-triggered Cursor Automation, connect the tracker and optionally Glean MCP, and paste the fenced prompt from automation-prompt.md after replacing all three placeholders. Save the automation, then store its webhook URL and bearer token in the ignored .env file.
Verify the delivery contract with no credentials
Verifies the calendar-delivery and recurring-brief workflow using recorded events.
cd pre-meeting-brief && npm run verify:fixtureSign in to Glean
Use the shipped OAuth flow, which registers a client dynamically. A TRIGGERS-scoped API token is the fallback.
cd pre-meeting-brief && npm run login -- --email "<work-email>"Preview indexed calendar events
Lists what your deployment serves and shows recent indexed events, so the meeting-title pattern is checked against real titles before anything is registered. Read-only.
cd pre-meeting-brief && npm run previewEnable the automation
Enable it now, before testing: a disabled automation may take no action on a delivery, so the receiver test would prove nothing. Enabling only makes it able to run — nobody else holds the webhook URL or key. Registering the Glean trigger, later, is what puts it in production.
Test the receiver before registering
A webhook trigger is a private endpoint with no test button, so post one delivery yourself. The title is built from the pattern you configured, so the run does the work rather than exiting ignored.
cd pre-meeting-brief && npm run test:webhookRegister the trigger
Setup reads the selected preset's required inputs from GLEAN_TRIGGER_INPUT_<FIELD> and rejects unsupported values. For this recipe, select a calendar preset that supports delivery 1,800 seconds before the event.
cd pre-meeting-brief && npm run setupVerify one scheduled meeting
Put a meeting matching your title pattern more than 30 minutes out. Confirm one run and one update on the configured project. On the first run, expect a labeled seven-day lookback; later occurrences cover only the interval since the previous brief.
The automation updates only the configured project and cannot infer a different destination from untrusted meeting content.
An unreachable tracker writes nothing and reports it; a genuinely quiet interval publishes no-movement. The agent never invents either.
The calendar preset does not expose a meeting-title filter, so eligible events reach Cursor. Cursor rejects non-matching meetings before reading the tracker or writing an update.
- Add a reviewed project mapping table when one automation needs to serve several meeting series.
- Send a read-only preview for approval before writing the project update, once the team wants interpretation rather than a purely factual record.
- Add a separate, earlier preparation trigger for meetings that need more than a 30-minute briefing window.
- Combine with the Gong call follow-up to see the same delivery contract driving a workflow tool instead of an automation.
Schedule a meeting whose title matches the reviewed pattern more than 30 minutes ahead
At 30 minutes before start, one run reports what moved since the previous brief and writes one update on the configured project.
Run two occurrences of the same recurring meeting, completing work between them
The second brief covers only the interval since the first, read from the marker the first run left — not a fixed seven days. Work finished in between appears once, in the second brief.