Connect a calendar to Meetin.gs

Short answer: Choose conflict calendars and where confirmed meetings are added. Begin with “Authorize the calendar account using the provider's consent screen.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

Authorize the calendar account using the provider's consent screen.Start with the intended outcome and the record that controls it.
Select every calendar that should block otherwise open time.Review every related setting before saving so one rule does not mask another.
Choose the destination calendar for confirmed events.Keep private data and guest-facing information clearly separated.
Book, reschedule, and cancel a test appointment before publishing.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot connect a calendar to Meetin.gs

These are the failures reported most often for this specific task, with the cause that explains each one.

Connected calendar events are not blocking time.

Authorization succeeded but the calendar was not selected as a conflict source. Connecting an account and choosing which of its calendars block time are two separate steps.

All-day and tentative events behave unexpectedly.

Decide explicitly whether all-day events, tentative invitations, and declined events should block bookings, then test one of each rather than assuming a default.

The connection keeps dropping.

Password changes, revoked consent, MFA enrolment, and administrator policy all invalidate tokens. Name an owner for reconnects and use a service identity where the provider supports one.

Related Meetin.gs help

Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.

Connect a calendar to Meetin.gs acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. Authorize the calendar account using the provider's consent screen.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Select every calendar that should block otherwise open time.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Choose the destination calendar for confirmed events.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Book, reschedule, and cancel a test appointment before publishing.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Calendar connections

Check connected calendars for busy time and add confirmed meetings to the calendar you choose. This page explains calendar connections requirements. Confirm production availability before depending on this capability.

Review scope

Connect a calendar to Meetin.gs: frequently asked questions

Short answers to the questions organizers ask most about connect a calendar to Meetin.gs.

Does Meetin.gs check my Google or Outlook calendar for conflicts?

Connected-calendar conflict checking is documented as a requirement rather than a shipped feature. Confirm it is available for your deployment before publishing availability that depends on it.

Can I block time from one calendar and write events to another?

That is the intended model: several calendars act as conflict sources while one is the destination for confirmed meetings. Verify both halves with a test booking.

What permissions does a calendar connection need?

Enough to read busy times from the calendars you select and to create events on the destination calendar. Grant nothing broader, and record which account holds the connection.

Why do connections break?

Password changes, revoked consent, new MFA enrolment, or administrator policy all invalidate tokens. Assign an owner for reconnects before rollout.