Omniscio

Calendar Scheduler (Plugin)

Calendar Scheduler is the free Omniscio marketplace plugin that turns the app into a Calendly-style booking tool: define event types and availability, publish a public booking link, and let people request time that lands in your Google Calendar once you approve it (a new event type holds each booking for approval by default), while Omniscio handles approval, reschedule and cancellation — and, by default, puts today's meetings in your inbox.

On this page

Marketplace plugin — Calendar Scheduler is not built into Omniscio. Nothing on this page works until you install it from the Plugin Marketplace, enable it, and connect your Google Calendar.

What it is

A scheduling tool that lives inside Omniscio. You define event types (the kinds of meeting someone can book with you) and your availability, and the plugin publishes a public booking link you can hand to anyone — including people who do not use Omniscio. When somebody books, the booking waits as a request until you approve it (the default for a new event type), and then the meeting lands on your Google Calendar.

It is a first-party marketplace plugin: free, with its own sidebar entry, its own backend, and a set of CLI routes an agent can drive (most of them: booking, cancelling, rescheduling, approving, erasing and connecting Google are switched off for an agent in this version, see "Switched off for AI in this version"). It is the only thing that provides Omniscio's booking-link capability, so the Send Booking Link action in Team Time appears only while this plugin is installed, enabled and connected.

Because a booking link is a public door, the plugin treats some actions as things a human should agree to: creating or editing an event type, changing your availability, deciding an approval, cancelling or rescheduling, disconnecting Google Calendar, changing settings or webhooks, and running its heartbeat all ask for confirmation rather than acting silently.

If Google stops sharing the host's calendar, the plugin shows a red banner on every tab with a Reconnect Google Calendar button, marks Settings Needs reconnecting, and emails the host once per outage; invitees are told the page cannot take bookings right now. If an invitee's connection drops after they press Schedule, the booking page offers Check if it went through (yes or no only).

Where to find it

The booking site's full privacy policy is served at /privacy/, with /privacy redirecting there. The short privacy notice appears beside the booking form on wide screens and below it on phones.

  • Install it from the Plugin Marketplace (plugin-marketplace.md) — it is free, category productivity, authored by Edo.
  • Its own screen — once enabled it adds a Calendar Scheduler row to the sidebar (calendar icon), and hides the project panel inside it. That screen is where you build event types, set availability, and read your bookings.
  • Plugin settings — the plugin's settings panel is where its options live, reached the same way as any marketplace plugin's (plugin-settings-panel.md).
  • Team Time — the Send Booking Link action on a Team Time row creates a Gmail draft containing a booking link. It is only visible when this plugin is installed, enabled and running (team-time.md).
  • What an AI can and cannot do — see the section of that name below; the plugin's CLI routes are also listed in plugin-cli-discovery.md alongside every other plugin's.

How it behaves

The panel (1.11.0). It has five tabs: Calendar, Requests, Event Types, Availability and Settings (Settings is the old Account tab and now also holds Webhooks and the server address in a closed "For developers" section). Requests shows the booking requests you can still answer; Approve and Decline are held for ten seconds with an Undo button before anything is emailed, and are sent at once if you leave the tab. On a phone-width panel the Calendar opens on the Agenda. At 480px and under every control is at least 44px, text fields are 16px so a phone does not zoom, the week shows a strip of all seven days over one day's hours, and the month and week day lists open a booking in place like the Agenda, with Join, Reschedule and Cancel booking as full-size buttons.

Keyboard shortcuts. While the panel has focus and you are not typing, 1 to 5 open Calendar, Requests, Event Types, Availability and Settings, A approves the request whose row has focus (never while its Decline box is open, and only once), N opens New event type, C copies the focused event type's booking link or, on Calendar, your page link, and ? opens a Keyboard shortcuts list (Escape or its close button shuts it). The keys are fixed: there is no rebinding yet, because it waits for Omniscio's central Settings page. Keys do nothing in fields, the event-type editor, the reschedule picker, a confirm box or while connecting Google, and never with Ctrl, Alt or Cmd held. Hover or focus a button to see its key in the tooltip. A screen reader in browse mode keeps single letters for itself. See empty-states-and-tab-nav.md.

What the 1.11.0 store release added (now on master too). A booking row has Erase guest data: after a plain confirm it removes the booking and everything the guest gave you from Calendar Scheduler's own records. Up to 1.11.0 it also took the event off Google Calendar; from 1.12.0 it no longer touches your Google Calendar: the meeting stays there, so remove it yourself if you want it gone. An AI cannot do this in this version (see "Switched off for AI in this version"). A guest asking to move a booking shows on Requests as Wants to move, with the old time still booked until you answer. Connecting Google can finish with the one-time code Google shows, typed into Settings. Settings shows which server version is live. A booking you just cancelled or moved shows its new state at once, and if the list then fails to refresh, a note says so with a Refresh link. A very busy month says when some Google events are not shown, and a public booking address that cannot work is caught before it is saved. The plugin's version on master is 1.12.0 (pending release); the CHANGELOG has the entry.

