Google Calendar, in both directions

Your board already knows what is due and when. This guide connects it to your Google Calendar so the two stop disagreeing: tasks with a deadline appear as events, and events you already keep in Google appear as tasks with a countdown.

It is a two-way integration, but not a free-for-all: nothing is pushed and nothing is imported until you choose it, workspace by workspace and calendar by calendar. Both directions run about once a minute, and "Sync now" makes either happen immediately.

1. Connect your calendar

Open Settings → Integrations and find Google Calendar.
Press Connect Google Calendar and grant access on Google's consent screen. You will be asked to let Taskr create and change calendar events, to see the list of your calendars so you can pick one, and — for the import direction — to read the events of the calendars you choose.
Taskr creates a calendar of its own, called Taskr, in your Google account and uses it by default. You can point the sync at any calendar you can write to instead, and you can delete Taskr's own calendar at any time by disconnecting.

You can disconnect whenever you like. Disconnecting removes the events Taskr created and the calendar Taskr created, and leaves everything you picked yourself alone.

2. Choose what goes out

Tick the workspaces whose tasks should reach your calendar. A task needs a date to be pushed: a task without one is just a note, and it stays one.

With a date and no time it becomes an all-day event.
With a date and a time it becomes a one-hour block at that time.
A completed task keeps its event, marked with a ✓ in the title — the calendar is a record of what was due, and an event that quietly vanishes looks like a bug.

Each workspace can be pointed at a different calendar, so work can go to your work calendar and home to your personal one. A workspace you untick stops being pushed, and its events are removed on the next pass — that is what unticking means, so it is worth knowing before you press Save.

3. Choose what comes in

Under Import from Google Calendar, pick the workspace an event from each calendar becomes a task in. The default is Don't import for every calendar, and only events with a date are imported.

A holiday, an out-of-office block and a working-location marker are not work you do, so they are ignored.
Your edits win over Google's when they are the more recent ones: an event you renamed becomes the task's title, a task you edited becomes the event, and deleting one side deletes the other.
An event that scrolls out of the twelve-month import window is not deleted — only an event you actually delete in Google, or a task you delete here, removes the pair.

4. Repeating events

A repeating event in Google becomes one recurring task with the same schedule — not one task per occurrence, and not a series that dies the first time you tick it off.

The event's repeat rule is kept exactly as it is in Google. "Every second Monday and Thursday", a rule with a count, a rule with an end date: whatever Google holds is what comes back to Google.
The task shows the next occurrence, with the same countdown as any other task, and moves to the following one when the occurrence passes or when you tick it off.
A rule Taskr cannot express on its board as a repeat chip (something like "the third Tuesday of the month") still arrives as a task and still keeps its exact rule in Google. What you lose is the repeat chip, not the schedule.
The schedule of a series that came from Google belongs to Google. Editing the date of that task here does not move the series — change the recurrence in Google.
The title follows whichever side edited it most recently: rename the event in Google and the task takes the new name, rename the task here and the event is renamed. Its date and repeat rule stay put either way.
Moving or deleting a single occurrence in Google does not touch the task: a series is paired as a whole. (A whole series you cancel in Google does remove its task, unless you edited the task after the cancellation.)
A series that ends is respected: "after 5 times" and "until 1 December" are turned into an end date on the task, so it stops repeating here at the same point it stops in Google.

Known limitation, not mirrored yet. Per-occurrence exceptions in Google — EXDATE (an occurrence you delete or skip on its own) and an occurrence you move or retitle without touching the series — do not reach the task. The series keeps its exact schedule in Google, and the task keeps its own day, so a single exception is the one place where the board and the calendar can disagree. The series as a whole is always in step; it is the individual exception that is not.

A series that starts here is the other way round: Taskr owns the rule. Set a repeat rule on a task and the event repeats with it; clear the repeat rule and the event stops repeating.

5. What the calendar in Taskr shows

The workspace calendar draws what Taskr knows and what your Google Calendar holds, so you can plan in one place instead of two:

every dated task and dated list of the workspace, and every note bound to a day — exactly as before;
the events of the calendars you chose to import into that workspace, drawn as read-only chips carrying Google's own colours. A chip shows its time (or all day), and clicking it shows the details and a link straight into Google Calendar. That click changes nothing in Taskr: the calendar here is a view, never an editor.
An event that already has a task is drawn once, from the task — including the events Taskr itself wrote into your Google Calendar, and every occurrence of a repeating event that came in as a single task. Without that, the same appointment would appear twice on the same day.

The calendar Taskr created for you is never read back: everything in it is a copy of your own tasks.

Holidays, out-of-office blocks, working-location markers and birthdays are left out of the calendar for the same reason the import leaves them out — one list for both places, so the calendar and the board never disagree about what an event even is. Task lists in Google Tasks are a separate layer in Google's own app and are not calendar events, so they do not appear here either.

Only the calendars you mapped for import into that workspace are read, and only for the period on screen — a month either side of it is fetched so the edges of the month grid are covered. Moving around the calendar reads nothing else and writes nothing anywhere; at most ten calendars are read for one period, and if a workspace has more, that is reported rather than quietly dropped.

If Google cannot be read, the calendar keeps showing your own items and says so quietly above the grid. An empty calendar and a calendar that could not be loaded are different things, and you should be able to tell them apart.

Two small limits worth knowing: an event spanning several days (a holiday week, a trip) appears on its first day, and moving a single occurrence of a repeating event inside Google shows up as its own chip rather than changing the series.

6. If something does not show up

