All your calendars, in one view
Connect every Google Calendar and Outlook account you actually use. See them in one color-coded view (month, week, day, or agenda) right next to your messages, tasks, and the Brain. Handle invites where they arrive, find free time across the calendars you have connected, let customers book you on a public page, and run workflows that read and write your calendar.
Every calendar you connect. Color-coded. Four views.
Bring in your work Google Calendar, your personal one, an Outlook account, a shared team calendar, whatever else you have. Each connected calendar gets its own color, so a week view shows the work meetings, the personal blocks, and the team events overlaid on the same grid without you having to scan between accounts.
Switch between Month, Week, Day, and Agenda views with one click. Create new events directly from the calendar surface. Toggle individual calendars on and off when you want to focus. A mini-month picker in the rail makes jumping to any date one click.
RSVP without leaving the surface the invite arrived on
When a calendar invite comes in by email, it shows up next to the rest of the conversation, not in a separate tab. Accept, decline, mark tentative, or propose a new time in one tap. The reply goes back through Google Calendar or the Microsoft Graph API the way the original invite expected, and your real calendar updates on both sides.
Propose New Time works on both providers. The person who sent the invite gets the standard reply they would have gotten from Gmail or Outlook, with your suggested slot attached.
Free time, found for you. Across the calendars you have connected.
The assistant can answer questions about your calendar in plain language. Ask when you are free on Thursday afternoon and you get a list of open blocks, not a calendar grid you have to scan. Ask for a time that works for you and a teammate and we look at both of your free busy data and propose a window that works for both.
Everything respects your time zone, including when the people you are scheduling with are in a different one. Free busy lookups stop at free busy; the assistant never sees the title, attendees, or description of a private event when it is computing availability.
Let customers book a meeting on a page powered by your Brain
A public artifact (a landing page, a public FAQ, a launch microsite) can show your live availability and let a visitor book a meeting on your real calendar. The visitor picks a time, enters their name and email, and the event appears on your calendar with them as an attendee. They get the calendar invite they would expect.
Because the public page is powered by the Brain, the same page can answer the visitor's questions and then close the meeting, without sending them to a separate Calendly link or back to your inbox. The slots they see are real, collision detection runs every time the page is loaded, and only Google Calendar free busy is exposed (no event titles, no attendees).
See when your team is free. Don't see what they are doing.
When you want to find time across a team, the assistant looks at the free busy data for the people you ask about and proposes a window that works. Private events stay private: titles, descriptions, attendees, and organizers are not exposed to teammates running availability queries. Public events on a teammate's calendar can be listed by title; anything marked private is filtered out.
Every member can opt out of team availability lookups from their account settings. When someone opts out, queries against the team simply skip them. No silent exposure, no opt-out-by-policy-document.
Workflows that read the calendar. Workflows that write to it.
Workflows can check team calendars as a step in a flow, so an automation can answer questions like "is everyone on the sales pod free Wednesday morning" before deciding what to do next. Other workflow actions can create a calendar event, reschedule one, or invite a list of attendees, the same way they can draft a reply or update a CRM record.
The result is that scheduling becomes part of automation rather than the thing that breaks every automation. A workflow that handles a sales follow-up can both reply to the prospect and put time on the calendar for the call.
Your calendar is not training data for anyone
Calendar data is encrypted at rest with AWS-owned keys. No this+that employee can decrypt it. We never use Customer Data, including calendar events and the contents of inbound invites, to train, fine-tune, or improve any machine learning model, ours or any third party's. The contractual commitment lives in our DPA. When a public booking page exposes availability, it exposes only free busy; titles, attendees, organizers, and descriptions stay private.
Pull every calendar into the same place the rest of your work lives
Connect your calendars in two clicks. One color-coded view across all of them, invites you can act on, availability you can ask about in plain language, public booking pages powered by your Brain, and workflows that schedule for you.
Get startedFree during beta · No credit card required