Gmail Sync
Google knocks the moment something changes, so mail is here without anybody pressing refresh. The knock is checked before it is believed, and what it starts is a catch-up from where you left off, not a full re-read.
A push landing on a Gmail mailbox
the cursor- messageAddeda reply from Dana Whitlowstored, and filed against the lead it matches
- labelRemovedINBOX taken off an older threadarchived. The label set that comes back is treated as complete, so the old filing is dropped
- labelAddedSTARRED added elsewherethe flag follows, because starring never moves anything
- messageDeleteda message removed in Gmailflagged deleted here rather than erased
Product figures from the platform’s own defaults - not customer averages
How it works.
Where it starts from is what we wrote down, not what the knock says
A notification only carries the newest change number at the moment it fired. Starting there would skip everything since the last one, so the catch-up begins from the number we last wrote down and pages until Google stops offering more. The new mark comes from what Google answered with, not from the knock.
Moving a message counts as changing it
Archiving neither adds a message nor removes one; it only takes a label away. Label additions and removals are followed as well, and the label set that comes back is treated as complete, so a filing left over from the old position is dropped.
The knock must prove where it came from
It is accepted on a shared secret compared without leaking timing, or on a Google-signed token checked against Google's published keys. With neither configured the endpoint turns everything away.
The five-minute sweep gets out of the way
The sweep looks for a live watch first and skips any account that has one. The trade is that the watch covers the inbox alone, so a change somewhere else waits for whichever inbox event wakes the next catch-up.
Two moments in every message.
Every message passes through the same seven. Gmail 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.
8 facts- Consent
- A single scope, gmail.modify, which already covers reading, sending, labels and the watch itself
- Push
- A watch on the inbox label alone, feeding a Pub/Sub topic, seven days long, renewed by a nightly pass. Something that never touches the inbox raises no notification
- Incremental
- Change history from a saved cursor, fifty pages of it in one run
- Cursor too old
- Google answers with a not-found and the run falls back to catching up the last three days
- First sync
- Ninety days, fetched as four separate label queries, with progress written down every two hundred messages
- Deleting
- A message removed in Gmail is flagged deleted here rather than being erased
- Attachments
- Twenty-five megabytes each, twenty-five per message, and anything past either is skipped with a log line
- Revoked consent
- The connection is switched off and further attempts stop until somebody reconnects it
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 mailbox connections, tracking, calendar and meetings.
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change comes back when you sync.
A Microsoft mailbox brings its diary and address book with it, and whether it sits in Microsoft 365 or on a server in your building is worked out for you.
The connection for a mailbox nobody hosts for you. We sign in for real before saving the hosts and ports, so a typo is caught while you are still at the form.
Templates with merge variables, organized into groups and granted per team, so the answer your best rep writes becomes the answer everybody sends.
Regulated copy stays with the people allowed to send it. Filing a template into a group is what shares it, so there is no second step for anybody to forget.
What does not count is the useful part: a rep opening their own message, a crawler, the same person twice in five minutes. A figure a supervisor can act on.
Park a thread and it comes back at the hour you named, unread, so nobody walks past it. Hold a send and it leaves at the hour you named, once, never twice.
Nobody retypes their sign-off. It is held once per mailbox and added on the way out, so mail from the platform arrives looking like mail from a person.
A meeting agreed on a call is never lost because somebody else's service was slow. The booking is saved here first, then the room and the calendar entry.
Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes too, with nobody chasing it.
The join link is made by the calendar itself, on the same save that books the meeting, so nobody hunts for it later. One Google account is the whole setup.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
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 gmail sync on your own floor.
Thirty minutes, your numbers and your data. We will set gmail sync up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included