Connecting your calendar
A calendar connection is a read-only link between Verinode and your Microsoft 365 or Google Calendar. Once connected, Verinode reads your meeting times, titles, and attendee counts, nothing else, s…
On this page
What it is
A calendar connection is a read-only link between Verinode and your Microsoft 365 or Google Calendar. Once connected, Verinode reads your meeting times, titles, and attendee counts, nothing else, so it can build a picture of which jobs had a call or a site visit and when. It never reads meeting notes, bodies, or attachments, and it never creates, moves, or deletes anything on your calendar.
This is one of six ways to connect a tool on the Connect page. The other five are QuickBooks Online (your books), Microsoft 365 and Gmail (your business mail), and the Verinode Notetaker (meetings on Zoom, Google Meet, Teams, or Webex). Calendar sits alongside those as its own wizard because a calendar needs no folder or label scoping, a mailbox does.
Where to find it
Open Connect from the sidebar, under My Data (/connect). The page opens on a row of five channel tiles: Email forwarding, Integrations, Upload, Photo, and Voice. Click Integrations to open the setup slider, which reads:
Connect your tools. Verinode turns the data already sitting in your accounting and inbox into benchmarks and process insights. A direct connection means you stop forwarding and exporting. You decide exactly what we can read.
Above the tiles sits a trust strip with three pills: Read-only access, You choose what we read, Encrypted at rest. Below it is a grid of provider tiles. Two of them are calendars:
- Microsoft 365 Calendar (tagline: "Outlook meetings")
- Google Calendar (tagline: "Google Workspace meetings")
Tiles reorder automatically: connected tiles float to the top, then connectable ones, then ones still marked "Coming soon." Click either calendar tile to open its wizard.
What each tile shows
Every provider tile, calendar included, shows the provider's logo, its name, a one-line tagline, and a call-to-action in the bottom corner:
- Manage (green) once a connection is live, with a green Connected pill in the top corner of the tile.
- Connect (copper) once the provider is available but you haven't linked it yet.
- Coming soon (gray, disabled) if the provider isn't turned on yet in your environment.
Clicking a tile in any of these three states opens the same wizard; what you see inside it changes based on whether you're already connected.
Inside the calendar wizard
The wizard opens with the provider logo, name, and tagline at the top, and a All integrations link to go back to the grid. Below that:
A direct connection reads your meeting times and titles so Verinode can tell which jobs had a call or site visit this week. It is strictly read-only. We read only meeting metadata, never the meeting notes, body, or attachments, and we never add, move, or change anything on your calendar.
Then a boxed section, "What we ask for, and what we never do":
Read-only access to your Outlook Calendar [or Google Calendar]. Meeting titles are encrypted at rest. We never request permission to create or change events, and your data is never sold to carriers. Disconnect in one click any time, which revokes our access immediately.
with a link to Verinode's Data Use Policy for the full detail on what's read, how long it's kept, and how to revoke access.
Unlike the Microsoft 365 and Gmail mailbox wizards, there is no folder or label to type in and no consent checkbox to tick here. A calendar connection has nothing to scope, there's only one calendar per connected account, so the wizard goes straight to a single Connect button once the provider is available.
Note
Google Calendar and Gmail are gated by separate approval processes with Google. If Google Calendar shows "Coming soon" in your environment while Microsoft 365 Calendar is live, that's expected, the two providers roll out on independent timelines.
Connecting a calendar
- 1From Connect in the sidebar, open the Integrations tile.
- 2Click Microsoft 365 Calendar or Google Calendar.
- 3Read the "What we ask for, and what we never do" box. This is the same access you're granting: read-only, metadata only, revocable in one click.
- 4Click Connect Microsoft 365 Calendar (or Connect Google Calendar). A popup window opens to Microsoft's or Google's own sign-in and consent screen, not a Verinode page, since the permission grant happens with the provider directly.
- 5Sign in and approve the read-only calendar permission. Microsoft's screen names it as calendar read access with offline access (so Verinode can keep syncing without asking you to sign in again); Google's names it as read-only access to your calendars.
- 6The popup closes and the tile flips to Connected. A message appears at the top of the page: "Calendar connected. Your meetings will sync shortly."
Once connected, the tile shows a green Connected badge, the line "Read-only sync is live," and, underneath, "Reading meeting metadata from" the email address of the calendar you connected. There's a Disconnect button beside it.
What Verinode actually reads
For every meeting in the sync window, Verinode reads four things and nothing more:
- Title, encrypted at rest before storage, since a meeting title often names a homeowner, a claim, or a carrier.
- Start and end time.
- Attendee count, how many people were on the invite, not who they are individually.
- Internal or external, a best-effort read on whether every attendee shares your company's email domain. When Verinode can tell, it uses this to separate an internal team meeting from a client-facing or carrier-facing one. When there aren't enough attendees to tell, or the domains don't resolve cleanly, this is left blank rather than guessed.
Verinode syncs meetings in a rolling window centered on today, roughly two months back and two months ahead, and it keeps polling in the background afterward. There's nothing to trigger manually once you're connected.
Note
For the technically curious: Microsoft grants the delegated Calendars.Read scope with offline access; Google grants calendar.readonly. Neither includes any permission to write, and Verinode never requests one.
This is early groundwork, not a finished dashboard. There isn't yet a calendar view inside Verinode listing every synced meeting; the metadata flows in so that, as the picture matures, Verinode can connect a call or a site visit to the job it belongs to and factor that into the job's touchpoint history, alongside your margin and client and carrier data. If you don't see that reflected in a decision or a job page yet, that's expected while this connector is early, not a sign the connection isn't working.
Disconnecting
Click Disconnect on a connected calendar tile. Verinode asks you to confirm: "Disconnect this calendar? Verinode will stop reading it." Confirming immediately revokes Verinode's access with the provider and stops the sync. The tile shows "Calendar disconnected." at the top of the page, and the tile itself drops back to a Connect state so you (or anyone else) can reconnect it, to the same account or a different one, at any time.
Messages you might see
After the popup closes, or if you're redirected back to Connect from the provider's consent screen, one of these appears at the top of the page:
| Message | What happened | |---|---| | "Calendar connected. Your meetings will sync shortly." | Success. The sync engine will pick up your meetings on its next pass. | | "Connection canceled. No access was granted." | You closed the popup or declined on Microsoft's or Google's screen. Nothing was connected. | | "Something went wrong connecting your calendar. Please try again." | The provider or Verinode hit an error mid-connect. Retry the Connect button. | | "Calendar connections are not available yet." | This provider isn't turned on in your environment yet. |
If a tile is still on Coming soon, its wizard shows a disabled Connect button with the note: "Coming soon. Notetaker and meeting links handle this today." Until a calendar provider is live for you, the Verinode Notetaker joining a call, or a meeting link you paste in, are the ways a meeting still turns into a job update.
Best-practice example
Say your team runs most client calls and site-visit walkthroughs off Outlook. Connect Microsoft 365 Calendar once, from your own login, and every meeting on your calendar over the following two months of history and two months ahead starts flowing in as metadata, no forwarding, no manual entry. If a teammate also fields calls from their own calendar, they connect separately from their own account. Neither of you needs to touch it again; disconnecting is the only manual step, and it takes effect immediately.
Related help articles
- Connecting your data: the full picture of every channel on the Connect page, not just calendar.
- Forwarding documents: the email-forwarding channel, for carrier, TPA, and vendor mail.
- Clients and carriers: where job and client touchpoints, including calls and site visits, eventually surface.
- Understanding your margin: how connected data, including meeting activity, feeds the picture of a job's health.
- The decision workspace: where Verinode turns data like this into a recommendation you act on, never a decision it makes for you.
Data sources
- 1.Microsoft 365 Calendar (Outlook) via delegated, read-only Graph API access. Microsoft 365.
- 2.Google Calendar via read-only Calendar API access. Google Workspace.