Read-only.
When to use it
- “Which of our targets does Brightpath also work with?”
- “Show me accounts shared by two or more partners.”
- “Which declared targets does no partner touch?”
- “Run the warm-intros play for the open house.”
Parameters
All optional.Response
data[0] (note the camelCase keys, served as written):
setCounts reflects the full matched set before min_confidence, partner_role and my_role narrow the returned rows. my_role narrows after the page is read, so a page can hold fewer rows than returned: follow next_cursor until has_more is false.
Plays
A real response from the heyBTW workspace scoped to the SF open house fixture, trimmed to two plays. The fixture partners have no managed or attributed account evidence yet, so no rows come back while 251 declared targets are uncovered:
Rules the agent must follow
partner_count, exclusivity andin_targetare set facts. Nothing is ranked or rated: apply the user’s own CRM and ICP to prioritize.my_roleis maintained in heyBTW from Lists (provenancemanual), not CRM-verified. Cross-check in the user’s CRM where it matters.- Join on
company_domain(lowercase, without www) against the user’s CRM. - Follow
next_cursoruntilhas_moreis false before stating a total from rows. - A failed read is always an error, never an empty set. An empty
rowswithstatus: "ok"is a real answer.
Errors and gaps
Related
- get_account_relationship: one account in depth.
- get_partner_insights: one partner’s rollup.
- get_abm_plan: the collab’s target accounts and who covers them.
- Playbook: Invite sprint.