Skip to main content
Read-only.
The marketer’s question is “what did this partner actually drive?” This is the one tool for partner-level revenue. Reach for it for a partner rollup across events; for one event’s view use get_event_attribution. Both read the same canonical resolver, so their partner figures reconcile. Follows the heyBTW MCP rules.

When to use it

  • “How much pipeline did Brightpath drive this quarter?”
  • “Which partners brought senior people, not just sign-ups?”
  • “What’s our account coverage with Ferrocity?”
  • “Prep the partner QBR numbers.”

Parameters

Response

crm_context comes first (capability deal_read). Then one row per identity-resolved partner, ordered by sourced revenue descending, then total sourced, then partner name; an unknown value sorts last (metadata.ordering). In pipeline_impact, null means unavailable and 0 means measured, none. account_overlap is null when the query is cross-workspace, when the partner spans more than one collab in this workspace, or when the coverage lookup failed soft. None of those means “no data”.
influenced_new_revenue and influenced_expansion_revenue come from the dashboard’s Influence Breakdown panel (“Partner Influenced (New)” and “Partner Influenced (Expansion)”). That taxonomy is independent of Sourced and Influenced: the two classifiers disagree deal by deal. Never present these dollars as a slice of influenced_revenue, never expect them to sum to it, and never add them to the headline. The panel’s other buckets (Direct, Direct Influenced, Partner Sourced) are not served here; say the split is unavailable. The mapping is in agent_guidance.dashboard_vocabulary on get_workspace_overview.
A real response from the ScaleUp.ai fixtures, trimmed to one of four partners:
pipeline_impact.crm_enriched is also emitted; it is deprecated and will be removed on 2026-11-16. Read crm_joined.

Rules the agent must follow

  • Partner revenue comes from this tool only. Never compute a partner figure yourself.
  • Say a revenue figure is heyBTW’s only when pipeline_impact.crm_joined is true.
  • Null is unknown, never zero. A null reasons or account_overlap is withheld, not empty.
  • No rank or engagement composite is served. Ordering is by sourced revenue only.
  • Quote dashboard words from dashboard_vocabulary so the user can find the figure on screen.

Errors and gaps