Outlook Add-in

Click-to-book Workestra meetings from inside Outlook on the web, desktop, and mobile.

The Workestra Outlook Add-in adds a "Schedule with Workestra" pane to your Outlook compose window. Pick which booking link to send, and a pre-formatted snippet — with your availability or a direct link — gets inserted into the email body.

Useful when most of your scheduling outreach happens from inside Outlook and copy-pasting URLs from a separate tab is friction.

Outlook add-in pane

Screenshot needed — Outlook compose window with the Workestra add-in pane open on the right showing booking links

What it does

Insert booking link — drop a Workestra link with your availability text into the email body
Insert offered slots — pick 3–5 specific slots, formatted as a clickable HTML block, that the recipient picks from
Insert team page link — drop a team page URL for departmental scheduling
Open Workestra calendar — direct link to /calendar in the host's default browser

Installation

The add-in is a single-tenant Microsoft 365 add-in distributed via:

Microsoft AppSource — search "Workestra Scheduling" (when published)
Sideload manifest — for IT-managed deployments. Download the manifest from /settings/integrations/outlook-add-in → Manifest, then sideload it via the Microsoft 365 admin center for your org.

After installation, "Workestra" appears in the Add-ins menu of Outlook compose windows (web, desktop, mobile).

Authentication

The add-in uses the same Workestra session as the web app. Sign in once via the add-in pane; the session persists across compose windows. Sign-out from /settings/security.

For shared mailboxes (e.g. support@), the session reflects the user who installed the add-in — not the shared mailbox owner. Send-on-behalf-of is supported through standard Outlook delegation.

Distribution

The add-in source lives in apps/outlook-addin/ of the Workestra monorepo. It's a standard Microsoft 365 add-in (Office.js + manifest XML). For organizations that want to host it themselves (e.g. internal CDN, no AppSource dependency), the build artifacts are shippable.

What's NOT supported

Outlook 2016 and earlier desktop — manifest v1 only; not all features render
Outlook Web Access (legacy) — modern OWA only
Server-side ingestion of Outlook events as Workestra activities — that's a different integration (Microsoft 365 Calendar)