Pipeline follow-up

A promising opportunity can go quiet while everyone assumes someone else is following up. Pipeline follow-up helps a sales owner find the records that deserve a closer look.

Try the report

Enable Pipeline follow-up in Plugins, then choose Run report. It reads the workspace’s opportunity records without requiring another provider connection. The plugin starts disabled. Use an authorized workspace, or explore Plugins in the fictional demo.

Give a fictional open deal a next action in the past. Run the report and open the linked opportunity to inspect its history before deciding whether to contact the customer.

Open opportunities qualify when their next action is overdue or their last update is older than seven days. The report describes the inspected records, not the probability of winning a deal.

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_pipeline_watch, 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

Build a focused exception report over canonical business records. Change the rules for a different review process without introducing a second CRM or asking a model to calculate dates.

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.