Google Calendar & Tasks

One connection, two syncs: your events can appear in Google Calendar, and your tasks in Google Tasks.

Connecting

1. Go to Integrations and find the Google Calendar & Tasks card.

2. Connect Google — you’re sent to Google to authorise.

3. Approve access to your calendar and your tasks. It’s one connection covering both; you can’t take one without the other.

4. You come back to karani.co/account/services/google, which is where everything below happens.

Where things sync to

Karani stays out of your primary calendar. On the first sync it creates, in your Google account:

• a calendar called Karani
• a task list called Karani

Everything Karani pushes goes there, and those two are the only places it reads from.

Only the Karani calendar comes back

An event sitting on your primary Google calendar will never appear in Karani, however much it looks like a fundraising event. Move it into the Karani calendar — or create it there — if you want Karani to pick it up.

Which direction runs on its own

Direction	When it happens
Google → Karani	On its own. Once a night, and within moments of a calendar change if you turn on webhooks
Karani → Google	When you push. Use Push All Karani Events or Push All Karani Tasks

Karani-side edits don't travel by themselves

Renaming an event or changing a task’s due date in Karani doesn’t reach Google on its own. Push again to send the new version. Google’s side is the one that flows automatically.

The sync buttons

The integration page has the same three buttons for events and for tasks.

Button	What it does
Pull Events / Pull Tasks from Google	Reads the Karani calendar or task list and brings everything in it into Karani
Push All Karani Events / Tasks	Sends every Karani event or task up to Google
Full Event Sync / Full Task Sync	Reads what’s changed in Google, then retries anything still pending or previously failed

All four are queued rather than run on the spot — the page comes straight back and the work happens in the background. Watch Recent Sync Activity at the bottom of the page to see it land.

What syncs on an event

Karani	Google Calendar
Name	Title
Description	Description
Start and end date, with timezone	Start and end
Venue name and address	Location
Virtual event URL	A Google Meet link, requested on the event
Status — published, draft, cancelled	Confirmed, tentative, cancelled

Coming the other way, a Google event becomes a Karani event carrying its name, description, dates, location (as the venue name) and status. Nothing else exists in Google to bring over, so a pulled event arrives bare — no tickets, goal, or registration. Fill those in on the event itself; see Creating an event.

Two details worth knowing: an all-day Google event arrives running 00:00 to 23:59, and an event Google gives no timezone for is stored as America/New_York.

What syncs on a task

Karani	Google Tasks
Title	Title
Note	Notes
Due date	Due
Completed, and when	Status and completion date
Repeat schedule	A recurrence rule, where Google supports the pattern

What doesn’t cross: the contact the task is attached to, and the task type. Google Tasks has nowhere to put either.

If you sync, complete in Karani

Ticking a Karani task off logs an interaction, and that interaction is what makes Out of Touch Donors and Unthanked Donors work. A task completed in Google comes back as completed, but without the contact it was never carrying, there’s no interaction to log against anyone.

Use Google to see your tasks; tick them off in Karani.

Sync mode

Settings → Default Sync Mode for New Items:

Mode
Off	New items stay out of Google
Manual	New items sync when you use the buttons
Auto	New items sync on their own

It applies to items created after you save it. Existing events and tasks keep whatever mode they already have.

Off is the one that bites

With the default set to Off, the push buttons quietly do nothing for anything new — no error, just no event in Google. Manual and Auto both allow pushes and both get swept up by the nightly sync.

Real-time updates

Settings → Enable Real-time Webhooks. With it off, changes made in Google wait for the nightly sync. With it on, Google tells Karani as the Karani calendar changes and the sync runs then.

This covers the calendar only — Google Tasks doesn’t offer notifications, so task lists are re-read in full on each sync either way.

The subscription Google issues expires after a week; Karani renews it daily and shows Webhook Status and its expiry on the settings page.

Checking on it

Where	What it shows
The integration page	Your 20 most recently synced events and tasks, each with a Synced, Pending, or Error badge
Recent Sync Activity	The last 20 sync actions, with counts of what was created, updated, deleted, and skipped
Settings → Sync History	The last 50, with the failure message and a link to the event or task involved

Connection Information on the settings page has the rest: when you connected, your Google user ID, the ID Karani holds for the calendar or list it’s syncing with, and when the access token expires — which Karani refreshes on its own.

Deleting things

What you do	What happens
Delete an event from the Karani calendar in Google	The Karani event stays put, unlinked. It stops syncing
Delete the whole Karani calendar in Google	Karani builds a new one on the next sync, and every event pushes up again as new
Delete an event or task in Karani	The Google copy stays until you remove it there

Alongside Microsoft To Do

You can run this and Microsoft To Do at once — neither knows about the other, and both treat Karani as the middle. A task created in Google’s Karani list arrives in Karani on the next sync, and from there it can go on to Microsoft. Nothing breaks; you just have two copies of your task list to keep an eye on.

Sharing with a team

A team leader’s Google connection can be published to the team, so members don’t each connect their own — see Shared integrations.

Disconnecting

Disconnect revokes Karani’s access to your Google account. Nothing is deleted: the Karani calendar and task list stay in Google with everything in them, and your Karani events and tasks stay where they are.

Reconnecting starts the sync state fresh. Karani forgets which calendar and list it was using and re-reads both from scratch on the next sync; anything already linked keeps its link rather than duplicating.