> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/set-up-your-studio/integrations.md).

# Integrations

Put your jobs on Google Calendar or Outlook, so your team sees them where they already look.

Schedulink can push your events to Google Calendar or Outlook, which means your photographers see the week's work in the calendar they already have open rather than logging in to check.

**Setup > Integrations**.

## Connecting a calendar

Set your Studio Email under **Setup > Organization** first, because that's the account the connection is made against.

Then choose Google Calendar or Outlook Calendar, sign in, and authorise access.

You'll be asked to grant permission to add, edit and delete events. Schedulink needs all three, because a job that moves has to move on the calendar too, and a cancelled job has to come off it.

This is one studio calendar connection, not a per-person one. Your team doesn't each connect their own account.

## Choosing which calendar a job lands on

The calendar is picked on the **event template**, not here. So picture days can go to one calendar and sports to another, and your team can subscribe to the work that concerns them.

See Event templates for where to set it.

## When jobs appear

An event syncs when it moves to **Scheduled**, not when it's created. A job sitting in Planning won't show up, which is usually the answer when someone says a booking is missing from the calendar.

Moving an event to Cancelled removes it again.

{% hint style="warning" %}
Adding a calendar to an event template only affects events created after that point. Jobs you booked earlier won't start syncing on their own.

The workaround is to duplicate the affected event and delete the original, which recreates it against the current template.
{% endhint %}

## What appears on a group event

When an event has sub-events, only the sub-events go to your calendar. The parent doesn't, because it isn't a schedulable job in its own right, it's the container holding the days.

So a client shooting Tuesday and Wednesday shows two calendar entries, not three.

## Disconnecting a calendar

Each integration shows its status, **Connected** or **Not connected**, with a button beside it to connect or disconnect. You'll be asked to confirm before anything is disconnected.

Disconnecting stops any new jobs reaching that calendar, and stops changes and cancellations flowing through.

{% hint style="warning" %}
**Events already on the calendar stay there.** Disconnecting doesn't clean up behind itself, so anything Schedulink has already put on your Google Calendar or Outlook remains, and it will no longer update if the job moves or is cancelled.

If you're disconnecting because the calendar is wrong, delete those entries yourself afterwards. Otherwise your team is looking at a schedule that has quietly stopped being true.
{% endhint %}

Reconnecting starts the sync again for jobs created from that point. Existing jobs won't come back on their own, the same as when you first add a calendar to a template.


---

# 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://schedulink.io/help-center/set-up-your-studio/integrations.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.
