Google Meet
There is no meeting API being called here. The link is asked for as part of writing the calendar entry, which is why it needs a connected Google account and why it appears the moment the entry syncs.
The request that mints the link
creation field attachedPOST /calendars/primary/events?conferenceDataVersion=1Product figures from the platform’s own defaults - not customer averages
How it works.
The calendar mints it, not a meeting service
A creation request naming the Google conferencing type rides along with the entry, and the address comes back attached to it. There is no second call, and nothing separate that could later drift out of step.
Asked for once and only once
The request is attached only when the booking wants Google conferencing and carries no address yet. That test is what protects an existing room, not the fact of editing: the same builder runs on the update path, so editing an event that wants Meet and has no link does mint one.
A fresh request identifier each time
Every creation carries a new random identifier. Google uses that value to recognise a replay, and minting a fresh one each time means a genuine retry is not recognised as one. What actually stops a second room is the check above it.
Removing the entry removes the link
Because the room belongs to the calendar entry, withdrawing the entry takes it away. Nothing has to be cancelled separately and nothing is left running.
One moment in every message.
Every message passes through the same seven. Google Meet is the lit one, and everything either side of it is a different page in this category.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
who may use what, and see what
The specifics.
7 facts- Mechanism
- A conferencing creation request carried inside the calendar write, at conference data version one
- Requires
- A connected Google Calendar account and nothing beyond it. The room comes out of the same consent the diary does, so there is no second permission to grant and no second integration to keep alive
- When it appears
- As soon as the entry reaches Google, not at the moment you press save
- On edit
- A request is sent only where there is no link to lose. An existing room survives a reschedule because the address is already stored, not because updates are exempt
- Reading it back
- The pulled entry is recognised by its Google conferencing address or its video entry point and labelled accordingly
- Cancelling
- Handled by removing the calendar entry. There is no independent cancel
- Not the same as
- Zoom, which is a separate object with its own lifecycle that this product creates, amends and withdraws
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
12 capabilitiesWebmail, four sync providers, tracking, calendar and meetings.
A full mail client inside the CRM, with snooze, send later, eight system folders and a reading sandbox that never runs a single thing the sender wrote.
Connect Gmail on one scope and mail arrives by push rather than polling, filed against the lead holding the address, with nobody having to forward anything.
Outlook and Microsoft 365 sync through Graph with delta queries and subscriptions, so large mailboxes stay current without re-reading themselves.
A Microsoft mailbox brings its calendar and address book over Graph, on subscriptions that renew themselves, with a ten-minute pass running underneath.
Any mailbox that speaks IMAP and SMTP connects with a form and a live login test, so a provider nobody built an integration for is still a real inbox here.
Templates with merge variables, organised into groups and permissioned per team, so the answer your best rep writes becomes the answer everybody sends.
Grant a whole template folder to particular roles and teams, so regulated copy stays with the people allowed to send it. Filing is the act of sharing here.
Opens and clicks recorded against the record, with signed link identifiers so the tracking endpoint never trusts a parameter it was handed.
Put a thread out of sight until it matters and schedule a send for the morning, with the parked thread coming back unread so you cannot walk past it.
One signature per connected mailbox, added by the send path to new messages and forwards, so mail from the platform arrives looking like mail from a person.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Email & Calendar
See google meet on your own floor.
Thirty minutes, your numbers and your data. We will set google meet up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included