The short answer

To automate a sales pipeline report, record yourself building it once from your CRM: stage movement, slipped deals, coverage ratio and weighted pipeline. Export the workflow to Make, n8n or Claude and schedule it before your pipeline review, so the numbers are ready without anyone touching the CRM.

A pipeline report answers the same questions for sales leadership every week: how much is in each stage, which deals slipped, is there enough coverage to hit quota. The questions never change, the CRM is the single source, and the pull is identical each time — a textbook automation candidate.

The metrics a pipeline report needs

The steps

1. Build the report once — recorded

Open the CRM, apply your pipeline view and date filters, export or read the figures, compute the deltas and coverage, and write the summary — with a recorder running.

2. Reconstruct the workflow

The recording becomes the steps: the CRM pull, the week-over-week comparison, the slipped-deal flag, the post. Confirm the filters and thresholds.

3. Export and schedule

Export to Make or n8n to query the CRM via API, or Claude for the narrative call-outs ("three enterprise deals slipped — here's why"). Schedule it for the morning of your pipeline review.

If your pipeline review starts with ten minutes of exporting CRM data, you've found the part to automate. The meeting should start with the discussion, not the gathering.

Worked example: the Monday pipeline review

Pull open deals from HubSpot or Salesforce, compare close dates to last week to flag slippage, divide pipeline by quota for coverage, and post a digest to the sales channel tagging deal owners. Recorded once, it runs itself at 8am Monday. More in sales use cases, and pair it with the forecast report.

How Spion does it

Record the pipeline report once; Spion reconstructs it and exports a ready-to-run automation to Claude, Make, Zapier or n8n. See how to automate your weekly report for the general pattern.