Avalo
Get Pro Free Download
Documentation

Calendar & conferencing integrations

← All documentation

Google Calendar sync and Google Meet links are free on every plan. Outlook sync, Zoom, external calendar blocking, and webhooks require Availo Pro.

Connect Availo to the tools you already use. Everything is configured under Availo → Integrations.

Google Calendar (Free)

Two-way sync with Google Calendar: stop double-bookings by reading your busy times, and add each new booking straight to your calendar.

One-time setup (administrator)

Because Google requires each site to use its own credentials, an administrator adds an OAuth client once:

  1. In the Google Cloud Console, create a project and enable the Google Calendar API.
  2. Configure the OAuth consent screen (External), add the Calendar scopes, and publish it to production.
  3. Create an OAuth client ID of type Web application, and add the redirect URI shown on the Availo Integrations page as an authorized redirect URI.
  4. Paste the Client ID and Client secret into Availo → Integrations → Google Calendar.

Publish the consent screen to production, not “testing” — testing-mode connections stop working after 7 days.

Connecting (each host)

Once credentials are in place, every host clicks Connect Google Calendar and signs in to their own Google account. Then choose:

  • Check these calendars for conflicts — busy times on the selected calendars remove matching slots from your availability.
  • Add new bookings to — the calendar new bookings are written to (optional).

Tokens are stored encrypted. Conflict data is cached briefly, and if Google is ever unreachable, your booking page keeps working — it just falls back to your Availo availability.

Google Meet (Free)

On any event type, tick Add a Google Meet link to each booking. When someone books, Availo creates the calendar event with a real Google Meet link and uses that link as the booking’s location — so it appears in the confirmation email and the calendar invite automatically.

Requires the host to have Google Calendar connected. If both Google Meet and Zoom are enabled on the same event, Zoom takes precedence.

Zoom (Pro)

Automatically create a Zoom meeting for every booking.

One-time setup (administrator)

  1. In the Zoom App Marketplace, build a Server-to-Server OAuth app.
  2. Add the meeting scopes (create/read) and activate the app.
  3. Copy the Account ID, Client ID, and Client Secret into Availo → Integrations → Zoom.

Per event type

Tick Create a Zoom meeting for each booking in the event’s Pro booking options. Every booking then gets its own Zoom meeting, and the join link becomes the booking location — flowing into the confirmation email and calendar invite. If Zoom is ever unreachable, the booking still succeeds with the event’s normal location. Cancelling or rescheduling a booking deletes the old Zoom meeting.

Block time from external calendars (Pro)

Don’t use Google Calendar? You can still avoid double-bookings by pasting iCal/ICS feed URLs — for example your Google Calendar’s “Secret address in iCal format,” an Outlook published calendar, or an Apple public calendar. Events in those calendars block matching booking slots.

Add one or more feed URLs under Availo → Integrations. Feeds refresh every few minutes, and a broken feed never breaks your booking page.

Your bookings as a calendar feed (Pro)

Availo also gives each host a private calendar feed of their own bookings. Subscribe to it from Google, Apple, or Outlook to see your Availo bookings inside your usual calendar app. The feed URL is a secret — treat it like a password — and you can regenerate it at any time.

Webhooks (Pro)

Push booking events to your own systems (Zapier, Make, a CRM, a custom endpoint). Administrators add webhook endpoints under Availo → Integrations → Webhooks.

  • Choose which events an endpoint receives: booking.created, booking.approved, booking.cancelled, booking.rescheduled.
  • Set an optional secret to sign requests.

Each delivery is an HTTP POST with a JSON body describing the booking. When a secret is set, the request includes a signature header so you can verify it came from your site:

X-Availo-Signature: sha256=<HMAC-SHA256 of the raw body, keyed with your secret>

Deliveries are sent in the background (a slow endpoint never delays a booking), and a log of recent deliveries is shown on the page. For the payload shape, see the Developer reference.

License

Enter your Availo Pro license key here to enable automatic plugin updates. Without a valid key the plugin keeps working, but you won’t receive updates through the WordPress updates screen.