Calendar Sync | SiLobbyist

Step 1 · Connections

Where should events land?

Honest status: manual-export mode is live — direct sync is pending

Direct Google/Outlook sync needs OAuth app verification, which is on Johnny's go-live task list. Until then, this page works in manual-export mode: it builds a .ics file you import into Google Calendar, Outlook, or Apple Calendar in one click. SiLobbyist never stores OAuth tokens in localStorage — when the connection goes live, refresh tokens will live server-side only, never in your browser.

📅 Google Calendar

Not connected

OAuth via the Google Calendar API. Requires app verification — pending.

📧 Outlook / Exchange

Not connected

OAuth via Microsoft Graph. Requires app registration — pending.

📥 Manual export

Working now

Import into Google, Outlook, or Apple Calendar. Same events, same travel blocks.

Step 2 · Event sources

What syncs

Toggle each source. SiLobbyist only pushes what you enable — nothing is read back into the site.

FPPC filing deadlines
Quarterly lobbyist reports (Forms 615/625/630/635/635-C) from data/compliance.json. Deadlines roll to the next business day on weekends/holidays. Legislative calendar
Session deadlines, recesses, and floor sessions from data/legislative-calendar.json. Floor times are the typical pattern — exact times are announced in each house's Daily File. Tracked-bill hearings & floors
Upcoming hearings that match bills on your watchlist. No tracked bills → nothing to sync. CRM fundraisers
Future fundraiser entries from your private CRM (silobbyist_crm_v1, this browser only).

Step 3 · Travel time

Block the drive, not just the meeting

Events with a location get travel blocks before and after. Cap-to-Cal-Access runs on Capitol time — your calendar should know that.

Minutes before event

Minutes after event

Default origin

All-day events (filing deadlines) don't get travel blocks — there's no driving to a deadline. In manual-export mode the blocks are separate .ics entries; with direct sync they'll be native calendar blocks.

Conflict rules

Who wins when both sides change

Event type	Winner on conflict	Why
FPPC filing deadlines	SiLobbyist wins	Dates are authoritative under the Political Reform Act — your calendar is a reminder, not the source of truth.
Session deadlines, hearings, floor sessions	SiLobbyist wins	Same principle: the official calendar outranks a manually edited copy. Sync refreshes them from the source.
Fundraisers (from your CRM)	Your calendar wins	SiLobbyist never overwrites an event you edited or moved — it only re-syncs fundraiser entries you changed inside the CRM.
Your personal events	Your calendar wins	Sync never touches events it didn't create. It can't — it only writes events tagged `silobbyist-*`.

Duplicate-proofing: every synced event carries a stable ID (silobbyist-{source}-{key}), so re-syncs update instead of duplicating. Delete a SiLobbyist event in your calendar and the next sync recreates it — that's "SiLobbyist wins" for deadline events, by design.

Upcoming events

What would sync next

Loading…

Ask Goldie about a deadline →

Sync log

What changed, when

Deadline dates are pulled from curated site data (data/compliance.json, data/legislative-calendar.json) — verify any filing against fppc.ca.gov and the house Daily Files before you rely on it. SiLobbyist never transmits your data anywhere; manual export hands you a file, nothing uploads. Tokens, when OAuth goes live, are server-side only — never localStorage.