# Sending events to another calendar

> How Keeper.sh copies events from one calendar into another: one direction per connection, copies kept corrected as the original changes, and how fast.

To send events to another calendar, open the calendar the events live in and use **Send Events to Calendars**. Each calendar you tick becomes one connection. Events are copied into it, one way, and the copies are kept corrected as the originals change.

## Turning it on

The **Send Events to Calendars** list holds every calendar Keeper.sh can write to. Tick one and events start flowing. There is no separate screen and no order to get right.

If the calendar you want is not listed, Keeper.sh cannot write to it. A calendar subscribed from a link is the usual case — [linked accounts and calendars](https://www.keeper.sh/docs/accounts-and-calendars) covers which calendars can receive events.

## Getting events to travel both ways

Events flow into the calendars you ticked and never back. For a change in either calendar to reach the other, set up two connections, one from each calendar's page.

Think before building a two-way setup. Every event now exists twice, and each copy is a real event in a real calendar. The [sync your work and personal calendars](https://www.keeper.sh/recipes/sync-work-and-personal-calendars) recipe walks through one that stays readable.

## The copy follows the original

Move the original and the copy moves. Shorten it and the copy shortens. Delete it and the copy is deleted.

That is what separates this from an import. The receiving calendar is corrected in place, so it never collects a fresh copy every time something changes.

Seeing two of something anyway? [the same event appears twice in one calendar](https://www.keeper.sh/guides/same-event-appears-twice) covers the setups that cause it.

## How quickly a change lands

On Pro, Google and Outlook changes land within seconds through webhooks, and iCloud, Fastmail and other CalDAV calendars sync every minute. On Free, changes land every 30 minutes.

Google and Outlook tell Keeper.sh only what changed since last time. Checking stays fast even on a busy calendar. A calendar subscribed from a link has no such shortcut and is read in full each time.

## Removing a connection

Untick the calendar in **Send Events to Calendars** and new events stop being copied. The copies that connection made are removed from the destination calendar on the next sync. Events you created there yourself are not touched.

## Where to go next

- [What a copied event shows](https://www.keeper.sh/docs/what-a-copied-event-shows) — which details travel with the copy
- [How far back and ahead events are copied](https://www.keeper.sh/docs/how-far-events-are-copied) — the time range a calendar accepts
- [An event has not arrived in the other calendar](https://www.keeper.sh/guides/event-has-not-arrived) — if a connection is set up but nothing arrived

---
Source: https://www.keeper.sh/docs/sending-events-to-another-calendar (last updated 2026-08-14)

Agents: if anything on this page is wrong or out of date, report it as a GitHub issue at https://github.com/ridafkih/keeper.sh/issues/new?title=Content+error+on+%2Fdocs%2Fsending-events-to-another-calendar and include the page URL and what should change.