Connecting Google Calendar or Microsoft Calendar turns your meetings into work events Halyard can report on. Each teammate connects their own account. Halyard records that meetings happened, not what was said in them.
What you get: work events, not searchable knowledge. Calendar produces episodic calendar_event_scheduled records that you list and filter by author and time. It does not capture transcripts or make meeting content semantically searchable.
What it produces
Section titled “What it produces”Calendar events arrive as the work-event type:
calendar_event_scheduled
Each event carries the meeting’s details and attendees, stitched to Halyard users via external identity where their accounts are linked. That attendee stitching is what connects a meeting to the people who were in it.
Connect a calendar
Section titled “Connect a calendar”Calendar is a per-user connection — each teammate authorizes their own calendar:
- In the Halyard app, go to Settings → Integrations.
- Choose Google Calendar or Microsoft Calendar, then select Connect.
- Grant read access to events in your own calendar.
You can connect both providers. Halyard requests no calendar write access and never imports event descriptions, bodies, or attachments.
Backfill and sync
Section titled “Backfill and sync”On connect, Halyard backfills roughly the last 90 days and looks ahead about the next 30 days. It then checks for changes every 15 minutes. You can select Sync now on either integration card when you need an immediate refresh.
If a provider withdraws access, the card explains that you need to reconnect. Disconnecting removes only your imported events for that provider.
- Knowledge vs work events — why a calendar invite isn’t searchable knowledge.
- Connect your sources — the full source matrix.