CalendarPipe syncs Google, Outlook, and Apple calendars through programmable pipes that filter, transform, and route events. Build pipes visually, describe them in plain English with AI, or write TypeScript. Events flow as real invitations — no OAuth needed on the recipient side. AI agents get a REST API, CalDAV, and MCP server to spin up their own calendars and send invites.
We built CalendarPipe because my work calendar didn't reflect my family calendar. Every week, I had to manually update blocks in my work calendar to ensure availability for errands or taking care of kids. Existing sync tools mirror everything or some parameters but aren't programmable. In my case, events in my family calendar starting with "J:" need to block time on my work calendar - and nothing else should leak through.
Another problem: my company doesn't approve apps connecting via OAuth to calendars directly. So we built a smart workaround that manages calendar invitations via email, avoiding the need for security approval entirely.
The core concept is a pipe, a pure function that takes an event in and decides what comes out. Block it, pass it through, redact the title - the configurability is almost endless 🧑💻.
For AI agents 🤖: CalendarPipe ships a REST API and ready-to-use skills. Agents can spin up their own hosted calendar and deliver real email invitations to any inbox.
Would love your feedback - especially on the pipe concept and the agentic workflows. AMA!
oh yes, it's like we are living in the "future" while my cal still runs on conflicts without me ever noticing them
Calendar sync for agents is a sharp unlock — every time I try to let an agent book or reschedule, the conflict-resolution logic is the part that falls over. How do you handle it when a human moves an event an agent is watching? Congrats on launch 🚀
I’ve struggled with juggling multiple calendars, so this idea really clicks for me. I like that I can define rules instead of constantly fixing conflicts.
This is pretty clever! I've faced similar issues before and just went with Zapier or the native email fwd'ing/automation tools but I'd image CalendarPipe feels much more native? Curious how you landed on building this vs using an existing automation tool.
Well done @jukben btw, I'm going to give it a try!
Invitation-based delivery is a clever way around OAuth and “recipient doesn’t need an account,” but invites/ICS can be fragile across Outlook/Gmail/security gateways. What have been the hardest interoperability or deliverability issues to handle, and what guardrails/debugging have you built for users when an invite doesn’t render or RSVP correctly?
About CalendarPipe on Product Hunt
“Programmable calendar sync for humans and AI agents”
CalendarPipe launched on Product Hunt on April 17th, 2026 and earned 131 upvotes and 12 comments, placing #7 on the daily leaderboard. CalendarPipe syncs Google, Outlook, and Apple calendars through programmable pipes that filter, transform, and route events. Build pipes visually, describe them in plain English with AI, or write TypeScript. Events flow as real invitations — no OAuth needed on the recipient side. AI agents get a REST API, CalDAV, and MCP server to spin up their own calendars and send invites.
CalendarPipe was featured in Productivity (649.7k followers), Calendar (32k followers) and Vercel Day (5 followers) on Product Hunt. Together, these topics include over 130.4k products, making this a competitive space to launch in.
Who hunted CalendarPipe?
CalendarPipe was hunted by Jakub Beneš. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how CalendarPipe stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Jakub Beneš
Hey Product Hunt 👋
We built CalendarPipe because my work calendar didn't reflect my family calendar. Every week, I had to manually update blocks in my work calendar to ensure availability for errands or taking care of kids. Existing sync tools mirror everything or some parameters but aren't programmable. In my case, events in my family calendar starting with "J:" need to block time on my work calendar - and nothing else should leak through.
Another problem: my company doesn't approve apps connecting via OAuth to calendars directly. So we built a smart workaround that manages calendar invitations via email, avoiding the need for security approval entirely.
The core concept is a pipe, a pure function that takes an event in and decides what comes out. Block it, pass it through, redact the title - the configurability is almost endless 🧑💻.
For AI agents 🤖: CalendarPipe ships a REST API and ready-to-use skills. Agents can spin up their own hosted calendar and deliver real email invitations to any inbox.
Would love your feedback - especially on the pipe concept and the agentic workflows. AMA!