CalendarPipe vs SYNCDATE: One-Way Rules or Mirror

Quick Answer: CalendarPipe is built around rules that copy events one way, from one calendar to another, and it lets you decide per event what passes. SYNCDATE is built around a sync that can hold several calendars and run two-way (Mirror) or one-way (Push). If you want a work calendar and a personal calendar to stay complete on both sides, or you feed several calendars into one, SYNCDATE does that in one sync. If you want to skip events by length or guest domain, add buffers around copies, or pay less, CalendarPipe is the better pick today.

CalendarPipe launched in April 2026 and sits in the same corner of the market as SYNCDATE: calendar sync where you decide what the copy looks like. This page compares the two on what each one does now. CalendarPipe's figures come from its own pricing and documentation pages, read on 12 October 2026. Where a page does not say, we say we could not confirm it, rather than guess.

What CalendarPipe is

CalendarPipe works in "pipes". A pipe is a rule between a source calendar and a target calendar, with a gate function in the middle that decides, event by event, whether the event passes and what the copy looks like. Its documentation draws it as "Source Calendar --> Gate Function --> Target Calendar".

You can write the gate function as TypeScript in a code editor, or build it from dropdowns in a visual builder that its documentation describes as needing "no coding". The visual builder offers conditions on title, description, location, organizer, duration, attendee count, hour, weekday, time of day, event status and your own RSVP, and copy changes such as title, description, location, visibility, free or busy, colour (Google only) and buffers before and after the event.

It connects to Google Calendar, Microsoft calendars (personal and work or school) and iCloud with read and write access, and reads ICS feed URLs one way. Its connector page does not list generic CalDAV servers, so we could not confirm whether a Fastmail or Nextcloud calendar can be connected.

What SYNCDATE is

SYNCDATE connects Google Calendar, Outlook and Microsoft 365, CalDAV calendars (iCloud, Fastmail, Nextcloud and other servers) and iCal feeds, which are one-way sources. A sync holds the calendars you pick and a direction. Push copies one way and never touches the source; Mirror goes both ways, so each calendar gets a copy of the other's events. Google and Outlook changes usually reach the other calendar in under a minute.

What a copy says is set on the sync screen under Custom text and rules: build the title, description or location from pieces of the original with an Insert variable control, and on Plus and up add if-this-then-that rules, such as "10 or more guests, show Busy". No programming is involved. The features page shows the variables and rules, and the use cases show them on real setups.

The main difference: Mirror versus one rule per direction

CalendarPipe's documentation describes each rule as reading from a source and writing to a target. It does not describe a mirror mode. To keep two calendars in step you create two rules, one each way, and its docs say this is safe because neither rule treats the other's copies as new events. The same docs say rules do not chain: a rule from A to B does not carry A's events on to C, so a third calendar needs its own rule.

In SYNCDATE the same job is one sync set to Mirror. Put your Google work calendar, your Outlook calendar and your iCloud calendar in it, and each shows the other two. On Plus a Mirror holds up to 4 calendars and on Pro up to 5. A Push can feed several client calendars into one calendar you actually look at, with up to 10 calendars on Plus and 20 on Pro. Three client calendars pushing into one working calendar is one sync with four calendars in it.

Two caveats from our own documentation. A sync has a single direction, so a setup where two calendars mirror and a third only receives is two syncs. And two separate syncs do not chain either: Mirror A-B plus Mirror B-C never shows A's events on C, so put all three in one Mirror.

One practical point on cost. CalendarPipe's Free plan allows 1 rule, so a two-way pair there is out of reach and needs Pro. SYNCDATE's Free plan allows 1 sync, and a Mirror of two calendars is that one sync.

How far ahead and how often

CalendarPipe's pricing page lists a 14-day sync window on Free and 90 days on Pro, which its FAQ says can be raised to 180. SYNCDATE syncs 30 days ahead on Free, 1 year on Plus and unlimited on Pro. If you plan holidays, term dates or a fixed-term contract a year out, that gap matters.

