CalendarPipe

Congrats on the launch! This is genuinely clever - the idea of events flowing as real invitations without OAuth friction is a game-changer for adoption.Quick question: when an AI agent sends calendar invites through CalendarPipe, how do you handle the identity/verification side? Does the invite appear to come from the agent itself, or from a proxy account?

I've been hacking this together manually for 3 years, WHERE WAS THIS??

Nice! 🔥

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?

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!EDIT: Don't forget to use the promo code if you want to experiment with Pro features! 🙏