Business Pulse

See pipeline risks, overdue commitments and upcoming meetings in one report.

Updated September 6, 2026 3 min read

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.

Business Pulse report in the fictional Plugins workspace, showing findings linked to source records. — A small extension can combine useful evidence without a separate dashboard. This report was run against the fictional demo data. Select the image to view it full size.

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.

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_business_pulse; 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

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.

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.