Work down this list before assuming it is broken:

Is the connection there? Settings → Integrations shows the connected account. If it says Google refused the stored access, press Reconnect.
Which calendar? Taskr writes into its own Taskr calendar unless you chose another one — events were probably written into a calendar you do not have open.
Is the workspace ticked? Nothing is pushed or imported from an unticked workspace or an unselected calendar, and that produces no error at all. It is the most common answer. In the calendar, the same is true of what you see: only the calendars mapped for import into this workspace are drawn.
Does the task have a date? An undated task is never pushed, and an event without a usable start date is never imported.
Wait a minute, or press Sync now. A change reaches Google within one pass; "Sync now" skips the wait.
Read the last sync problem at the bottom of the card. It names what Google answered — a missing permission, a refused token, a calendar that is gone.

Where to go next

Create your first task with a deadline — the countdown the calendar pairs with
Install Taskr — the board and its countdowns on desktop and Android
Feature: Recurring tasks on your schedule

Create a free account and let your calendar and your task list say the same thing.

Google Calendar, in both directions

1. Connect your calendar

Open Settings → Integrations and find Google Calendar.
Press Connect Google Calendar and grant access on Google's consent screen. You will be asked to let Taskr create and change calendar events, to see the list of your calendars so you can pick one, and — for the import direction — to read the events of the calendars you choose.
Taskr creates a calendar of its own, called Taskr, in your Google account and uses it by default. You can point the sync at any calendar you can write to instead, and you can delete Taskr's own calendar at any time by disconnecting.

You can disconnect whenever you like. Disconnecting removes the events Taskr created and the calendar Taskr created, and leaves everything you picked yourself alone.

2. Choose what goes out

Tick the workspaces whose tasks should reach your calendar. A task needs a date to be pushed: a task without one is just a note, and it stays one.

With a date and no time it becomes an all-day event.
With a date and a time it becomes a one-hour block at that time.
A completed task keeps its event, marked with a ✓ in the title — the calendar is a record of what was due, and an event that quietly vanishes looks like a bug.

3. Choose what comes in

A holiday, an out-of-office block and a working-location marker are not work you do, so they are ignored.
Your edits win over Google's when they are the more recent ones: an event you renamed becomes the task's title, a task you edited becomes the event, and deleting one side deletes the other.
An event that scrolls out of the twelve-month import window is not deleted — only an event you actually delete in Google, or a task you delete here, removes the pair.

4. Repeating events

A repeating event in Google becomes one recurring task with the same schedule — not one task per occurrence, and not a series that dies the first time you tick it off.

The event's repeat rule is kept exactly as it is in Google. "Every second Monday and Thursday", a rule with a count, a rule with an end date: whatever Google holds is what comes back to Google.
The task shows the next occurrence, with the same countdown as any other task, and moves to the following one when the occurrence passes or when you tick it off.
A rule Taskr cannot express on its board as a repeat chip (something like "the third Tuesday of the month") still arrives as a task and still keeps its exact rule in Google. What you lose is the repeat chip, not the schedule.
The schedule of a series that came from Google belongs to Google. Editing the date of that task here does not move the series — change the recurrence in Google.
The title follows whichever side edited it most recently: rename the event in Google and the task takes the new name, rename the task here and the event is renamed. Its date and repeat rule stay put either way.
Moving or deleting a single occurrence in Google does not touch the task: a series is paired as a whole. (A whole series you cancel in Google does remove its task, unless you edited the task after the cancellation.)
A series that ends is respected: "after 5 times" and "until 1 December" are turned into an end date on the task, so it stops repeating here at the same point it stops in Google.

A series that starts here is the other way round: Taskr owns the rule. Set a repeat rule on a task and the event repeats with it; clear the repeat rule and the event stops repeating.

5. What the calendar in Taskr shows

The workspace calendar draws what Taskr knows and what your Google Calendar holds, so you can plan in one place instead of two:

every dated task and dated list of the workspace, and every note bound to a day — exactly as before;
the events of the calendars you chose to import into that workspace, drawn as read-only chips carrying Google's own colours. A chip shows its time (or all day), and clicking it shows the details and a link straight into Google Calendar. That click changes nothing in Taskr: the calendar here is a view, never an editor.
An event that already has a task is drawn once, from the task — including the events Taskr itself wrote into your Google Calendar, and every occurrence of a repeating event that came in as a single task. Without that, the same appointment would appear twice on the same day.

The calendar Taskr created for you is never read back: everything in it is a copy of your own tasks.

6. If something does not show up

Work down this list before assuming it is broken:

Is the connection there? Settings → Integrations shows the connected account. If it says Google refused the stored access, press Reconnect.
Which calendar? Taskr writes into its own Taskr calendar unless you chose another one — events were probably written into a calendar you do not have open.
Is the workspace ticked? Nothing is pushed or imported from an unticked workspace or an unselected calendar, and that produces no error at all. It is the most common answer. In the calendar, the same is true of what you see: only the calendars mapped for import into this workspace are drawn.
Does the task have a date? An undated task is never pushed, and an event without a usable start date is never imported.
Wait a minute, or press Sync now. A change reaches Google within one pass; "Sync now" skips the wait.
Read the last sync problem at the bottom of the card. It names what Google answered — a missing permission, a refused token, a calendar that is gone.

Where to go next

Create your first task with a deadline — the countdown the calendar pairs with
Install Taskr — the board and its countdowns on desktop and Android
Feature: Recurring tasks on your schedule

Create a free account and let your calendar and your task list say the same thing.