Read-only.
When to use it
- “Which accounts have come to three or more of our events?”
- “Who keeps registering but never checks in?”
- “Has Beacon Hill been to every open house this year?”
- “Include our partners’ own staff this time.”
Parameters
Archived and demo collabs are excluded; a restored collab’s events return.
Response
data is one row per account, ordered by event count, then most recent.
attendee_count counts SIGN-UPS. checked_in_count counts sign-ups with a check-in record. It is null, not 0, for an event not yet held, an event whose source did not record check-in, or a Luma event never synced with check-in-aware ingest; a partial_coverage gap names which.
A real response from the ScaleUp.ai fixtures with limit: 3, trimmed to one row and the relevant gaps:
Rules the agent must follow
- Never report
attendee_countas attendance. Only checked-in sign-ups attended. - A null
checked_in_countis unknown, never zero. - When a
scope_truncatedgap is present, more accounts match; say so and narrow.result_countalone cannot tell you, because partner accounts are excluded after the limit applies. - Nothing here is a score or a rank. Order is by event count and recency only.
- For owners and open deals, use the user’s own CRM connector, joined on
domain.
Errors and gaps
Related
- get_account_relationship: one account in depth.
- get_event_details: one event’s roster.
- get_partner_overlaps: accounts shared with partners.
- Playbook: Invite sprint.