Calendar Sync
Google is the one calendar that goes both ways here. Saving pushes straight out and mails the invitations; the return trip only happens when somebody asks for it, and that asymmetry is the thing to know.
A slot booked, and the trip back
writing out- 1validated and storeddone
the local row is written first, so the booking exists whatever Google does next
- 2written to the accountdone
inside the same operation, against the primary calendar on it
- 3guests are emaileddone
by Google, because the write asks it to notify everyone
- 4the identifier comes home
what Google returns is put on the local row, so a later edit patches that same entry
- 250 per page, up to twenty
thirty days behind to a hundred and eighty ahead
- cancelled entries are asked for
deliberately, so the matching local row can be deleted rather than left greyed out
- a series arrives flat
occurrences are expanded before storage, and the rule rides along on the row as text
Product figures from the platform’s own defaults - not customer averages
How it works.
Out at once, back on request
Saving an event writes it to the connected account inside the same operation, and asks Google to email the guests. Reading changes made in Google runs when somebody presses the sync button, not on a timer.
The provider identifier comes home
What Google returns is written onto the local row, so a later edit patches that same entry instead of making a rival copy, and the return pull recognises it rather than duplicating it.
A cancellation is a deletion
Cancelled entries are deliberately asked for on the way in so the matching local row can be removed. A meeting called off elsewhere disappears here rather than sitting greyed out.
A repeating series arrives flat
Recurring entries are expanded into individual occurrences before storage, so a range query never has to interpret a rule. The rule itself rides along on the row as text.
Two moments in every message.
Every message passes through the same seven. Calendar Sync is the lit ones, 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- Provider
- Google Calendar, and only the primary calendar on that account
- Direction
- Writes leave immediately on save. Reads are pulled when requested and are not scheduled
- Window
- Thirty days behind to a hundred and eighty ahead, two hundred and fifty per page, twenty pages
- Invitations
- Sent by Google, because the write asks it to notify everyone
- Recurrence
- Series are expanded into occurrences; the first rule is carried on the row as a string
- Outlook Calendar
- Carried by the Microsoft connection instead, which brings the diary over Graph. Exchange Sync is the page for it
- Not the same as
- Exchange Sync, which pulls a Microsoft calendar into a store of its own that this screen does not read
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
11 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.
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 calendar sync on your own floor.
Thirty minutes, your numbers and your data. We will set calendar sync up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included