Gmail Sync
Google knocks when something changes and the knock is checked before it is believed. What it triggers is a replay of your own change log from where you last stopped, not a re-read of the mailbox.
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.
The stored cursor decides, not the knock
A notification carries the newest change number at the moment it fired. Starting there would skip everything since the previous one, so the replay begins from the number we last wrote down and simply pages until Google stops offering more. The new cursor 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 therefore 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.
Polling stands down while push is up
The five-minute sweep looks for a live subscription 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 replay.
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 sync providers, tracking, calendar and meetings.
Google Calendar writes out the moment you save and mails the invitations, and reads back on demand, so a meeting booked on a call is there before it ends.
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.
Book from the conversation, with the invitation, the joining link and the record all created together instead of in three separate tabs afterwards.
Connect Zoom and a booking creates, moves and cancels the meeting for you, with the joining link and passcode riding inside the calendar invitation.
Pick Google Meet on a booking and the calendar write mints the link with the invitation, so everyone on the account gets it rather than finding it in a note.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
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