Events and productivity

Connectors → Events & Productivity turns calendar, file, document, spreadsheet, Slack, and Teams changes into governed Flolah work.

The generic flow is:

provider event → durable inbox → workflow or goal → policy check → connector action → receipt and verification

Connect Google Workspace, Microsoft 365, Slack, or Teams under OpenConnector, then bind each semantic operation to an exact connector action ID. App ID is selected from compatible apps connected for your company; Action ID and the optional verification action are selected from the live action catalog reported by that app. Exact bindings prevent agents from guessing an external action from keywords. At run time Flolah resolves the owner-scoped binding, applies Action Control, executes only the selected action, suppresses duplicate retries, and stores an action receipt.

For read-only calendar access, you may instead configure a Published calendar URL (ICS) subscription. It can trigger calendar-change events and automatically provides event listing and free-slot searches when no OAuth read binding is available. It cannot modify the calendar. Creating meetings or invitations, rescheduling, and cancelling require a Google Calendar or Outlook Calendar OAuth binding.

The app picker is operation-aware as well as provider-aware. An Outlook mail connection cannot be used for calendar_list_events; a calendar-capable connector action must be present. The API also rejects action IDs that do not belong to the selected app. Agents with large permanent tool grants retain those grants, while each chat request receives a bounded relevant subset so model tool-count limits do not remove the requested capability.

Subscriptions can retain an event for inspection, start a published event-enabled workflow owned by your company, or start a durable goal plan. The event type is selected from a provider-aware dropdown; arbitrary free-text values and unsupported provider/event combinations are rejected. Google Workspace and Microsoft 365 offer email, calendar, and file triggers. Slack and Microsoft Teams offer message and reaction triggers. The webhook secret is displayed once and stored only as a hash.

Reads and searches are R0. Internal document/spreadsheet writes are R1. Calendar invitations, external comments, and Slack/Teams sends are R2 and follow Action Control approval and scoped overrides. The pack does not expose destructive or financial operations.

For testing, begin with a narrow read-only calendar range or a uniquely named document search. Live provider validation requires the matching OAuth account. A fixture/harness result validates Flolah's contract but is not a claim that Google or Microsoft was tested live.

Failed events retry with bounded backoff. After five attempts they remain in the owner-scoped dead-letter inbox, where the error can be corrected and the event replayed. Completed history and receipts follow the user's retention setting.