Integrations / Calendars

Calendar integration for PodGlue

Connect Google Calendar, Outlook, or iCloud and PodGlue uses your existing events to block out busy times on your booking page, then writes each confirmed booking to your calendar and emails the guest an invite.

For booking only. PodGlue reads your busy times so guests can’t double-book you, and writes booking events back — it does not move, edit, or read the contents of your other calendar events.

Last updated

Connect your Calendars account

1

Open Booking setup in PodGlue

In PodGlue, open Settings → Booking and go to the calendar connections section. All three calendar providers connect from here — this is in Booking setup, not the Integrations tab.

2

Connect Google Calendar

Click Connect on Google Calendar. You are sent to Google’s official sign-in to authorize PodGlue, then returned to PodGlue with the connection saved. PodGlue stores an access and refresh token server-side so it can keep checking your availability.

3

Connect Outlook

Click Connect on Outlook. You are sent to Microsoft’s sign-in (login.microsoftonline.com) to authorize PodGlue for the Calendars.Read, Calendars.ReadWrite, User.Read and offline_access permissions. This works for both personal Outlook.com and work or school Office 365 accounts. You are returned to PodGlue with the connection saved.

4

Connect iCloud

For iCloud, generate an app-specific password at appleid.apple.com (Apple requires this for calendar/CalDAV access — it is separate from your Apple ID password and can be revoked on its own). Sign in with Apple in PodGlue and paste the app-specific password. PodGlue stores it server-side to reach iCloud over CalDAV.

What happens after you connect

Publish flow

A calendar connection feeds PodGlue’s guest booking in two directions. For availability, when a guest opens your booking page PodGlue reads the busy events from your connected calendar for the requested window — your primary Google Calendar via the Google Calendar API, or your iCloud calendars over CalDAV — and hides any slot that overlaps an existing event, so guests can’t double-book you. When a booking is confirmed, PodGlue writes the event into your connected calendar (Google via the Calendar API, Outlook via Microsoft Graph, iCloud via CalDAV), titles it with the booking type and the guest’s name, sets the duration from your booking-type config, adds the guest as an attendee, and emails them a calendar invite. You can connect more than one provider at once.

Media support

Calendars don’t carry podcast media — there’s nothing to publish here. What moves is scheduling data: PodGlue reads the start/end times of your existing events to compute free slots, and writes a single booking event per confirmed booking (title, description with the guest’s name and email, start and end time, the guest as an attendee, and a reminder). It does not sync the contents, attachments, or attendees of your other events, and it never creates anything on your calendar except booking events.

What it can do

Read your busy times so your booking page only offers genuinely free slots (Google via the Calendar API, iCloud via CalDAV)
Write each confirmed booking into your connected calendar — Google (Calendar API), Outlook (Microsoft Graph), or iCloud (CalDAV)
Add the guest as an attendee and email them a calendar invite for the booking
Set the event length from your booking-type config (e.g. a 30-minute discovery call or a 45-minute interview)
Connect more than one provider at the same time (e.g. Google for availability and Outlook for events)
Refresh expired Google and Outlook access tokens automatically using the stored refresh token, so the connection keeps working

What it won’t do

Connect iCloud with OAuth alone — Apple requires an app-specific password (generated at appleid.apple.com) for calendar access
Read or change the contents of your existing calendar events — PodGlue only reads their times for availability and writes its own booking events
Move, reschedule, or delete events you created yourself
Guarantee a connection lasts forever — if a token or app-specific password becomes invalid, PodGlue flags the calendar as needing reconnection rather than failing silently
Be managed from the Integrations tab — calendars are connected in Settings → Booking setup

Privacy & security

Google and Outlook connect through their official OAuth sign-in — PodGlue never sees or stores your Google or Microsoft password. iCloud uses an app-specific password you generate at appleid.apple.com, separate from your Apple ID password and revocable on its own.
All credentials — OAuth access and refresh tokens, and the iCloud app-specific password — are stored server-side only, never in your browser.
PodGlue reads only the busy times it needs to compute availability and writes only the booking events it creates; it does not read the contents of your other events or write anything else to your calendar.
Outlook requests Calendars.Read, Calendars.ReadWrite, User.Read and offline_access; Google requests calendar access plus your basic profile to label the connection.
Disconnecting from Settings → Booking setup removes the stored credentials and stops PodGlue using that calendar. For Google, PodGlue also revokes its token with Google. Outlook has no revoke endpoint, so its token simply expires; for iCloud you can additionally revoke the app-specific password at appleid.apple.com.

