Why Combine All Three
Meetario, Google Calendar, and Slack each solve one piece of the scheduling puzzle on their own. Meetario handles the booking page and availability logic. Google Calendar is where your actual commitments live. Slack is where your team's attention already is. Connect all three together and you get a workflow where availability is always accurate, every booking lands on your calendar automatically, and you find out about it within seconds — without touching any of the three tools manually.
How the Three-Way Workflow Works
Here is the flow once everything is connected: a guest visits your Meetario booking page and only sees time slots that are actually free, because Meetario checks your Google Calendar for existing events in real time before displaying availability. When they book, Meetario creates the appointment, pushes a new event to your Google Calendar automatically, and posts a notification to your connected Slack channel — all within moments of the guest clicking confirm.
None of these steps require you to do anything manually. The only setup work happens once, when you connect each integration.
Step 1: Connect Google Calendar
Go to Account → Integrations → Google Calendar → Connect and authorize Meetario to access your calendar. This does two things: it lets Meetario read your existing events so it can hide conflicting time slots from your booking page, and it lets Meetario write new events whenever someone books, so your calendar always reflects your real schedule. For the full walkthrough, see our guide on connecting Google Calendar.
Step 2: Connect Slack
Next, go to Account → Integrations → Slack → Connect and authorize your workspace. Slack will ask you to choose a destination channel during its own authorization screen — pick the channel where you want booking alerts to appear. Our guide on setting up Slack booking notifications covers this step in detail if you want the full picture, including what each notification type looks like.
Step 3: Configure Your Event Type
With both integrations connected, open the event type you want this workflow to apply to and review its availability settings:
- Buffer time — Add a few minutes before or after each booking so back-to-back meetings synced from your calendar do not run into each other.
- Minimum notice — Prevent guests from booking a slot minutes before it starts, giving you time to see the Slack alert and prepare.
- Location type — If you want a Google Meet link generated automatically, set the location to Google Meet, which relies on the same calendar connection.
Step 4: Test the Full Flow
Before trusting this with real clients, test it end to end. Block off a slot directly in Google Calendar and confirm it disappears from your Meetario booking page — this proves the calendar sync is reading correctly. Then book a test slot as a guest using a secondary email address and confirm three things happen: the event appears on your Google Calendar, a confirmation email goes out, and a message posts to your Slack channel. If any one of these three does not happen, revisit that specific integration's connection status under Account → Integrations rather than assuming the whole workflow is broken.
What Happens End-to-End When Someone Books
- Guest opens your Meetario booking page and sees only genuinely open slots, filtered against your Google Calendar.
- Guest picks a time, fills out the booking form, and confirms.
- Meetario creates the event and, if configured, generates a Google Meet link.
- The event is written to your Google Calendar automatically.
- A confirmation email goes to both you and the guest.
- A Slack notification posts to your connected channel with the event type, time, guest name, and a join button.
- Shortly before the meeting, both a reminder email and a Slack reminder notification go out.
Tips for Keeping It Reliable
- Keep your timezone accurate — Set your timezone correctly in Meetario's account settings so calendar sync and Slack timestamps line up with your actual local time.
- Reconnect after long inactivity — OAuth tokens for Google Calendar can occasionally need re-authorization if unused for extended periods; check the Integrations page periodically.
- Use one event type per workflow variant — If some meetings need different buffers or locations, create separate event types rather than overloading one with conditional settings.
Common Integration Issues
Calendar sync delay
If a time slot you blocked off in Google Calendar still appears as available on your Meetario booking page, the most likely cause is a brief sync delay. Meetario checks your Google Calendar for conflicts when a guest loads your booking page, but if you just added the calendar event moments ago, it may take a short time for the change to propagate through Google's API. In practice, this delay is usually under a minute. If slots remain stale for longer than that, go to Account -> Integrations -> Google Calendar and confirm the connection is still active — an expired OAuth token will silently stop all sync. Reconnecting takes seconds and immediately restores real-time conflict checking. For more details on how conflict detection works, see our Google Calendar conflict detection guide.
Slack message not showing calendar link
Meetario's Slack notification includes a meeting join link only if the event type has a location configured that generates a URL — such as Google Meet, Zoom, or Jitsi. If your event type is set to "In Person" or "Phone Call," there is no URL to include, so the Slack message will show the location text instead. If you expected a Google Meet link but do not see one, confirm that Google Calendar is connected (Meet links are generated through the calendar integration) and that the event type's location is set to Google Meet rather than a manual custom location.
Timezone mismatches between Slack and Calendar
When the time shown in a Slack notification does not match what appears on your Google Calendar event, the issue is almost always a timezone mismatch between your Meetario account settings and your Google Calendar settings. Meetario displays times in the timezone configured under Account -> Settings, while Google Calendar displays events in whatever timezone you have set in Google's own settings. To fix this, make sure both are set to the same timezone. If you work across multiple time zones, Meetario's booking page automatically shows available slots in the guest's local timezone, but your Slack notification and calendar event will always use your configured host timezone — this is by design so your own schedule view stays consistent.
Quick Start
Connect Google Calendar first, then Slack, then run a single end-to-end test booking before rolling this out publicly. Once it is working, teams running round-robin scheduling should also read our guide on Slack team booking workflows to extend this same three-way setup across multiple hosts. For a deeper look at how to route different booking types to different Slack channels, see our scheduling automation guide.