When something goes wrong or takes too long. Every save or action button stops waiting after 30 seconds; the screen then says the result is unknown ("It may have worked") instead of staying stuck on "Saving..." or "Cancelling...". A cancel that gets no answer keeps its confirm open with a Refresh the list button, and a cancel or move that fails after you switched tabs still shows a message with an Open Calendar button. The reschedule time picker gives up after 20 seconds with a Retry button, and tells a brief Google hiccup ("try again") apart from a real disconnect ("reconnect it in Settings"). If your sign-in was revoked elsewhere, Event Types, Requests, Availability and Webhooks say "You have been signed out" with a Sign in again button instead of a Retry that could never work, even when they were already showing saved data; the saved data of the refused sign-in is cleared from every tab, and background details such as your booking link fall back to a saved copy only for a short while after an ordinary connection failure. The server address in Settings accepts only https addresses (plain http only for localhost), and switching to another server signs you out of this computer first, after asking.

Connecting Google Calendar. The plugin uses Google Calendar as the calendar of record. You connect it once (an OAuth flow you finish from the plugin), and it can be disconnected again later; disconnecting is a confirm-first action.

When an agent's reply is lost. If a change the agent sent (an event type or settings edit, say) times out or the connection drops, the plugin answers outcome_unknown: it may or may not have happened, so the agent should read the current state before trying again.

Applies only when the switched-off actions are turned back on. Repeating a book call whose booking already exists returns that booking marked replayed instead of booking a second slot. A cancel, reschedule or approval that a person approves late still works: its one-time confirm token (from confirm-token) stays valid for 8 days, longer than the 7 days Omniscio keeps an approval waiting. Every confirmed change that may have landed leaves an audit record marked applied or unknown. Today an agent cannot reach any of these actions.

Availability and slots. Open slots are derived from the availability you set, not typed in by bookers. A booking page preview and a slot list are both requestable, so you can see exactly what a visitor would be offered before you send the link.

When your saved hours cannot be read. If the weekly hours you saved have become unreadable, guests are never offered the default week in their place: your booking page shows no open times, and a booking or reschedule is refused with "That time is no longer available. Please pick another slot." Your Availability tab still opens the editor, with the red line "Your saved hours could not be read, so guests see no open times right now." at the top and the week set to Monday to Friday, 09:00 to 17:00, in your computer's time zone, with no date exceptions. Nothing is saved until you press Save availability; that save sends the whole schedule and replaces the unreadable one, then the red line goes away and guests see your new hours. A save that leaves out the date exceptions is still refused, because it would have to keep the unreadable ones. Any other loading problem still shows "Could not load." with Retry.

Approval, cancel and reschedule. A new event type holds each booking as a request until you approve it, while event types that existed before approvals shipped keep confirming straight away. The panel has no approval switch, and the plugin keeps a list of requests awaiting your decision. Bookings are not write-once: a booker can be given a link that lets them cancel or reschedule themselves, which produces a fresh list of reschedule times rather than a free-text change. When you cancel or move a booking yourself, the email to you says so ("You cancelled Sam's Strategy session") and prints the times in your own time zone; when the booker does it, the email names them. The approval page shows the booker's date next to their time whenever their day differs from yours. The link in the approval email does not stay a window onto the booker: once you have answered, or the request has expired or been withdrawn, it shows only the outcome and says "Their details are no longer shown here" (you still see them in the panel), and after the requested time has passed it says "This link is no longer active." If an answer times out or fails, the page keeps Approve and Decline off while it re-reads the request, then shows what really happened.

On the booking page, a "try later" answer is shown as the server wrote it with "No booking was made", a switched-off link tells the booker to ask you for a new one, and the confirmation has its own address ending in /booked so a refresh or the Back button shows it again. That copy lives in the booker's browser tab only (session storage, never the manage link), so a restored confirmation has no manage link. While a move is being sent from the manage page, "Keep the current time" is switched off.

The reschedule list does not count the meeting's own calendar event as busy, so its current time and the times next to it stay on offer. Approving checks that the requested time itself is still free, at the length it was requested for. After a disconnect, existing bookings stand but cannot be moved: the reschedule page tells the invitee to contact you, and approving a held request asks you to reconnect first.

If a future meeting disappears from the exact Google calendar where Calendar Scheduler created it, the booking is cancelled and no longer holds that time. The guest receives a neutral cancellation email; the host is told whether that email was actually queued. Temporary Google failures, an expired connection and rate limiting do not cancel anything. If Calendar proves that a future booking never received a Google event after its creation window, the booking is also cancelled and both the host and guest are emailed. Past meetings are left alone. Renaming an event type keeps its 20 most recent old links working: the page quietly forwards to the newest address, while booking and slot requests continue without redirecting. An archived event type releases all of its links, and reusing an old address makes that address belong to the new event type. Links older than the retained history stop working.

Today's agenda in the inbox. The plugin has one user-facing setting, Today's agenda in the inbox, on by default. While it is on, today's meetings appear as inbox rows — a summary before the day starts, then a reminder 15 minutes before each meeting. Turning it off clears those rows; your bookings, invitees and reminder emails are unaffected.

Health check. The plugin runs a heartbeat every 30 minutes that checks its own health. It is gated behind approval, so it does not spend anything or reach outside the machine on its own.

