Meeting preparation

Preparing well starts with knowing what is coming. Meeting preparation brings the next meetings into a time-ordered report, with links back to the calendar records your team already uses.

Try the report

Enable Meeting preparation in Plugins, then choose Run report. The workspace must contain readable calendar events; the report itself has no additional connection settings. The plugin starts disabled. Use an authorized workspace, or explore Plugins in the fictional demo.

A fictional confirmed discovery meeting starts in an hour, while another appointment was cancelled. Run the report to see the confirmed meeting and open its source record to plan your preparation.

Non-cancelled meetings starting now through, but not including, 48 hours ahead are sorted by start time. This version identifies meetings; it does not research attendees or generate a briefing.

Read the result

Each finding is a reason to inspect its source. Check the inspected-record count and any truncation indication before drawing a conclusion. Each source is limited to 100 records, the combined input to 64 KiB, and displayed findings to 20. An empty result means no matches in that snapshot; it does not certify the entire business.

The report is read-only and deterministic. It neither changes business records nor contacts anyone. Its AI/MCP tool is run_meeting_prep; the host checks whether the plugin is enabled when it runs. The report needs no write approval and makes no model request. Hosting and database usage still apply, and an AI conversation around the report can incur model charges.

What this example teaches you to build

Use time-windowed records as the foundation for a preparation workflow. A richer briefing would need additional sources and a separately implemented step. Keeping those layers explicit makes the small report useful on its own.

Start with the report source and its module manifest. The report code receives declared fields inside the shared isolate; the host supplies access and records the result. Reuse that boundary when changing the logic.

Disable or recover

Turn the plugin off in Plugins to stop new evaluations. Source records and historical receipts remain. For missing-source or access errors, check the workspace's source registration and permissions, correct them, then rerun. For truncated results, inspect the source records rather than assuming the omitted records are clear. Repeating a report does not create duplicate tasks or messages.

The developer guide links the source contracts and controlled tests, including npm run test:report-plugins. Those fixtures exercise the report behavior; they do not verify every installation's data or provider connections.