Business Pulse

A business owner should not have to inspect three screens just to prepare for the morning. Business Pulse brings the findings together and keeps each one linked to its source.

Try the report

Enable Business Pulse in Plugins, then choose Run report. No extra provider credentials or report settings are required. The plugin starts disabled. Use an authorized workspace, or explore Plugins in the fictional demo.

A fictional studio has a deal last updated ten days ago, a task due yesterday and a meeting tomorrow. The report can surface all three, giving the owner a starting point for deciding what to do next.

It combines open opportunities with overdue next actions or updates older than seven days, overdue pending or snoozed tasks, and non-cancelled meetings in the next 48 hours.

Reading the result

Treat each finding as a reason to open its source record, not as a verdict on its own. Check the inspected-record count and any truncation notice before drawing a conclusion from what's shown: each source caps at 100 records, the combined input at 64 KiB, and displayed findings at 20, so an empty result means nothing matched in that particular snapshot, not that your whole business is clear.

The report itself is read-only and deterministic: it never changes a business record and never contacts anyone. Its AI/MCP tool is run_business_pulse, and the host checks whether the plugin is actually enabled every time it runs. Running it needs no write approval and makes no model request on its own, though hosting and database usage still apply, and an AI conversation you have around the report can still incur its own model charges.

What this example teaches you to build

Compose several bounded sources into one useful view. Adapt the selection rules for your business while retaining source links. A future action workflow can build on the findings, but this report does not create tasks or send messages.

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.

What to check, and how to turn it off

Turning the plugin off in Plugins stops new evaluations immediately; source records and historical receipts stay exactly as they were. For a missing-source or access error, check the workspace's source registration and permissions, correct them, and rerun, and for a truncated result, go inspect the source records directly rather than assuming whatever got cut off would have been clear. Running the report again never creates a duplicate task or message, so re-running it to double-check is always safe.

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.