On timing, CalendarPipe lists a 15-minute sync interval on Free and 5 minutes on Pro. We found no faster path or manual trigger in the pages we read. SYNCDATE listens for changes from Google and Outlook, so those changes usually reach the other calendar in under a minute. CalDAV calendars are checked about every 15 minutes and iCal feeds on a schedule, so the speed gap is on Google and Outlook, not on every provider.

Rules and conditions: where CalendarPipe is ahead

CalendarPipe's gate functions can read an event's duration, weekday, hour, time of day, attendee count, attendee list, organizer, status, location and description, combine conditions with AND or OR, and block or pass the event. Its cookbook has 14 recipes, including blocking by attendee domain and by duration. It can also set buffers of 0 to 60 minutes around a copy, set a reminder, mark a copy as out of office and write a reason for each block to the sync log.

SYNCDATE's filters today cover all-day events, free events, titles that contain a word, your invitation response, one working-hours window and, on Google, event types. Its rules decide the text, privacy and free or busy of a copy, and a different rule for each calendar in one sync is available on Pro and Team. On Plus and up a rule can also look at event length, start time, weekday and the guest's email domain, to change what a copy says. Skipping an event by length or guest domain, and buffers, are not available in SYNCDATE. If your setup depends on them, CalendarPipe covers it and we do not.

The difference is about what a rule decides. SYNCDATE rules shape the copy using the original's guest count, guests, organizer and meeting link; CalendarPipe rules can also decide whether the event is copied at all, on far more properties.

Some limits on our side, so nothing surprises you. Meeting link is blank for CalDAV, iCloud and iCal feed events. Organizer is blank on Outlook unless you organise the event. A free or busy rule can only make a copy Busy. A title or location result over 255 characters is not written.

Do you need to write code?

Not for either, in practice. CalendarPipe's visual builder is a no-code route, and its docs also describe a plain-English generator that we did not read, so we cannot say how much it covers. Code mode asks for TypeScript, and in that mode hour and weekday are evaluated in UTC, so a local-time check needs a helper. If you like writing that, it is a strength. SYNCDATE has one place for it, on the sync screen, with variables and rules in plain wording and no code mode to switch to.

Pricing

CalendarPipe's pricing page, read on 12 October 2026:

Its Pro trial lasts 14 days and asks for a card up front; its Free plan asks for none.

SYNCDATE has Free, Plus, Pro and Team plans; our current prices and the caps are on the pricing page. Free needs no card. Plus and Pro start with a 7-day trial that asks for a card up front, and you can cancel inside the 7 days without being charged. Free covers 2 accounts, 1 sync and 2 calendars. Plus allows 5 accounts, 5 syncs and 20 calendars, and Pro and Team allow 20 accounts, 20 syncs and 100 calendars. Custom text is on every plan; if-this-then-that rules and the Meeting link, Guest count, Guests and Organizer variables start on Plus.

On price alone CalendarPipe is lower, and its paid plan has no cap on rules or connections. If budget decides it, that counts.

Which should you choose

Choose SYNCDATE if:

• You want two calendars to show each other's events, in both directions, as one sync you set up once
• You feed several calendars into one, or mirror three or four accounts together
• You plan further ahead than a few months
• You use Fastmail, Nextcloud or another CalDAV server
• You want to change what copies say without leaving the sync screen or learning a scripting language

Choose CalendarPipe if:

• You need to skip events by length or by the domain of a guest's email
• You want buffers before and after copied events, or a reminder time of your own choosing on the copy. SYNCDATE can keep the original event's reminders on the copy, but cannot set a time of its own
• You are comfortable writing TypeScript, or find its visual builder enough
• You want the lower price, with unlimited rules and connections on Pro
• You want a written reason for every blocked event in the sync log

Neither is a bad choice. If a two-way pair of calendars is your whole need, SYNCDATE gets you there with less to maintain. If your need is a precise filter, CalendarPipe is built for it.

Moving from CalendarPipe

Set up the SYNCDATE sync first and check that copies land as you expect. Then switch the CalendarPipe rules off and remove what they created through CalendarPipe, so each tool cleans up its own copies. Two tools writing to the same calendar will produce duplicates in the meantime.