Meeting prep briefs: Calendar → Notion + Linear → Slack

Enable the Calendar API and configure OAuth consent

Google Cloud Console → APIs & Services → Library → search "Google Calendar API" → Enable. Then APIs & Services → OAuth consent screen → set App name and User type (Internal only works inside a Workspace domain; External needs a Google review to distribute widely, but External + Testing mode is enough for a team running this for itself).

Create a Web application OAuth client

Credentials → Create Credentials → OAuth client ID → Web application — not Desktop app. The official Desktop quickstart only walks through a one-off local interactive authorization; it does not cover persisting a refresh token for an unattended poller, which is what this needs. Build the authorization URL with access_type=offline — omit it and the access token has no way to renew itself silently once it expires.

Scope to read-only events, nothing wider

Use calendar.events.readonly (full value in the snippet) — Google's own scope list describes it as "View events on all your calendars", narrower than the calendar.readonly scope most tutorials default to, which also grants calendar metadata and settings this workflow never touches.

https://www.googleapis.com/auth/calendar.events.readonly

Poll a narrow time window — this is not the anti-pattern Google warns about

Google's own quota guide tells you not to repeatedly poll a calendar and to use push notifications instead — but that advice is about watching for content changes (events added or edited). This workflow needs something Calendar has no push mechanism for at all: a "meeting starts in 30 minutes" alert. reminders.overrides only fires to email or popup, never a webhook, so there is no native way to be told when wall-clock time crosses a threshold. Polling a 30-minute window every 5–10 minutes is the only path, not a shortcut around the documented best practice. Both timeMin and timeMax are exclusive bounds and both must carry a timezone offset — a bare timestamp is rejected. singleEvents=true is required before orderBy=startTime is accepted; without it, a recurring meeting comes back as one recurrence rule instead of the specific instance starting soon.

GET https://www.googleapis.com/calendar/v3/calendars/primary/events
  ?timeMin=2026-08-08T09:30:00-04:00
  &timeMax=2026-08-08T10:00:00-04:00
  &singleEvents=true
  &orderBy=startTime
  &maxResults=10
Authorization: Bearer {access_token}

Create the integration at the current URL

The old notion.so/my-integrations now 301-redirects — create the connection at app.notion.com/developers/connections instead (Developer portal → Connections → New connection; requires workspace-owner permission). Under Capabilities, check only Read content; this workflow never writes to Notion.

Add the connection to every page or database it needs

A new connection starts with access to nothing. Open each project page or database to be matched against → "•••" menu → Add connections → search for and select the connection by name. There is no workspace-wide grant — repeat per page or database.

(Optional) Record the project database's data source id

If the team keeps a structured "Projects" database with a Relation or Select property per project, retrieve it once and keep its data_source_id — querying that by property filter is more reliable than the title search in the flow below, since it is not limited to substring matching.

Know the shape of the title search

query matches only page and data_source titles, not page body content, and it is a substring match with no fuzzy tolerance. Take the meeting title (or its core phrase, stripped of dates and meeting-series numbers) as query — a wider search only pulls back noise, it does not increase the chance of finding the right doc.

{
  "query": "Q3 Roadmap Sync",
  "filter": { "value": "page", "property": "object" },
  "sort": { "direction": "descending", "timestamp": "last_edited_time" },
  "page_size": 5
}

Create a personal API key

Linear → Settings → Security & access → Personal API keys → New API key. Send it as the raw Authorization header value — no "Bearer " prefix, the most common source of a 400 here.

Look up team ids once

Run a one-off teams { nodes { id key name } } query and store the ids the polling job needs — every Linear GraphQL call is addressed by id, not by name.

Use searchIssues, not the deprecated issueSearch

The schema still defines issueSearch but flags it "[DEPRECATED] ... use searchIssues instead" — a pre-2025 tutorial using it is pointing at an endpoint on its way out. searchIssues runs full-text and vector search, optionally weighted with teamId, and carries its own rate limit — 30 requests/minute — separate from the account's general 5,000-requests/hour key limit. When several meetings land in the same poll window, queue their searchIssues calls rather than firing them concurrently; the 30/min ceiling bites well before the general limit does. If the meeting title is itself a project name, searchProjects first and pull that project's issues instead — it is more precise than a full-text search over every issue title.

query MeetingRelatedIssues($term: String!) {
  searchIssues(term: $term, first: 10) {
    nodes {
      identifier
      title
      state { name }
      url
    }
    totalCount
  }
}

# variables
{ "term": "Q3 Roadmap Sync" }

Create the app with two Bot Token Scopes

api.slack.com/apps → Create New App → From scratch → OAuth & Permissions → Bot Token Scopes: chat:write and users:read.email. Skip im:write and channels:manage — chat.postMessage's channel parameter accepts a Slack user id directly and opens the DM itself, so there is no separate conversations.open call to make first.

Install to workspace

OAuth & Permissions → Install to Workspace → copy the xoxb- Bot User OAuth Token.

Know the DM payload shape

channel takes the Slack user id returned by users.lookupByEmail, not a channel id — Slack opens the DM conversation on the first post if one is not already open.

{
  "channel": "U024BE7LH",
  "text": "Pre-read for Q3 Roadmap Sync (starts in 25 min)",
  "blocks": [
    { "type": "section", "text": { "type": "mrkdwn",
      "text": "*Q3 Roadmap Sync* — starts in 25 min\n\n*Notion docs:*\n• <https://notion.so/...|Q3 Roadmap Draft>\n\n*Linear issues:*\n• <https://linear.app/acme/issue/ROAD-88|ROAD-88> In Progress" } }
  ]
}