Skip to main content

What Weflow MCP Returns: Forecast, Pipeline and Call Data

What the Weflow MCP connector returns to Claude, ChatGPT and other AI assistants: forecast and pipeline numbers, call recordings and AI Playbook results.

The Weflow MCP connector gives an AI assistant such as Claude or ChatGPT read-only access to forecast and pipeline numbers, recordings with their summaries and transcripts, and AI Playbook results. It returns only what the connected user can see in Weflow.

Note: an admin turns the connector on in Admin Console > Weflow AI > MCP Connector and decides there whether assistants may read full transcripts.

Data

What comes back

Forecast

Pipeline, closed-won, targets per rep

Forecast calls

Latest submission and its gap

Recordings

Summaries, transcripts, meeting type

AI Playbooks

Playbook results per deal

Organisation

Your org structure

Forecast and pipeline data the Weflow MCP connector returns

The Get Forecast tool returns forecast data for a close-date period you choose, with a start and end date. You scope it to your own opportunities (me) or to your team hierarchy (team), and can ask for a per-rep breakdown of up to 25 owners.

For each rep in scope it returns:

Metric

Detail

Pipeline value

Weighted and unweighted

Closed-won

Amount and count

Closed and total opportunities

Counts, with opportunity IDs

Win rate

Per rep

Average deal size and contract value

Per rep

Sales cycle length

Average days

Coverage ratio

Pipeline against target

Gap to forecast

Pipeline distance from target

Weflow computes these numbers from your Weflow forecast configuration, not from a Salesforce report. The opportunity IDs come back with them, so an assistant can open the deals behind a number.

  • Forecast categories: the breakdown follows the categories your org uses, category buckets such as Pipeline, Best Case, Commit and Closed, or stage-based buckets.

  • Forecast calls: the most recently submitted forecast call for the period, the live pipeline total, and the delta between them. When nothing was submitted, the submission comes back empty.

  • Targets: where you configured quotas or targets in Weflow, they come back next to the actuals, including manager forecasts and manager targets.

Forecast calls, submissions and targets live in Weflow rather than in Salesforce objects, so no Salesforce connector can see them.

Call data the Weflow MCP connector returns

The List Recordings and Get Recording tools return the recordings you can access, with their AI summaries, transcripts and meeting type.

  • Conversation data such as tracker hits and coaching scores is part of what the connector serves.

  • Recordings of Conversation Intelligence Light users are included.

Allow transcript access decides how deep the connector reaches: On, connected assistants read full call transcripts; Off, they see the AI summaries only.

MCP Connector settings with Allow transcript access

AI Playbook data the Weflow MCP connector returns

The List Playbooks and Playbook Values tools return your AI Playbooks and their results on deals, the methodology scores that live in Weflow. An assistant can score an opportunity against your playbook and say what is missing.

What the Weflow MCP connector does not return

  • Salesforce fields and captured emails: emails captured by Activity Capture and values stored on Salesforce records live in Salesforce. An assistant reads them through a Salesforce connector, used alongside Weflow's.

  • Saved views: a deal board's filters, columns and grouping live only inside Weflow, so an assistant rebuilds the same slice from the records it reads.

  • Meeting preparation: Weflow generates its meeting preparation live, inside Weflow. With the connector attached, an assistant builds its own briefing from the recordings, summaries, playbook results and forecast data.

  • Changes to Weflow: the connector is read-only. Templates, prompts and settings are edited in the Admin Console.

Who sees what through the Weflow MCP connector

Each user connects their assistant with their own Weflow sign-in and approves read-only access to their recordings, forecast and playbook data.

The connector then returns only what that user can see in Weflow, following your Weflow hierarchy, whether it comes from Salesforce or from a custom Weflow hierarchy.

A rep cannot reach a manager's forecast calls through an assistant, because they cannot reach them in Weflow either.

Note: where no hierarchy is configured, the team scope of an admin's forecast request covers every active user in the company.

The Connected users table on the MCP Connector page shows every user who has connected an assistant, when they connected and when they last used it.

Frequently asked questions about Weflow MCP data

What questions can I ask with the Weflow MCP connector?

Questions such as: what did the champion say about budget on the last three calls with this account; score this opportunity against our playbook; how far is my team's pipeline from target this quarter; what changed between last week's forecast call and this one.

Do I still need a Salesforce connector?

Yes, for Salesforce fields and captured emails. The Weflow connector adds what Salesforce does not hold: forecast calls and targets, transcripts, tracker hits and AI Playbook results.

How much can an assistant read through the Weflow MCP connector?

There is no usage cap, only rate limits: 60 requests per minute for each user and 600 for each company.

Does reading Weflow data through MCP use agent actions?

No. Only agents run in Weflow's own Agent Builder use agent actions.

Did this answer your question?