Integrations
You don't have to give up your habits. Your festival calendar already works in Apple, Google and Outlook via .ics and webcal, and the rest of your Google workspace, Drive, Sheets and Docs, is coming. The system always stays the source of truth; integrations are the mirror, not the original.
What connects
status per serviceSubscribe to the festival calendar or your personal feed and everything is in Apple Calendar, Google Calendar or Outlook. Refreshes automatically.
Soon not only reading but writing too: a shift you move in Google comes back into the system, with confirmation.
Site maps, contracts and riders from your Drive, linked to the right module, without stray folders and duplicate versions.
Every list as a Google Sheet for anyone who prefers to work in a spreadsheet, and the run sheet or a briefing as a Google Doc to share or print.
How we approach it
Through an open standard, .ics with webcal, your festival is in every calendar app today. No account to connect, no waiting for permission: a link is enough. This is the first integration and it's live.
Many organisations live in Google: Calendar, Drive, Sheets and Docs. We connect those step by step, so your festival data and your Google workspace look at the same truth.
An integration is a mirror, not a second set of records. What's true is in festival.productions; Drive and Sheets show it, they don't decide it. That way you never get three versions that are just slightly off.
Connecting is optional and per component. You link only what you want to share, see exactly what goes back and forth, and revoke an integration with a single click.
Everything in the system you can get back out: as a calendar subscription, as a spreadsheet, as a document. Your data is yours, even if you ever want to go a different way.
Like every module, an integration is tested in practice before it makes it in. What doesn't help on a real field doesn't make it in.