Brief recurring meetings with Glean Triggers and Cursor Automations

Use a Glean calendar trigger to start Cursor Automations before a recurring meeting, summarize what changed, and update the project tracker.

~1 hrAdvanced

Problem

A recurring project meeting starts, and the first few minutes disappear while everyone reconstructs what changed. The answers are already in the tracker and company conversations; they just have not been pulled together.

Thirty minutes before the meeting, Glean gives Cursor the event and Cursor prepares one focused project update. Your team can start with the brief instead of building it live.

Architecture

Google CalendarAn indexed calendar event is coming up

Glean TriggerSends the event 30 minutes before it starts

Cursor AutomationChecks the meeting and gathers what changed since last time

Project trackerLeaves one focused update on the project

Prerequisites

Glean Triggers enabled with an ahead-of-event calendar preset available and Google Calendar events indexed

A Cursor plan with Automations and webhook triggers, which is a paid feature

Cursor connected to the project tracker over MCP with permission to read issues and write project updates; Glean MCP is optional

Node 20+

Steps

1

Set up the automation kit

npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/pre-meeting-brief pre-meeting-brief

2

Create the Cursor Automation

Create a webhook-triggered Cursor Automation and connect the tracker. Add Glean MCP if you want cited context, then paste the prompt from automation-prompt.md and fill in its three placeholders. Save the automation before copying its webhook URL and bearer token into the ignored .env file.

3

Verify the delivery contract with no credentials

Use the recorded events to check calendar delivery and the recurring-brief workflow before connecting real accounts.

cd pre-meeting-brief && npm run verify:fixture

4

Sign in to Glean

Use the shipped OAuth flow; it discovers your tenant and registers a client dynamically. If OAuth is unavailable, use a `TRIGGERS`-scoped API token.

cd pre-meeting-brief && npm run login -- --email "<work-email>"

5

Preview your calendar events

See which presets your deployment offers and review recent indexed events. Use real meeting titles to test your pattern before registering anything. This step is read-only.

cd pre-meeting-brief && npm run preview

6

Enable the automation

Enable the automation before testing. A disabled automation might ignore a delivery, so the receiver test would prove nothing. Enabling it only allows Cursor to run; the webhook URL and key stay private. Registering the Glean trigger later puts it in production.

7

Test it before going live

Webhook triggers do not have a test button, so send one delivery yourself. The default command uses a non-matching title and writes nothing. After it succeeds, ask for explicit approval before running `npm run test:webhook -- --write`; that path creates one tracker update and each repeat is a new occurrence.

cd pre-meeting-brief && npm run test:webhook

8

Register the calendar trigger

Setup reads the preset catalog, checks the selected preset's inputs, and rejects unsupported values. Set `GLEAN_TRIGGER_INPUT_TITLE` to the reviewed pattern so Glean filters by title at the source. Choose a calendar preset that supports delivery 1,800 seconds before the event.

cd pre-meeting-brief && npm run setup

9

Try one scheduled meeting

Schedule a meeting that matches your title pattern and starts more than 30 minutes from now. Confirm one run and one update on the configured project. The first brief looks back seven days; later briefs cover only the time since the previous one.

One project, chosen up front

The automation updates only the configured project; it cannot infer a different destination from meeting content.

Missing data stays missing

An unreachable tracker writes nothing and reports it. A genuinely quiet interval says so. The automation never fills the gap with guesses.

Meeting titles are checked twice

Glean filters by a case-insensitive substring, so most unrelated events never leave Glean. Cursor checks again because the delivery is untrusted and substring matches can be broader than expected.

Take it further

• Add a reviewed project map when one automation needs to serve several meeting series.
• Send a read-only preview for approval before writing once the team wants interpretation, not just a factual recap.
• Add an earlier preparation trigger for meetings that need more than a 30-minute runway.
• Pair it with Gong call follow-up to use the same delivery model in n8n.

Try it

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.

• Choose your tool
  Install the plugin

  1

  claude plugin marketplace add gleanwork/glean-cookbook

  2

  claude plugin install cookbook@glean-cookbook

  Run the recipe

  /cookbook:pre-meeting-brief

  Run /reload-plugins to pick it up without restarting.

View source

Runs the recipe through the Glean cookbook plugin.

Auth

Run the authenticate step on this page. It discovers your tenant from work email and signs you in with OAuth, using the shipped login command. If OAuth is unavailable, create a scoped Glean-issued token in Token Management (TRIGGERS).

This recipe uses a third-party API key in addition to Glean. Follow the authenticate step on this page.

At a glance

SurfacesPlatform API

StatusShowcase

Time~1 hr

Required scopes

TRIGGERS