---
title: Meetings in People
description: "A one-page brief on each person before a meeting, your next meetings on Today with their people, an after-meeting note that proposes the deal move, field updates and next step, and the Granola sync that files each meeting for you."
section: cloud
order: 170
audience: [user, operator, agent]
sources: ["services/nodejs-cloud/lib/people/meetings.ts", "services/nodejs-cloud/lib/people/meetings-model.ts", "services/nodejs-cloud/lib/people/granola.ts", "services/nodejs-cloud/lib/people/tools-meetings.ts", "services/nodejs-cloud/components/people/MeetingsSettings.tsx", "services/nodejs-cloud/app/api/cron/people-meetings/route.ts", "services/nodejs-cloud/app/api/workspace/people/meetings", "services/nodejs-cloud/migrations/0292_people_meetings.sql", "services/nodejs-cloud/lib/people/brief.ts", "services/nodejs-cloud/lib/people/brief-model.ts", "services/nodejs-cloud/lib/people/upcoming.ts", "services/nodejs-cloud/lib/people/upcoming-model.ts", "services/nodejs-cloud/lib/people/attendees.ts", "services/nodejs-cloud/lib/people/after-meeting.ts", "services/nodejs-cloud/lib/people/meeting-note-model.ts", "services/nodejs-cloud/lib/people/tools-meetingbrief.ts", "services/nodejs-cloud/components/people/TodayMeetings.tsx", "services/nodejs-cloud/components/people/BriefView.tsx", "services/nodejs-cloud/components/people/MeetingDebrief.tsx", "services/nodejs-cloud/app/(people)/people/[id]/brief/page.tsx", "services/nodejs-cloud/app/(people)/people/meetings/[id]/page.tsx", "services/nodejs-cloud/migrations/0298_people_meeting_upcoming.sql", "services/nodejs-cloud/migrations/0299_people_note_changes.sql", "services/nodejs-cloud/lib/people/calendar-log.ts", "services/nodejs-cloud/components/people/MeetingAttendees.tsx", "services/nodejs-cloud/migrations/0383_people_meeting_calendar_log.sql", "services/nodejs-cloud/lib/calendar/ics-feed.ts", "services/nodejs-cloud/lib/people/calendar-review.ts", "services/nodejs-cloud/lib/people/calendar-review-model.ts", "services/nodejs-cloud/lib/people/calendar-history.ts", "services/nodejs-cloud/components/people/MeetingHistory.tsx", "services/nodejs-cloud/migrations/0384_people_meeting_calendar_review.sql"]
features: [cloud.page-people]
---

Venom People helps on both sides of a meeting: a brief on each person before it, and a short note after it that turns
into the next step. If you take notes in Granola, it can also file each meeting for you (below).

## Before a meeting

**People → Today** has a **Meetings** section with today's and tomorrow's meetings, in your own time zone. Each row shows
the time, the title, the deal it belongs to and the people in it as chips. Tap the title to open the meeting's brief
(`/people/meetings/<id>`): a shared header with the time, title and deal, then a brief for each person in it, most senior
first. The section is hidden when you have no meetings with people in them; meetings nobody was matched to fold under
**more**.

### Where meetings come from

Meetings for the next seven days come from:

- **Venom bookings**: the person who booked, and the booking's deal.
- **Your Google or Microsoft calendars**: the attendees' emails, matched against the emails of people you can see in
  People (your own first). Venom stores the event's id, start, end, title and location, the people it matched and how
  many attendees matched nobody. For an upcoming meeting, an unmatched attendee is only that count: their email and name
  are not kept. Once the meeting has ended, they go to your own review list until you decide (see
  [People you met who are not in People](#people-you-met-who-are-not-in-people)). Attendees and the location are
  read in the calendar's existing sync, from the same answer and with the permission you already gave: a calendar
  connected for free/busy only gives none, and **People → Settings** marks it "free/busy only".
- **Your .ics feeds**: the same, from each event's `ATTENDEE`, `ORGANIZER` and `LOCATION` lines, read in the fetch
  Venom already makes to keep the feed's busy time ([.ics feeds](/docs/calendar/ics-feeds.md)). A feed has no address of
  its own, so your sign-in email and the addresses of your other connected calendars count as you: they are never
  matched, and an event you declined (`PARTSTAT=DECLINED`) is left out. Rooms and other resources are skipped. A
  feed is read whole each time, so an event that left it, or was cancelled, leaves People too.

You can connect as many Google and Microsoft accounts and .ics feeds as you meet people through: a work account, a
personal one, a client's. **People → Settings → Calendars for meetings** lists the ones you connected and has **Connect
Google calendar** and **Connect Microsoft calendar** (shown when your organisation's Google or Microsoft sign-in is set
up) and **Add an .ics feed**, which opens **Calendar → Connections** where **Add feed** takes the address.
Each opens the provider's account picker, so you can add another account while signed in to the first, and brings you
back to People. The same accounts are in **Calendar → Connections**. Every connection is yours alone: nobody else in
the organisation reads its meetings.
- **The title**, where no attendees could be read: a title such as "Ann Lee / Acme" or "Ann <> Acme" names one of your
  own people. It shows as **Ann Lee?** until you tap the tick to confirm it.
- **Granola**, for a meeting filed today. When Granola recorded nobody but you (an in-person meeting with no invite,
  say), the row stays out of **more** and says "Granola recorded no attendees. Add who was there".

Tap **+** on a row to add a person by hand, and the **x** on a chip to remove a wrong match. A removed person is not
added back to that meeting. Adding one of your own people to a Granola meeting files that meeting on them, the same way
the sync files an attendee (see [Granola](#granola)). This also works on a calendar event or booking that is the same
meeting: the same start time and the same title, which is how Today shows the two as one row.

### The brief

A person's brief (`/people/<id>/brief`, the **Brief** button on their page, or **Brief** on a row of the list) fits on
one phone screen and prints on one page. Every line is a fact Venom already holds, with its date. A part with nothing
in it is left out:

- **Who**: their title and company now and since when, earlier companies, seniority, country, how you met and since
  when you have known them.
- **Open**: your open next step, an open Today follow-up, a last message either way that has no reply, and every
  "Open loop:" line in your notes and interactions.
- **Last**: your last three interactions, each with its date and its first sentence.
- **Deals**: their deals in Funnel, with the stage, the value and when the stage last changed.
- **At their company**: the five people you know at their current company, most senior first, then the warmest.
- **Connections**: who they know in your People, and which colleagues also know them.
- **Remember**: "Remember:", "Family:", "Interests:" lines in your notes, and their tags.

**Suggest talking points** makes one call to your organisation's model, under People's daily AI limit: three points,
each naming the fact it rests on. Nothing is sent until you press it, and the brief works without it.

A colleague's shared person shows only what you may see: no private notes, interactions, warmth or outreach of theirs.
Deals follow Funnel's rules for who sees what.

## After a meeting

Once a meeting is over, its row on Today asks **How did it go?** (and so does the meeting's brief). Meetings that ended
in the last 36 hours and have no answer yet wait in their own **How did it go?** group on Today. Write what happened
and press save. The note is logged as a meeting on the person's timeline. If Granola already logged that meeting on the
same day, its summary is shown above the box, read-only: what you write is saved as a note of its own, saving with the
box empty just uses Granola's, and the meeting is never logged twice. With several of your people in the meeting, the
note goes to each one you tick (all of them to start with). Only people confirmed in the meeting are offered: confirm
an **Ann Lee?** first.

### Calendar meetings on the timeline

An hour after a Google, Microsoft or .ics feed meeting ends, Venom logs it on each of your own people in it: one
**meeting** on their timeline with the event's title, its start time, the location as the place, and the account it
came from ("via ann@acme.com", or the feed's label for a feed). That is who you met, where, and through which account, with nothing to type. People in
it are the attendees matched by email, an **Ann Lee?** you confirmed, and anyone you added by hand.

It is logged once:

- A second run, an edited event, or the same event on two of your connected accounts logs nothing new: a person who
  already has a meeting at that start time (from Granola, from **How did it go?**, or from another account) gets no
  second one.
- When Granola's note of the same meeting arrives (same start time, same title), it replaces the calendar's entry,
  unless you edited that entry.
- Removing a person from the meeting (the **x** on their chip) before it is logged keeps it off them; removing them
  after takes the entry back off their timeline.
- A cancelled or declined event is not logged, nor is a colleague's private person. An attendee who matched nobody
  waits for you in the review list (below).
- Only meetings that ended in the last two days are logged here. **Import past meetings** (below) fills in older ones.

### On a Funnel deal

A meeting on one of your own people who is on a [Funnel deal](/docs/cloud/funnel.md#intros-and-meetings) shows in that deal's
activity, for you only: who, where (the place you typed on the person's page, or the event's location) and when. To log
an in-person meeting, use the person's page (**Met in person**, with **Where**). The deal also shows your next calendar meeting with
someone on it. The **How did it go?** suggestion to move a deal works with the stages of the deal's own pipeline, whichever
pipeline that is.

### People you met who are not in People

When a calendar meeting (Google, Microsoft or an .ics feed) has ended and had someone in it who matches nobody you can
see in People, they wait for you in **People → Settings → To review**: one item per email address, however many
meetings they were in. Each item shows the address, the name the calendar gave (Google's display name, Outlook's name,
an .ics feed's `CN`), the meetings they were in (the newest 20 with date, title, place and account, and how many there
are), and your own people with a close name. Then:

- **It's …** (or `accept` with a person over MCP): the address is added to that person's emails, and the meetings are
  logged on them.
- **Add as new**: a new private person with that name (or one made from the address), the address, and the company
  its work domain stands for; the meetings are logged on them. If someone of yours has that address by then (Granola
  added them, say), the meetings go on that person instead of a twin.
- **Dismiss**: the address, the name and the list of meetings are deleted. Venom keeps only a salted hash of the
  address, so the same person is never asked about again.

Meetings are logged the same way as above: once per person and start time, with the place and "via" the account.

Never asked about: you (every address of yours: your sign-in email and each connected calendar), colleagues on your
organisation's own domains (the same rule as Granola), rooms and resources, addresses that are not people (`noreply@`,
`no-reply@`, `calendar-notification@`, `notifications@`, Google's `group.calendar.google.com` and
`resource.calendar.google.com` calendars and the like), and anyone in a meeting with more than 15 people, rooms left
out: an all-hands is not someone you met.

**Privacy.** This is the one place Venom keeps the email and name of an attendee who matches nobody. It is kept only for
meetings that have ended, only in your own review list (never shown to colleagues, never in anyone else's People), and
only until you decide. Upcoming meetings still keep only the count. An item whose accounts you all removed is deleted
with them.

For a Google or Microsoft meeting the calendar's own sync did not see again after it ended (it only sends changes),
Venom reads that one event once more by its id, with the same connection, after the hour's grace. An .ics feed is read
whole on every sync, so nothing extra is fetched.

### Import past meetings

**People → Settings → Calendars for meetings** lists your calendar accounts, each with **Import past meetings**, and
**Import from all** when you have more than one. Pressing it reads the last 24 months of that account:

- each meeting is logged on your own people in it, with its title, start time, place and "via" the account, once per
  person and start time, so the same meeting through two accounts, a meeting Granola or **How did it go?** already logged,
  or a second import adds nothing;
- people who are not in People go to the review list above.

All-day events, events you declined, cancelled events and meetings with more than 15 people are skipped. Nothing is
read until you press it, and each account is yours alone. A Google or Microsoft account is read with the connection you
already gave it (no new permission), a month at a time, newest first, in the background every 10 minutes; the line
under the account shows how far back it has got and what it found, and the button is back when it is done. If the
provider's rate limit is reached it waits a few minutes and goes on from where it was. An account connected for
free/busy only can't be imported (its attendees are not read): connect it again with full access. An .ics feed is read
once more and gives whatever history the feed holds. Pressing it again later goes over the window again and only adds
what is new.

A weekly meeting over two years is about a hundred entries on one person's timeline. That is the real history: the
timeline pages it as it does any other.

**How did it go?** on a meeting already logged this way saves what you write as a note of its own, and saving with the
box empty just uses the logged meeting, the same as with Granola.

The same single model call that proposes the next step (see
[How did it go?](/docs/cloud/people-keep-warm.md#how-did-it-go)) also reads the note for:

- **the deal**: move the person's open deal to its next stage, to won or to lost, or **Create a deal** when there is
  none and the note shows interest. Stages come from the deal's own pipeline.
- **their details**: a new title, a new company, or a move to another country, in the note's own words.
- **a task**: something you promised ("I'll send the deck by Friday") as a Tasks issue for you.

Each one is a chip: tap the tick to apply it or the **x** to dismiss it. Nothing changes until you tap. Without a model,
or with the day's AI limit used up, the same rules as the next step read the note.

## Granola

If you take meeting notes in [Granola](https://www.granola.ai), Venom People can do the filing after each meeting for you.
Connect Granola once and, from then on, every meeting with a summary is:

- **matched to your people** by the email on the calendar invite. Someone you already have is updated: blank fields
  are filled (their company, from their work domain), nothing you wrote is changed. Someone new is added as a private
  person with their name, email and, for a work address, the company the domain stands for (`frost.co` is Frost);
- **logged** as one *meeting* interaction on each of them, with Granola's summary, the meeting's date and a link to the
  Granola note;
- **turned into tasks**: your own action items (only the ones the notes give to you) become Venom Tasks issues assigned
  to you, labelled `from-meeting`, linking the people and the note.

You and your colleagues are never added: attendees with your addresses, or on your organisation's own domains (its SSO
domains and its members' work addresses), are skipped. Gmail, Outlook and other free-mail addresses never stand for a
company.

### Connect Granola

Go to **People → Settings** (`/people/settings`), section **Meetings (Granola)**, and press **Connect Granola**. Granola
asks you to sign in and allow Venom; you come back to the settings page and the first sync starts right away. It reads
the meetings of the last seven days, then everything that changes after.

Each member connects their own account: the sync reads only your meetings and files them in your own People. Nothing
runs, and nothing is sent to Granola, for a member who has not connected.

Under the same heading you can:

- turn the sync **off** and on again;
- choose how **action items** land: **Create Tasks issues** (the default) or **Suggest them here**, which leaves each
  one in the review list below for you to create or dismiss;
- **Sync now** instead of waiting for the next run (every 10 minutes);
- **Disconnect**, which deletes your Granola sign-in. What was already filed stays, and connecting again never files a
  meeting twice.

The line under the heading shows the account, the last run and what it did, and the last error, if any. "Needs
connecting again" means Granola no longer accepts the saved sign-in: press **Connect again**.

### The review list

The sync never guesses. An attendee with a name but no email waits in **To review**, with your people whose name is
close: press **It's …** to log the meeting on that person, **Add as new** to create them, or **Dismiss**. In suggest
mode your action items wait here too (**Create issue** or **Dismiss**), and so do people from your ended calendar
meetings (see [People you met who are not in People](#people-you-met-who-are-not-in-people)), with or without Granola.
The list is hidden when it is empty.

### People you add on Today

Granola doesn't always know who was there. When you add one of your own people to a Granola meeting on **People →
Today** (the **+** on its row, or the tick on a **Possibly …?**), Venom asks Granola for the meeting and logs it on that
person: one *meeting* interaction with Granola's summary, the meeting's date and a link to the Granola note, shown on
their timeline as **Granola note**. If Granola can't be asked within a few seconds (or another sync is talking to it),
the sync runs right away and does it. Nothing shows on the person until it is filed. A colleague's shared person is
added to the meeting but nothing is written on them. With the Granola sync turned off, nothing is asked of Granola and
the row says "Granola sync is off"; turning it back on files it on the next run. If Granola stops giving the meeting
back (the note was deleted) for six runs in a row, Venom stops asking and the row says "Granola no longer has this note".

If you already answered **How did it go?** for that same meeting before Granola's note arrived, Granola's interaction
becomes the meeting and your answer stays on their timeline as your note on it, so the meeting counts once toward
warmth and last touch. Another meeting with them that day is left alone. Removing the person from the meeting with the
**x** deletes the interaction that adding them created, and your answer counts as the meeting again. If you had left
**How did it go?** empty (so it used Granola's note), it is cleared too and the meeting asks again. People you added by
hand before this feature existed are filed by the next sync run.

The calendar or booking twin must start at exactly the same time as Granola's meeting. Granola's meeting time often
differs from the invite by a minute or two, so in that case add the person on the Granola row instead.

The status line counts the meetings Granola recorded with no attendees ("1 with no attendees").

### Edits and re-runs

Every meeting is recorded once per member: who was matched or added, the interactions logged and the issues created. A
re-run, a reconnect or a meeting that shows up again never adds a person, an interaction or an issue a second time. When
you edit a note in Granola, the interactions it logged take the new summary. Action items are read once per meeting.

### AI and limits

Action items are read by your organisation's own model (its gear) through the internal People key, under People's daily
AI limit, the same as context cards. At the limit the sync stops where it is and carries on the next day; people and
interactions do not need the model. Without a model, meetings are still filed and no action items are made.

A run takes at most 10 meetings per member, inside a time budget; one member's failure is recorded on their row and never
stops the others.

### Privacy and security

- Granola's meeting notes are treated as data, never as instructions: the model is told so, and only short action titles
  and dates are read from its answer.
- The connection is OAuth with PKCE against Granola's MCP server (`https://mcp.granola.ai/mcp`), with Venom registered
  as an app on your first connect. The tokens are sealed in the vault (`VENOM_VAULT_KEYS`) and never shown, logged or
  sent anywhere but Granola. Without a vault, connecting explains that the operator has to set it up.
- Calling Granola is an outbound call your member chose to make, like any connected integration; a self-hosted or
  air-gapped install that never connects Granola never calls it.

## For agents (MCP)

The `people_` tools act for the calling member:

| Tool | What it does |
|---|---|
| `people_meetingsync_get` | Connected or not, on or off, tasks mode, last run, last error, open review items |
| `people_meetingsync_set` | `enabled`, `tasks_mode` (`create` or `suggest`) |
| `people_meetingsync_run` | Run the sync now |
| `people_meetingreview_list` | The review list, with name matches for attendees; `calendar` items carry the email, the name and the meetings |
| `people_meetingreview_decide` | `accept` (with `person`), `create` or `dismiss` one item |
| `people_meetinghistory_get` | Your calendar accounts and where each one's **Import past meetings** is |
| `people_meetinghistory_run` | Import past meetings from one `account`, or from all of them |
| `people_meeting_list` | Your meetings in the next seven days and the last day and a half, with their people (`with_people` for only those that have some) |
| `people_meeting_link` | `attach`, `confirm` (a title's guess) or `detach` a person on a meeting |
| `people_meetingbrief_get` | The brief for a `person`, or for every person in a `meeting`, as text |
| `people_meetingbrief_draft` | Three talking points for a person, each citing a fact (one model call, under the AI limit) |
| `people_todaynote_create` | With `meeting`: "How did it go?" for that meeting; answers the next step and the proposed changes |
| `people_notechange_apply` | Apply one proposed change (the deal move, a field, the task) |
| `people_notechange_dismiss` | Dismiss one proposed change |

Connecting and disconnecting Granola are browser actions only (`GET /api/workspace/people/meetings/granola/connect` and
its callback). The REST twins are under `/api/v1/people/meetings`; see [People for agents](/docs/cloud/people-mcp.md).

## For operators

The cron is `GET /api/cron/people-meetings` (every 10 minutes, `CRON_SECRET`, `?budget_ms=` up to 200 s). The tables
are `people_meeting_sync`, `people_meeting_states`, `people_meeting_ledger` and `people_meeting_reviews` (migration
0292).

The meetings themselves are `people_meeting_upcoming` and `people_meeting_people` (migration 0298), refreshed when Today
or the meeting list is opened and by each calendar sync. The same cron then logs ended calendar meetings on the people
in them (`lib/people/calendar-log.ts`, database only, no outside call; its count is `calendar_meetings` in the cron's
answer): `people_meeting_upcoming.location`, `people_meeting_people.logged_at` and `.interaction_id` (migration 0383).
It then reads ended Google and Microsoft meetings with unmatched attendees once more by id (`ended_meetings`, at most 50
a tick) and goes on with the imports members asked for (`meeting_history`, `lib/people/calendar-history.ts`).
Migration 0384: review items of kind `calendar` in `people_meeting_reviews` with their meetings in
`people_meeting_review_events` (deleted with the account), `people_meeting_upcoming.unknowns_at`, the import
table (one row per account with the window, place reached, lease, counts and last error; deleted with the account) and `people_meeting_history_log` (which person was logged for which start; deleted with the person). Proposed
changes after a meeting are `people_note_changes` (migration 0299). The brief needs no table and no model.
