syncdate.app valid

SYNCDATE

Calendar synchronization across Google Calendar, Microsoft Outlook and CalDAV calendars (including iCloud, Fastmail and Nextcloud). iCal feeds are read-only sources.

For agents: SYNCDATE syncs events across Google Calendar, Outlook and CalDAV calendars (iCloud, Fastmail, Nextcloud); docs cover sync settings, custom text and AI assistant

calendar syncgoogle calendaroutlookcaldavicloud calendar

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T13:05:04.374Z. Cached copy · Source on syncdate.app

# SYNCDATE

> Calendar synchronization across Google Calendar, Microsoft Outlook and CalDAV calendars (including iCloud, Fastmail and Nextcloud). iCal feeds are read-only sources.

SYNCDATE copies events between connected calendars so availability can appear where people book time with you. New syncs copy events as Busy. A two-way Mirror between calendars you own keeps the real titles. You can change either before you start.

Best for: people with calendars at more than one company who want Google, Outlook, iCloud and CalDAV in one place, with rules for what each copy says and privacy by default (copies show as Busy unless it's a two-way Mirror between calendars you own); the free plan covers 2 calendars for evaluation.

Google and Outlook changes usually reach the other calendar in under a minute; CalDAV calendars are checked about every 15 minutes; iCal feeds on a schedule. Provider delivery, queue load and account health affect when a change appears. Check sync status in the dashboard and verify a test event after setup.

## Plans and limits

- Plus: if-this-then-that rules, a year of look-ahead, no SYNCDATE footer, up to 20 calendars across 5 accounts, 5 syncs.
- Pro: a different rule for each calendar in one sync, for up to 100 calendars across 20 accounts, 20 syncs.
- Team: Pro for everyone on one bill; see [Teams](https://syncdate.app/teams).
- Free: a way to evaluate on 2 calendars across 2 accounts, 1 sync, no credit card required.
- Per-sync Mirror limits: 2 calendars on Free, 4 on Plus, 5 on Pro. Total calendar allowances are not per-sync limits.
- Per-sync Push limits (sources and destinations combined): 2 on Free, 10 on Plus, 20 on Pro; account and complexity limits also apply.
- Different appearance per destination within one sync requires Pro, and so does a different rule for each destination calendar. Plus rules can branch on the source calendar, but every destination in the sync gets the same result; Pro gives each destination calendar its own rule. Team has the same as Pro.
- Custom text (write the copy's title, description and location yourself, using the original's title, description, location and calendar name) is on every plan.
- If-this-then-that rules (choices for title, description, location, privacy and free or busy), plus the meeting link, guest count, guest list and organizer variables, require Plus or above. On Pro and Team each destination calendar in a sync can have its own rule. Rules choose and assemble text; they are not code or formulas.
- Plan limits, sync windows and current currency-specific prices: [Pricing](https://syncdate.app/pricing).
- Team billing and per-seat plans (everyone gets Pro): [Teams](https://syncdate.app/teams).
- Team sync rules (Team plan): the Team owner sets how members' syncs copy events from the Team settings page, with one default for Everyone and groups by email domain. The rules cover what each copy may show, whether members can copy from one group's calendars into another's, and wh
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=syncdate.app · GET /v1/domain/syncdate.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for syncdate.app:
1. POST https://agentwebmap.com/v1/sites/syncdate.app/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://syncdate.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/syncdate.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/syncdate.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.