> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

# Connect your calendar

Connect your Google or Outlook calendar to dCal so busy times block new bookings and every confirmed booking lands in your calendar, with an online meeting link when you want one. Connect several acco

Connect a calendar and dCal does two jobs with it: it reads your busy times so nobody books you on top of another meeting, and it writes each confirmed booking into your calendar. You can connect Google Calendar or Outlook / Microsoft 365, and as many accounts as you use.

Without a connected calendar dCal still takes bookings, but it only knows your hours and the bookings made in dCal. It cannot see the rest of your day.

***

## Connect your first calendar

**Step 1:** Go to [app.dcal.ai](https://app.dcal.ai) and open **Calendars** in the left menu. With nothing connected yet, the page reads **No calendars connected yet**. Click **Connect a calendar**.

> **💡 Tip:** The **Connect** button in the **Get bookable** checklist on **Home** opens this same page.

***

**Step 2:** The **Connect a calendar** dialog asks you to choose a provider. Click **Google Calendar** or **Outlook / Microsoft 365**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-4742798fa52636869f213acebfa4c19c25de5a92%2Fdcal-connect-a-calendar-02-choose-provider.png?alt=media" alt="The Connect a calendar dialog with the text Choose a provider to link, the Google Calendar and Outlook / Microsoft 365 buttons boxed, and Close"><figcaption><p>Two providers. You can come back and add the other one later.</p></figcaption></figure>

***

**Step 3:** Under **Which account are you connecting?**, check the **Account email**. dCal fills in the email you signed in with. If the calendar belongs to a different address, type that address instead. Click **Continue**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-7aad49146e097c78ec4867a8ee668bd61348cf7b%2Fdcal-connect-a-calendar-03-account-email.png?alt=media" alt="The dialog step Which account are you connecting? with the Account email field boxed and filled in with jane.doe@example.com, its hint, and the Back and Continue buttons"><figcaption><p>Enter the address of the calendar account you are about to sign in to.</p></figcaption></figure>

> **⚠️ Note:** Type the address of the account you will sign in to in the next step. dCal uses it to keep each connection separate, and to recognize the account if it is already connected elsewhere in Dapta.

***

**Step 4:** A small window opens. Sign in to Google or Microsoft with that account. Google or Microsoft asks you to allow access: allow it. The window then shows **Connected** and closes by itself. If it stays open, click **Close window**.

If no window opens, your browser blocked it, and the dialog tells you so. Allow pop-ups for app.dcal.ai and click **Continue** again.

***

**Step 5:** Back in dCal, the dialog shows **Waiting for you to finish connecting…** and keeps checking on its own. As soon as it finds the new connection it closes, and the calendar appears in your list. If you already finished in the small window and the dialog is still waiting, click **I’ve finished connecting**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6cea11b98e7db6de5afa6c4357f25117cb63361d%2Fdcal-connect-a-calendar-04-waiting.png?alt=media" alt="The dialog showing a spinner, the text Waiting for you to finish connecting…, a line asking you to finish in the popup window, and the I’ve finished connecting button boxed"><figcaption><p>dCal notices on its own when you are done. The button is there if you want to check right away.</p></figcaption></figure>

If the dialog says it still finds no connection for your email, you most likely signed in with a different account. Start again and enter the address you actually signed in with.

***

## Your calendars list

Once a calendar is connected, **Calendars** shows a summary and one row per account under **Your calendars**.

* The summary tells you where new events go (**New events are added to** and the account) and how many calendars are checked for conflicts.
* Each row shows the account email, the provider, a status pill and, on the calendar that receives your bookings, a **Destination** badge.
* **Connect another**, at the top right, adds one more account.

### Check for conflicts and Add new events here

Each row has two settings. They are independent of each other, and they save the moment you click them.

| Setting                 | What it does                                     | How many                                                    |
| ----------------------- | ------------------------------------------------ | ----------------------------------------------------------- |
| **Check for conflicts** | Busy times on this calendar block new bookings.  | Any number of calendars.                                    |
| **Add new events here** | Confirmed bookings are written to this calendar. | Only one. Choosing it on one row clears it from the others. |

New rows start with **Check for conflicts** on. The first calendar you connect also gets **Add new events here**, unless another calendar already has it.

A common setup: check both your work and your personal calendar for conflicts, and add new events only to your work calendar.

> **⚠️ Note:** Each row is a whole Google or Microsoft account, not a single calendar inside it. dCal does not list the separate calendars inside an account, so you cannot pick one of them here. If you keep work and personal calendars in different accounts, connect each account and set each row the way you want.

### Several accounts

Connect as many accounts as you need, Google and Outlook mixed. Click **Connect another** and repeat the steps above. When a provider is already connected, its button in the dialog says so and still lets you add another account.

If you already connected a calendar in the Dapta app with your user (for example for your agents), dCal picks it up the next time you go through **Connect a calendar**. It shows up as one more row, with **Check for conflicts** on. Untick it if you do not want it checked.

***

## Test a calendar

Each row's status pill tells you whether dCal can reach the account: **Connected**, **Needs attention**, or **Checking…** while it checks. dCal checks every row when you open the page, and the line **Checked** with a time (or **Not checked yet**) shows when it last did. Click the pill to check again. When a row needs attention, the reason shows in red under its buttons.

For a full check, use **Test**.

**Step 1:** Click **Test** on the row. The button reads **Testing…** while dCal checks the connection and reads your busy events for the next 14 days.

**Step 2:** Read the banner that appears in the row.

| The banner starts with                         | What it means                                                          | What to do                                                                         |
| ---------------------------------------------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Working**, and says conflict checking is ON  | dCal reads this calendar and uses it to block times.                   | Nothing.                                                                           |
| **Working**, and says conflict checking is OFF | dCal can read this calendar but does not use it to block times.        | Tick **Check for conflicts** if busy times on this calendar should block bookings. |
| **Not connected**                              | The calendar is not linked yet.                                        | Click **Reconnect**.                                                               |
| **Could not reach your calendar**              | dCal could not reach the account. Access may need to be granted again. | Click **Reconnect**.                                                               |
| **Connected, but reading your events failed.** | The link exists, but reading your events did not work this time.       | Run **Test** again in a moment. If it keeps failing, click **Reconnect**.          |

***

## Reconnect

When a test fails, a **Reconnect** button appears next to the result. Click it and go through the same steps as the first time: choose the provider, enter the same account email and sign in. dCal updates the row you already have instead of adding a new one, so your **Check for conflicts** and **Add new events here** choices stay as they were.

***

## Disconnect

**Step 1:** Click **Disconnect** on the row.

**Step 2:** dCal asks **Disconnect this calendar?** and explains that the account stops being checked for conflicts and that new bookings will not be written to it. Click **Disconnect** to confirm.

| Disconnecting does                                                     | Disconnecting does not                                           |
| ---------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Remove the account from your list in dCal.                             | Cancel or change any booking.                                    |
| Stop checking its busy times.                                          | Delete events dCal already wrote to that calendar.               |
| Stop writing new bookings to it.                                       | Change anything in your Google or Microsoft account.             |
| Remove it from any event that used it in **Calendars for this event**. | Affect the same calendar where it is connected in the Dapta app. |

> **⚠️ Note:** If you disconnect the calendar marked **Destination**, new bookings are not written to any calendar, and online meeting links cannot be created, until you choose **Add new events here** on another row.

Events dCal already wrote stay in that calendar. If you later cancel or reschedule one of those bookings, open that calendar and remove or move the old event if it is still there.

***

## What dCal writes to your calendar

| When                               | What happens in your calendar                                                                                                                                                |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A booking is confirmed             | dCal creates an event in the calendar with **Add new events here**. The event carries the title of your event and lists you and the person who booked.                       |
| A booking needs your confirmation  | Nothing is written while the request waits. The event is created when you confirm it. See [Require confirmation](https://docs.dapta.ai/dcal/events/require-confirmation.md). |
| A team booking has several hosts   | Each host gets the event in their own calendar with **Add new events here**.                                                                                                 |
| A booking is rescheduled           | The same event moves to the new time. No second event is created.                                                                                                            |
| A booking is cancelled or declined | The event is removed from every calendar it was written to.                                                                                                                  |

To change the meeting's title or description in the calendar, open the event's **General** > **In the calendar** section. Use **Calendar event title** and **Calendar event description**, with variables for the guest's details or answers. See [Calendar event text](https://docs.dapta.ai/dcal/events/event-settings.md#calendar-event-text).

dCal never writes the same booking twice to a calendar.

Your calendar does not email your guest about these events: dCal's own emails, with their calendar invite, are your guest's invitation, update and cancellation. The exceptions are in [The calendar invite](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#the-calendar-invite).

A calendar problem never cancels or holds up a booking: the booking stands and the emails go out. If a confirmed booking is missing from your calendar, run **Test** on the calendar marked **Destination**.

***

## Add an online meeting link

dCal can create a meeting link for each booking, through the calendar that receives your events.

**Step 1:** Make sure one calendar on the **Calendars** page has **Add new events here**.

**Step 2:** Open **Events**, click **Edit** on the event and, in **General** > **Basics** > **Location**, choose **Online meeting**. The hint reads **A meeting link is created automatically when the booking is confirmed.** Click **Save changes**.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-ef51ddd8588ad82b05227390404bf8d0bfe805fa%2Fdcal-connect-a-calendar-09-online-meeting.png?alt=media" alt="The Location field of an event set to Online meeting, with the hint A meeting link is created automatically when the booking is confirmed., both boxed"><figcaption><p>Pick <strong>Online meeting</strong> once, and every confirmed booking of this event gets its own link.</p></figcaption></figure>

If your calendar reports the name of its meeting service, the option shows that name instead of **Online meeting**.

On a team event the option always reads **Online meeting**, and the hint is different: it says the location applies to every host, and that each booking's meeting link comes from the calendar where the assigned host (or, on collective and fixed round-robin events, one of the booking's hosts) receives new events. See [Round-robin, collective and fixed hosts](https://docs.dapta.ai/dcal/teams/scheduling-methods.md).

How the link behaves:

* It is created when the booking is confirmed. For a request that waits for you, that is the moment you confirm it.
* There is one link per booking. On team bookings, the other hosts find it in their copy of the event.
* Events left on **Not specified** get a link too. **In person**, **Phone call** and **Custom** events never get one.
* Your guest gets the link in dCal's emails and in the calendar invite they carry, not in an invitation from your calendar.
* A reschedule keeps the same link.
* The confirmation email waits a short moment for the link. If the link is not ready in time, the email goes out without it, and your guest finds the link on the page they open with **Manage your booking**.
* If no calendar has **Add new events here**, the event editor warns you that no meeting link can be created. Bookings still work in the meantime.
* On team events, the link comes from a host's own calendar with **Add new events here**. The team event editor warns you when hosts are missing one, and each host sets it on their own **Calendars** page.

***

## Use different calendars for one event

Your settings on the **Calendars** page are the starting point for your events. A personal event can use its own.

**Step 1:** Open **Events**, click **Edit** on the event and select **General** > **Hosts and calendars** > **Calendars for this event**.

**Step 2:** For each connected calendar, tick **Check for conflicts** (any number) and choose **Add events here** (one). The section starts from your **Calendars** page settings. **Manage calendars** takes you to that page. Click **Save changes**.

When you save a personal event, it keeps the choices shown in **Calendars for this event**. A change you make later on the **Calendars** page, such as a calendar you connect afterwards, does not reach that event until you update this section and save the event again.

If a calendar you chose for an event is disconnected later, the event stops using it, and when none of its own choices are left it goes back to your **Calendars** page settings. Team events do not show this section: each host's own **Calendars** settings apply.

***

## Good to know

* Changes on the **Calendars** page save at once. There is no **Save** button.
* If you have not uploaded a photo, your booking page can show the photo of your connected calendar account, when that account has one. See [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md).
* How busy times turn into open times, and what happens when a calendar cannot be read, is explained in [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

## Related

* [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md)
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md)
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md)
* [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md)
* [Troubleshooting](https://docs.dapta.ai/dcal/troubleshooting.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
