<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Integrations on BunnyCal Blog</title><link>https://bunnycal.io/blog/tags/integrations/</link><description>Recent content in Integrations on BunnyCal Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 16:03:00 +0530</lastBuildDate><atom:link href="https://bunnycal.io/blog/tags/integrations/index.xml" rel="self" type="application/rss+xml"/><item><title>Multiple calendars, one source of availability</title><link>https://bunnycal.io/blog/multiple-calendars-one-availability/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://bunnycal.io/blog/multiple-calendars-one-availability/</guid><description>&lt;p&gt;Most people don&amp;rsquo;t have &lt;em&gt;a&lt;/em&gt; calendar. They have a work Google account, a personal
one, maybe an Outlook calendar from a client engagement — and meetings booked
against any of them are equally real when someone asks if you&amp;rsquo;re free at two.&lt;/p&gt;
&lt;h2 id="read-from-everything-write-to-one"&gt;Read from everything, write to one&lt;/h2&gt;
&lt;p&gt;BunnyCal separates the two operations, because they want opposite defaults.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Conflict checking should be greedy.&lt;/strong&gt; Every connected calendar you mark as a
conflict source is queried when computing availability. A dentist appointment on
your personal calendar blocks a work booking, and nobody outside sees why — the
slot is simply gone.&lt;/p&gt;</description></item></channel></rss>