Meetings

Set onlineMeetingService on a calendar event and Workwae creates a Zoom or Webex meeting for it. Connect a host first: each user's own grant, or one server app for the organization.

Meetings with calendar eventsCopy Anchor Link

With onlineMeetingService (zoom or webex) on a calendar event, Workwae:

• creates the meeting and writes its join link into the event's onlineMeetingUrl on Google, Microsoft 365 and CalDAV;
• moves the meeting when the event moves;
• deletes it when the event is deleted or cancelled.

Meetings need the meetings module in the tenant's plan; without it the field answers 403 plan_module_unavailable.

curl -X POST "https://api.workwae.com/v1/accounts/$ACCOUNT_ID/calendar-events" \
  -H "Authorization: Bearer $WORKWAE_API_KEY" \
  -H "content-type: application/json" \
  -d '{
  "calendarId": "'"$CALENDAR_ID"'",
  "subject": "Customer onboarding",
  "start": { "dateTime": "2026-11-03T15:00:00", "timeZone": "America/Chicago" },
  "end": { "dateTime": "2026-11-03T15:45:00", "timeZone": "America/Chicago" },
  "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=TU;COUNT=8"],
  "onlineMeetingService": "zoom"
}'

• A series gets a recurring meeting translated from its rule. A rule the service cannot repeat by is refused with meeting_recurrence_unsupported before anything is created.
• A new subject, start, end or rule moves the meeting.
• Changing one occurrence leaves the service's series alone; its join link works for every occurrence.
• Only one of onlineMeeting, onlineMeetingUrl and onlineMeetingService may be set (multiple_meeting_options).

Workwae only creates, updates and deletes meetings and looks up the host. It never reads recordings, chat, transcripts or participant lists.

Who hosts the meetingCopy Anchor Link

For each event, Workwae picks the host in this order:

1. The account's own grant at the service.
2. The tenant's server app for that service.
3. Otherwise it refuses with meeting_service_not_connected.

A grant that needs reconnecting is not passed over for the app.

• A server app is used only where the provider vouches for the mailbox's address: Gmail, Microsoft 365, and IMAP accounts signed in with Google or Microsoft OAuth.
• A password IMAP account needs its user's own grant.
• A mailbox with no matching user at the service is refused with meeting_host_missing.

Per-user grantsCopy Anchor Link

curl -X POST "https://api.workwae.com/v1/accounts/$ACCOUNT_ID/meeting-connect-sessions" \
  -H "Authorization: Bearer $WORKWAE_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "service": "webex", "redirectUri": "https://app.example.com/settings/meetings", "state": "user-42" }'

List an account's grants, or disconnect one. Disconnecting deletes the grant; existing meetings stay.

curl "https://api.workwae.com/v1/accounts/$ACCOUNT_ID/meeting-connections" \
  -H "Authorization: Bearer $WORKWAE_API_KEY"

curl -X DELETE "https://api.workwae.com/v1/accounts/$ACCOUNT_ID/meeting-connections/webex" \
  -H "Authorization: Bearer $WORKWAE_API_KEY"

Server appsCopy Anchor Link

Register one server app per service per tenant; a second answers meeting_app_exists.

• A new app starts unverified.
• POST /v1/meeting-apps/{appId}/test requests a token the way meetings will, optionally looks up a host by address, and marks the app active or failing.
• Deleting a server app leaves the meetings it created at the service.

curl -X POST "https://api.workwae.com/v1/meeting-apps" \
  -H "Authorization: Bearer $WORKWAE_API_KEY" \
  -H "content-type: application/json" \
  -d '{
  "kind": "zoom_s2s",
  "name": "Acme Zoom",
  "accountId": "'"$ZOOM_ACCOUNT_ID"'",
  "clientId": "'"$ZOOM_CLIENT_ID"'",
  "clientSecret": "'"$ZOOM_CLIENT_SECRET"'"
}'

curl -X POST "https://api.workwae.com/v1/meeting-apps/$APP_ID/test" \
  -H "Authorization: Bearer $WORKWAE_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "user": "priya@acme.com" }'

Errors and reauthorizationCopy Anchor Link

A 401 or 403 from the service is retried once with a fresh token. Refused again, the grant is marked reauth_required and meeting_connection.reauth_required is sent with the service, host email and reason. Mail and calendar sync never use meeting grants, so they keep running.

Send the user to reconnect on the first two:

import { isApiError } from "@workwae/sdk";

try {
  await workwae.calendarEvents.create({ ...booking, onlineMeetingService: "zoom" });
} catch (error) {
  if (
    isApiError(error, "meeting_service_not_connected") ||
    isApiError(error, "meeting_service_reauth_required")
  ) {
    return askUserToConnect(booking.accountId, "zoom");
  }
  throw error;
}

Every route is in the Meeting connections and Meeting apps references.