NodClaude

Nod + Claude

Add your meetings to everything else in Claude.

The read-only Nod connector is built so your meetings can join the same chat as email, calendar, Slack, and tickets. Public installation opens after the directory listing is approved.

Awaiting directory approval

After directory approval, Nod can sit alongside the connectors you already use as one more source for Claude to reason across.

GmailGoogle CalendarSlackNotionLinearNod

How it works

Three steps, then it just works.

  1. Capture on your Mac

    Nod listens through your Mac and turns every meeting, call, and voice note into a clean summary and transcript. No bot joins the call, and the audio is never stored.

  2. Add Nod after directory approval

    When the public listing opens, add Nod in Claude, sign in with your Nod account, and approve read-only access. You stay in control and can disconnect any time.

  3. Combine it with everything

    After you authorize it, Claude can pull a meeting and cross-reference it with other connected context in the same answer — matching what was said to a ticket, email thread, or calendar event.

In practice

One question, two connectors.

A standup in Zoom, a review in Google Meet, a customer call in Teams — Nod is in every meeting you take, whatever the app, collecting the knowledge from each. The connector hands that shared memory to Claude, so it can line a call up with your other tools.

Check yesterday's eng sync against our open Linear tickets — is anything we agreed not tracked yet?

Searched Nod · opened “Engineering sync”
Searched Linear · 7 open issues

Cross-referencing the call with Linear, one decision has no ticket:

  • You agreed to add rate limiting to the public API before the next launch — confirmed feasible, but deferred to a later release.
  • Nothing in Linear covers it. The closest, ENG-214 (API hardening), is scoped to auth changes only.

Want me to draft a Linear issue for the rate limiting and link it under ENG-214?

Write a message…

Opus 4.8

Illustrative. Claude only ever sees the meetings in your own Nod account, and only when you ask.

What you can do

Your meetings, combined with everything else.

Reconcile calls with your tracker

Cross-check what a meeting decided against your Jira or Linear board, and spot what was agreed but never ticketed.

Match a call to the email thread

“Does what we said on the call line up with the thread in Gmail?” — Claude reads both and tells you where they diverge.

Prep from the whole picture

Before a 1:1, Claude can pull the last call from Nod plus the calendar invite and Slack DMs, and hand you a brief.

Feed meetings into your projects

Add Nod to a Claude project alongside its docs and connectors, so every call becomes part of that project's context.

Reach the calls you can't export

Recruiter screens, partner calls, a manager's Zoom you don't own — if Nod captured it, it's available to combine.

Turn decisions into next steps

From a messy scoping call, Claude can draft the tickets, the follow-up email, and the calendar hold — in one go.

Already ask across your meetings? You still can.

Nod has its own assistant built in — Ask Nod answers across all your meetings right inside the app, no setup required. The Claude connector doesn't replace it; it's there for the moments you want to mix that meeting memory with the other tools you've connected to Claude.

Useful on day one. Hard to work without by month three.

Start free on macOS, no card. Every conversation you capture today is one you can still ask about a year from now.