Data accessed

For availability, the start and end times of your existing calendar events in the window a guest is booking (Google via the Calendar API, iCloud via CalDAV) — not their contents, attendees, or attachments. For bookings, PodGlue writes one event per confirmed booking with the guest as an attendee. It also reads your basic account profile (e.g. your email/name) to label the connection. Google/Outlook OAuth tokens and the iCloud app-specific password are stored server-side.

Auth model

Per provider: Google Calendar uses Google OAuth (access + refresh tokens, server-side); Outlook uses Microsoft Azure AD OAuth 2.0 with the Calendars.Read, Calendars.ReadWrite, User.Read and offline_access scopes; iCloud uses Sign in with Apple plus an app-specific password (generated at appleid.apple.com) for CalDAV access. PodGlue never sees or stores your Google, Microsoft, or Apple ID password.

Disconnect

Open Settings → Booking setup, find the calendar, and disconnect. PodGlue removes the stored credentials and stops using that calendar. Google: PodGlue revokes its token with Google. Outlook: Microsoft exposes no revoke endpoint, so the token expires on its own. iCloud: revoke the app-specific password at appleid.apple.com if you also want to cut CalDAV access.

FAQ

Clear answers for searchers and AI assistants.

Which calendars can I connect to PodGlue?

Three: Google Calendar, Outlook (Microsoft 365 / Outlook.com), and iCloud. You connect them in Settings → Booking setup, and you can connect more than one at the same time. PodGlue uses them so guest bookings respect your real availability and land on your calendar.

How does each provider connect?

Google and Outlook use OAuth — you click Connect and sign in on Google’s or Microsoft’s own page, and PodGlue is authorized without ever seeing your password. iCloud is different: Apple requires an app-specific password for calendar access, so you generate one at appleid.apple.com and paste it into PodGlue, which uses it to reach iCloud over CalDAV.

Why does iCloud need an app-specific password instead of a normal login?

Apple does not allow third-party apps to reach iCloud Calendar with your regular Apple ID password. Instead you generate an app-specific password at appleid.apple.com for PodGlue. It only works for this connection, is stored server-side, and you can revoke it at appleid.apple.com at any time without changing your Apple ID password.

What does PodGlue actually sync — does it read all my events?

No. For availability, PodGlue reads only the start and end times of your existing events in the window a guest is trying to book, so it can grey out slots you’re already busy. It does not read the contents, attendees, or attachments of those events. The only thing it writes is a booking event when a booking is confirmed.

What happens on my calendar when a guest books me?

PodGlue creates a single event on your connected calendar — Google via the Calendar API, Outlook via Microsoft Graph, iCloud via CalDAV. The event is titled with the booking type and the guest’s name (e.g. “Podcast Interview: Jane Doe”), runs for the duration set in your booking-type config, includes the guest as an attendee, and sends them a calendar invite by email.

Can I connect more than one calendar at once?

Yes. You can connect any combination of Google, Outlook, and iCloud in Booking setup. PodGlue keeps each connection separately, so you might, for example, use one provider for availability and have booking events written to your main calendar.

What happens if my calendar connection expires?

For Google and Outlook, PodGlue automatically uses the stored refresh token to get a new access token, so the connection keeps working in the background. If a refresh fails — or an iCloud app-specific password stops working — PodGlue marks that calendar as needing re-authentication and asks you to reconnect, rather than silently dropping bookings.

How do I disconnect a calendar?

Open Settings → Booking setup, find the calendar, and disconnect it. PodGlue clears the stored tokens or app-specific password and stops using that calendar. For Google it also revokes its access with Google; Outlook’s token simply expires (Microsoft has no revoke endpoint); and for iCloud you can additionally revoke the app-specific password at appleid.apple.com.