Connecting Google Calendar to your Electbase site
Connect your Google account and Electbase creates a calendar called Campaign Events in it. Every event you add on your site's Events page appears there; edit it and the entry changes, delete it and the entry goes. It is a one-way sync of your campaign's own events, and no supporter data is involved: RSVPs and attendees never reach Google. Available on Grassroots and above.
What syncs, and what doesn't
When you create or edit an event under Events, Electbase sends its title, description, location (place name and address), and start time to the Campaign Events calendar. Each entry is given a one-hour duration, because Electbase events have a start but no end; if you change the length in Google Calendar, the next edit you make to that event on your site sets it back to an hour. Deleting the event on your site removes the calendar entry.
Weekly and monthly recurring events sync as recurring entries, in your campaign's own time zone, so a 6 p.m. weekly canvass stays at 6 p.m. across the daylight-saving change.
What never syncs: RSVPs. The calendar entry has no attendees and sends no invitations. This is deliberate and structural, not a setting: the sync carries only your event's own details, so no supporter's name or email can reach Google through it.
Connecting it in Electbase
- From your dashboard, open Connections in the top navigation and find the Google Calendar card. Click Connect Google Calendar.
- Google asks you to sign in and to let Electbase create secondary calendars and manage events on them. That is the only permission requested; Electbase cannot see your other calendars. Approve it.
- Back on the card, the chip reads Connected, and a calendar named Campaign Events is already in your Google Calendar.
Changes reach the calendar within a few minutes.
Events you created before connecting are not copied across on their own. Edit one (even a trivial change) and it syncs. New events sync from the moment you connect.
If the calendar disappears
If the Campaign Events calendar is deleted in Google Calendar, the card turns yellow and says sync is paused. Nothing is lost: click Reconnect Google Calendar, Electbase creates a fresh calendar, and the held events deliver into it.
If Google revokes our access instead, the card reads that authentication failed, and Reconnect Google Calendar fixes that too.
Disconnecting
Disconnect Google Calendar destroys our stored sign-in and stops queued updates. The Campaign Events calendar and everything on it stay in your Google account.
All of Electbase's Google connections on your account (Sheets, Calendar, Search Console) ride a single Google authorization. Disconnecting Calendar revokes that authorization at Google only if no other Google connection on this campaign still uses it. If one does, the card says so and the authorization stays, and you can remove it yourself at myaccount.google.com/permissions when you are done with all of them.
Has this been tested against the real Google Calendar?
Yes. On 2026-09-26 the round trip ran on a live campaign: connecting created a new Campaign Events calendar, a one-time event created on the site appeared on it at the right local time with the right title and location, editing the event changed the same entry without duplicating it, and deleting the event removed it, each step read back from Google rather than from our own chip.
Two paths have not been exercised yet: a weekly or monthly event checked across a daylight-saving change, and disconnecting then confirming the revocation at Google. We say so rather than describe them as proven.
Quick checklist
- On your Connections page, click Connect Google Calendar and approve the one permission Google asks for.
- Open Google Calendar and find Campaign Events in your calendar list.
- Add or edit an event under Events on your dashboard and watch for it on the calendar.
- Remember that events made before you connected sync only once you edit them.