Guests and private notes. An invitee can add up to 10 guests; each gets the Google calendar invitation. When a booking has guests, that invitation carries only "Booked with Calendar Scheduler.", never the invitee's notes or their answers to your questions. You still get both in your booking email and in the Calendar panel, and the booking form tells the invitee so. A booking with no guests keeps the full description.

The booking page when it does not load. If your main link (/<handle>) loads slowly or fails, the page says so ("This page is taking too long to load" or "Could not load this page") and offers Try again. Only a link that really does not exist says "Booking link not found".

Webhooks. The plugin can post to a webhook URL you configure; changing that configuration is a confirm-first action. In the panel's Webhooks section (Settings, For developers) a delivery that gave up for good can be sent again from the booking as it is now, shows the time and plain reason of each try, and triggers one email to the host at most once a day. A save from an older window is refused with "It was changed somewhere else" and the current settings are shown. A webhook test that your server refuses or cuts off says so ("Your server refused the connection or cut it off. Check that it is running and accepts https on that address.") instead of claiming a 5-second timeout; a real timeout keeps its own message. See src/plugins/calendar-scheduler/docs/contracts/webhook-delivery-pii-retention.md.

What an AI can and cannot do

An agent drives this plugin through its CLI routes (plugin-cli-discovery.md). In the version that ships the switch-off (master since 9 Nov 2026, version 1.12.0 pending release; an older installed build such as the store's 1.11.0 may still list the switched-off actions below) the plugin lists 31 routes, grouped by what they act on:

  • Event types — list, view, create, edit, delete (delete archives rather than destroys).
  • Availability — read and set.
  • Bookings — list bookings; get booking links; view one booking; list its reschedule times; list requests awaiting approval (read only).
  • Booking pages — preview a page and list open slots (read only).
  • Identity — read the connected identity and the display name, and set the display name.
  • Connection — check whether Google Calendar is connected, and disconnect.
  • Settings and webhooks — read and change.
  • Discovery — plugin status, and describe-an-action.

Several reads exist twice, as view-… routes and as "older path" routes, so a read never waits on a person (view-event-types, view-event-type, view-availability, view-profile, view-settings, view-webhooks). Every route that changes state is marked requiresConfirmation in manifest.json and asks the user first: creating, editing or deleting an event type, setting availability, setting the display name, disconnecting, and changing settings or webhooks. The manifest carries no safe marks, so no write runs without asking. Reading is not gated.

Switched off for AI in this version

An agent cannot do these eight actions today. A person does them in the panel.

Switched-off route What it does
connect, connect-poll start and finish connecting Google Calendar
book book a slot on a booking page
confirm-token prepare a booking change (issues the one-time token)
manage-cancel cancel a booking
manage-reschedule move a booking
manage-erase erase a guest and their booking
approval-decide approve or decline a booking request
  • Why: Edo switched them off on 9 Nov 2026 until they are proven. His words were "connect, book, cancel". Erase and approve or decline go with them because every booking change needs the token from confirm-token.
  • What the AI sees: a switched-off route is not registered, not in manifest.json and not in status or describe. A direct call gets the app's own "has no action" answer (404), and describe for one answers not_available (404). An agent should say "a person does this in the panel" instead of promising it.
  • The panel is untouched: it talks to the Calendar server directly, so a person can still connect, cancel, reschedule, approve, decline and erase there.
  • How it comes back: all eight return together, in one change that takes them off the switched-off list and puts their entries back in the plugin's action list. The text on this page about a lost reply, replayed and the 8-day confirm token applies from then on.
  • Older builds: versions before the switch-off listed these actions, and an installed copy of one may still show them. Trust the plugin's own status answer over this page for the build you have.

Pointing at the panel's controls

The in-app assistant can point at the Calendar panel's main controls: the five tabs, the refresh chip, and the main buttons and fields of the Calendar, Requests, Event Types, Availability and Settings views (the Connect Google Calendar button included). The plugin lists 46 of them in manifest.json under uiAnchors, and marks each control on the page with an invisible data-ui-anchor attribute. A repeated control, such as a meeting row or an event type card, has one anchor, not one per copy. A meeting in the week, all-day or timed, is one anchor, and a click on it opens that day. In the Agenda view the "upcoming meeting" row sits in a side list that is hidden on a narrow window (under 900 pixels), so there the assistant points at "a meeting in the agenda", which is visible at every width. The Connect button shows a link to open, and the code box takes the code Google shows; neither promises a code length. This is not released yet: it ships with the next Calendar store version, and a build installed before that has no anchors, so the assistant cannot point at anything in Calendar there. The list is ui-anchor-table.ts; the rules and checks are in src/plugins/calendar-scheduler/docs/contracts/panel-ui-anchors.md.

How plugins are found, installed and enabled is on Plugin marketplace, and where a plugin's own options live is on Plugin settings panel. What a plugin can draw on top of the app is on Plugin UI access. The row that offers Send Booking Link is documented on Team Time, and the CLI-route surface this plugin's routes appear in is Plugin CLI discovery.

Last verified 2026-11-18