Read-only.
This page documents the v1 response, the one served by default. The tool is evolving and this page will be revised.
When to use it
- “What’s our history with Beacon Hill Software?”
- “Who from Beacon Hill has come to our events, and did they check in?”
- “Is there a partner who can intro us to them?”
- “Before my call, how engaged is this account?”
Parameters
Archived and demo collabs are excluded, as in list_events; a restored collab’s records return.
Response
data[0]:
Contact
source is event_attendance (on an event roster) or crm_deal_contact (named on an attributed CRM deal without attending; email, title and funnel_status are null, never fabricated). attendance_status keeps the layers apart: APPROVED is registered, only CHECKED_IN is attended.
A real response for a ScaleUp.ai fixture account, trimmed to two events, two contacts and one coverage note:
Rules the agent must follow
attendee_countcounts sign-ups, never attendance. Only CHECKED_IN is attended.- A null
partner_sourcedoes not mean no partner brought the contact. Relay the coverage note as written. - When more history exists than
limitreads, warm pathreasonsandrecommended_actionsare null (unknown, not empty) and ascope_truncatedgap names the lever. - For owners, open deals and activity, use the user’s own CRM connector first, joined on
company_domain. Saypipelineis heyBTW’s only whencrm_joinedis true. - Never weight or rank contacts. Serve the facts with their basis.
Errors and gaps
No cursor is emitted: narrow the query rather than paging.
Related
- get_cross_event_patterns: patterns across many accounts.
- get_partner_overlaps: which partners share this account.
- get_event_attribution: event-level revenue.
- Playbook: What each system knows.