The meeting writes itself up.
Cedric joins the call as a visible guest, speaks when spoken to, and delivers notes and action items to the channel before anyone asks.
$50 in free credits when you sign up. No card needed.
- The expensive part of a meeting is not the hour; it is the commitments that evaporate after it.
- Cedric joins Google Meet calls as a guest, named in the participant list like anyone else.
- Address it during the call and it takes part; leave it alone and it just listens and writes.
- Notes, decisions, and action items with owners land in the channel afterward, unprompted.
- The recap that needs to go to the other side waits as a draft for your approval, like every send.
What does an AI meeting assistant in Google Meet do?
Most meeting notes are written by whoever lost the coin toss, which is why they are thin, late, or missing. An AI meeting assistant removes the coin toss: invite Cedric to the Google Meet like a person, and it attends as a guest, listens, and writes the meeting up properly, with the decisions and the commitments rather than a transcript nobody rereads.
During the call it is a participant, not a recorder. Address it and it takes part: the number someone half-remembers, the date of the last decision, the thing written down three meetings ago. The rest of the time it stays quiet and keeps track.
Afterward comes the part that changes behaviour: notes and action items, each with an owner, posted to the channel while the meeting is still warm. Because Cedric is the same AI employee that holds your other tools, the follow-ups do not stop at a bullet list: the recap email gets drafted, the agreed next call goes on the calendar, and each of those waits for a yes.
After the call
Commitments, on the record.
Lucia Moreau9:14 AM
@Cedric join our 3pm kickoff with Meridian and keep notes. Flag anything we commit to.
CedricAPP9:15 AM
Notes are in the thread. Three commitments: revised scope by Friday (Lucia), analytics access from their side (promised for today), and a weekly status call, Mondays 11:00. I can draft the recap email to Meridian with all three, held for your approval.
Joins as a guest
Invited like a person, visible in the participant list. No plugin, no bot console, no mystery.
Takes part when addressed
Mid-call look-ups and answers on request; silence and note-taking otherwise.
Writes the minutes
Decisions and action items with owners, posted to the channel while the meeting is still warm.
Connect Google Meet in a minute
No setup project, no workflow builder, no field mapping. The flow is the same for every tool Cedric connects to.
- 01
Install Cedric where your team talks
One click. It joins your Slack like any other member, and everyone shares the same Cedric.
- 02
Connect Google Meet from the dashboard
Open the Integrations page and sign in with Google Meet on its own screen. Cedric never sees or stores your password, and you can revoke the connection in one click at any time.
A fresh connection can look but not touch: read-only until you say otherwise.
- 03
Ask in plain words
Back in the channel, try it: "join the 3pm kickoff and keep notes". You describe the outcome; Cedric picks the Google Meet actions the ask needs. There is nothing to configure.
Connect for the whole workspace so the team shares it, or keep the connection personal. Two accounts are fine too; each gets a short name.
- 04
Let it become routine
Schedule the recurring version of the ask, and let Cedric fold Google Meet into bigger jobs that cross your other tools. Anything that would leave your workspace still comes back as a preview to approve first.
Better in company
The meeting is the middle of a chain. Google Calendar is where Cedric finds the slot and books the call it will later join, and Gmail is where the recap goes out, drafted from the notes and held for your yes.
Booked, attended, minuted, followed up: one assistant carries the whole arc, and you approve the parts that leave the room.
Where the limits are
Cedric attends the meetings you point it at; it does not lurk. It joins as a visible guest, and what it writes up lands where the team can read it. Whether a given call is one an assistant should sit in stays a human decision, and some calls should not be.
Cedric sees what the Google Meet connection grants and nothing more. Access is scoped, logged, and revocable from the dashboard, effective immediately.
Nothing sends itself. An email, a post, a change to a record: anything with consequences comes back as a preview for a human yes. That is the design, not a beta caveat.
FAQ
Yes, natively. Google Meet is one of the apps Cedric knows deeply, with a built-in playbook: connect it once from the dashboard and ask in plain words, with no workflow to build and no fields to map. It sits alongside 3,200+ other connectable apps.
Yes. It joins as a named guest in the participant list, the same way a colleague would. Nothing about its presence is hidden, and inviting it is as deliberate as inviting anyone.
When addressed, yes: it can look something up or answer from what the workspace knows, out loud, in the call. Unaddressed, it listens and writes. It does not interject on its own.
In the channel or thread the meeting belongs to, as notes and action items with owners. For the wider story of Cedric in meetings, see the use-cases page.
Connect it for the whole workspace and everyone shares it, with one person authorising once. A connection you would rather not share, a personal inbox for instance, can stay personal to you.
Yes, and it starts that way: a fresh connection can look but not touch until you say otherwise. Even with write access granted, anything that changes or sends waits for an approval.
Every workspace starts with $50 in credits, free, no card. Each task consumes credits in proportion to the work involved. See pricing for the plans.
Stop losing the meeting after the meeting.
Install Cedric, invite it to the next call, and see the write-up arrive before the coffee refill.
100K credits ($50) on sign up. No card needed.