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.

MCP servers

HubSpot Up · auth
https://mcp.hubspot.com
OAuth 2.1 with PKCE (MCP connector)
Slack Up · auth
https://mcp.slack.com/mcp
Confidential OAuth (registered Slack app)

Auth setup

HubSpot: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.
Slack: Sign in with OAuth in your client (run /mcp in Claude Code). Do it once interactively, and the client stores and refreshes the token.

mcp.json config for Claude Code and Cursor

Put this in .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Swap the example keys for your own, and don't commit real ones. Remove the // comment lines if your client requires strict JSON.

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

Step-by-step prompts

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

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.

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