Recipes / Weekly pipeline digest to Slack

Weekly pipeline digest to Slack

HubSpot + Slack

Who it's for

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

What you get

Monday digest posted to #pipeline. Sample output: every company and person in it is 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

Time and cost

Estimate About 5 minutes once it's set up.

Assumptions: One weekly run over about 40 open deals.

• HubSpot: Reads only. Credit use not confirmed by HubSpot.
• Slack: One message posted. Credit use not confirmed by Slack.

Exact credit costs depend on your plan with each vendor. Check the tool pages before a large run.

MCP servers

Every server is confirmed in: Claude

• HubSpot Up · auth
  ClaudeChatGPTRead + writeCredits not confirmed
  https://mcp.hubspot.com
• Slack Up · auth
  ClaudeClaude CodeCursorRead + writeCredits not confirmed
  https://mcp.slack.com/mcp

Set up in a chat app

Every server in this recipe is confirmed for Claude. Connect each one, then paste the prompts below into one conversation.

• Connect HubSpot without code (Claude, ChatGPT)
• Connect Slack without code (Claude)

Developer setup

{
  "mcpServers": {
    "hubspot": {
      "url": "https://mcp.hubspot.com"
    },
    "slack": {
      "url": "https://mcp.slack.com/mcp"
    }
  }
}

Step-by-step prompts

Copy all prompts

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.

Run it on a schedule (optional)

• This one is meant to run weekly, for example Monday at 7am before the pipeline meeting.
• For an unattended weekly run, decide up front whether the Slack post may go out without approval. If not, post it as a draft or send it to yourself first.
• Save each week's numbers somewhere the next run can read (a pinned message, a doc or a file), so week-over-week changes are real.
• Both HubSpot and Slack use OAuth. Test one manual run, then confirm the scheduled run still has valid tokens.

Where this goes wrong

• 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.

Gotchas

• Keep HubSpot strictly read-only here. The only write is the Slack post.
• Slack's MCP server uses confidential OAuth with a registered Slack app, so a workspace admin may need to approve it.
• For a scheduled run, both OAuth tokens need to work headless. Test one manual run first.
• The first run has no previous snapshot, so it shouldn't report fake changes.

Download

Get the prompts, guardrails and expected output as one Markdown file. Paste it into a Claude Project or ChatGPT project's instructions, or save it as CLAUDE.md for Claude Code.

Download weekly-pipeline-digest-slack.md

Vendor sites: HubSpot · Slack. If we join an affiliate program, these links will be labeled as affiliate links.