IonBin

Write a weekly pipeline forecast

Sales, CRM & outreach · Business data & reporting · checked 2026-10-16

A coding agent such as Codex or Cursor queries HubSpot deals through the MCP server, writes a forecast in Markdown, and saves it to Notion for the sales lead to review.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

Get a consistent weekly forecast without a spreadsheet ritual.

Connects through: MCP

Steps

#WhoWhat happensHowStatus
1HubSpot Returns open deals, stages and amounts
Reads deals and other CRM records the connected user can see.
 MCP Confirmed · source ↗
2Your coding agent Writes the forecast with risks and changes since last week AI platform Confirmed
3Notion Saves the forecast page MCP Confirmed · source ↗
4You The sales lead reviews and adjusts Human step Confirmed

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

Human approval

The sales lead owns the final forecast.

Watch out for

Keep the human approval step: The sales lead owns the final forecast.

Starter prompt

Goal: Get a consistent weekly forecast without a spreadsheet ritual. Tools involved: HubSpot, Notion. Your part: returns open deals, stages and amounts; writes the forecast with risks and changes since last week; saves the forecast page. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.

Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
HubSpot (free CRM)MCP hubspot.com ↗
NotionMCP notion.com ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs
OpenAI Codex To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs
Google Antigravity To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs
ChatGPT To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs
Gemini To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs
Perplexity To verify HubSpot: pairing not named in vendor docs; Notion: pairing not named in vendor docs

Computed from the MCP and API steps only: "Confirmed" needs the tool's docs to name the platform and the platform to support the connection. Browser, upload and human steps work from any platform.

What we checked

HubSpot’s remote MCP server reads deals, companies, contacts and activities, and every action respects the connected user’s HubSpot permissions. It’s built on the CRM search API, which has no vector search, so ask for filters (stage, close date, owner) rather than fuzzy matches. Notion MCP saves the forecast as a page in any workspace you can access. The sales lead owns the final numbers.

Set it up

  1. Connect HubSpot’s remote MCP server as a user who can see the whole pipeline, and Notion MCP for the output page.
  2. Write the forecast rules down once: which stages count as commit, best case and pipeline, and how to treat deals past their close date.
  3. Ask the agent to compare this week with last week’s Notion page and list what changed.
  4. The sales lead reviews and adjusts the numbers before sharing.

Every MCP action respects the connected user’s HubSpot permissions, so deals that user can’t see won’t be counted.

Sources

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.