# Weekly pipeline digest to Slack

Source: https://mcpforgtm.com/recipes/weekly-pipeline-digest-slack (StackMCP, independent directory of official MCP servers)

## Goal

Sales leaders and RevOps who want the Monday pipeline facts posted to Slack before the review meeting.

## Connected tools

- HubSpot: https://mcp.hubspot.com (setup: https://mcpforgtm.com/tools/hubspot)
- Slack: https://mcp.slack.com/mcp (setup: https://mcpforgtm.com/tools/slack)

## Guardrails

- Read only in HubSpot. The only write is one Slack message to the channel I name.
- If there's no previous snapshot, say this is the baseline and don't report changes.
- Don't include contact names or email addresses in the post.

## Steps

1. Read all open HubSpot deals with stage, amount, close date, owner and last activity date.
2. Group them by stage with counts and totals. Flag deals with no activity in 14+ days and deals closing in the next 30 days.
3. Compare to last week's snapshot if you have one. If you don't, say this is the baseline and don't invent changes.
4. Draft a short summary for #pipeline in Slack, with one line per deal that needs a decision this week. Post it after I approve it.

## Expected output

Monday digest posted to #pipeline. Example (all names fictional):

```
Pipeline digest, week of Oct 13 (baseline week: no comparison yet)

Open: 38 deals, $1.42M
- Discovery: 14 ($310K)
- Proposal: 11 ($520K)
- Negotiation: 9 ($470K)
- Contract sent: 4 ($120K)

Needs a decision this week:
- Quarry Lane Analytics (fictional), $48K, closes Oct 31, no activity in 16 days (owner: Alex)
- Fernhill Software (fictional), $22K, close date passed Oct 10 (owner: Jordan)

Closing in the next 30 days: 7 deals, $265K
```

## Watch for

- Made-up week-over-week changes: Without last week's snapshot, the model may invent trends. The first run must say 'baseline'. Store a snapshot each week.
- Missing or extra deals: The connected user only sees deals they have access to, and closed deals can sneak in. Check the total deal count against a HubSpot report once.
- Posting in the wrong place: Deal amounts and customer names can leak into a public channel. Name the exact channel and make sure it's private if it needs to be.