Lists

A List is a saved, filtered group drawn from the contacts and accounts already in your workspace. One object serves both halves of an event: who to invite before it, and who to follow up with after it. Find Lists in the left sidebar under Lists.

​

Dynamic vs. static

Every list is one or the other, and you choose at creation.

• Dynamic. The list is a saved set of filters, re-evaluated live. As new RSVPs arrive and CRM records change, membership changes with them. Nothing is frozen at save.
• Static. The list captures a fixed selection at the moment you save it. Membership does not change on its own.

Use dynamic for anything that should stay current, like “approved attendees with an open opportunity.” Use static when you need a stable set, like the exact group you sent an invite to. The Lists page shows the split at a glance, for example 13 lists, 7 dynamic, with All, Dynamic, and Static tabs above the grid.

​

Creating a dynamic list

Click + New list.

​

List name

Name it after the predicate, not the occasion. Approved · 2+ events tells you what’s inside six weeks from now. Dinner list does not.

​

Basis

Basis scopes where matches are drawn from.

• All workspace data. Matches are drawn from every collab in this workspace.
• A single collab. Pick one event from the searchable list to scope the list to its attendees.

Basis is the difference between a follow-up list for one event and a list built across your whole event history. Cross-event lists are how you find the people who keep showing up, which is usually the strongest signal you have. The basis appears on the list card afterward as a Basis: chip.

​

Filters

Add filters with + Add filter. All filters must match (AND), so each filter you add narrows the result. Account and CRM Event signals An incomplete filter blocks the save with a message naming it, for example Complete or remove the CRM status filter to continue. Click Create list.

​

Reading a list card

Each card on the Lists page carries:

• Name and size, counted in accounts or contacts depending on the list.
• Dynamic or Static.
• Draft while the list is still being worked on.
• Source, showing where the list came from: Agent, ABM, Partner list, Partner Ecosystem, or manual.
• Basis, the collab it was scoped to, if any.
• Filter chips summarizing the predicate, for example Attended ≥ 1 event, Has company, RSVP Approved.
• Updated date.

Narrow the grid with the All sources and All collabs dropdowns, re-order with the sort control, or search by name.

​

Where lists come from

You do not have to build every list by hand. Lists arrive from four places and all of them produce the same object:

• Lists page. Built directly, as above.
• Agents. An agent proposes a list from your CRM and event history, and you review it before anything happens.
• Partner Ecosystem. Click Save as List on a partner’s account mapping view to turn the accounts you’re looking at into a reusable list.
• ABM and manual upload. Built from the account planning board, or uploaded.

​

The list detail page

Click any list to open it. The left side is the membership itself, with a count, a Last checked timestamp, and an Update button to re-evaluate on demand. The right side is the list’s paperwork.

• Definition. What the list actually is. A static list reads as a snapshot with the date it was saved and a note that it does not change. A dynamic list shows the filters it re-evaluates against.
• Linked to. Every surface this list is attached to, each with a date: the collab, any ABM boards, Invite Builder, and the agent run that produced it.
• Activity. What has been done with it, for example “Sent to attio, 5 sent, by ScaleUp Admin,” with the date and the person.
• Provenance. Where the members came from and who created the list.

Provenance and Activity are the reason a list is safe to reuse months later. You can tell whether an agent built it or a person did, and whether it has already been sent somewhere, before you send it again. The Live toggle in the header controls whether the list keeps updating. Export CSV and Archive sit alongside it.

​

Activating a list

Activate is where a list stops being a saved query and does something. The dialog names the action and the target, for example Activate “neo4j test upload invites” to neo4j test upload, and splits the options in two.

​

Use in heyBTW

These open the list inside another surface. The list stays live, so it keeps updating while you work it.

• Invite Builder. Work the list as an invite plan.
• ABM. Load it onto the account planning board for the linked collab.
• Partner Ecosystem. Work it against a partner’s account mapping. This one opens from the required workspace context rather than from the dialog.

​

Send externally

• Send Luma invites. Beta. heyBTW calls the Luma API and Luma sends the invitation. Each recipient RSVPs themselves, so nobody lands on your guest list without acting. Luma is the sender of record, which means the invitation carries your event’s branding and lives in the recipient’s Luma history like any other invite.
• Add to an Attio list. Delivers the members into an Attio list so your own sequences can enroll from it. This is a handoff, not an outreach act, and the sender of record stays your mailbox.
• Download as CSV. For anywhere else.

Each option shows how many members it would act on, and a receipt once it has run, for example “Sent 5 to attio, Jul 2.” That receipt is what stops the same list being sent twice by two different people. HubSpot, Outreach, Apollo, and Splash are listed in the dialog as destinations still to come.

​

Follow-up segmentation

After an event, the same object becomes your follow-up routing. Build these as dynamic lists with a single-collab basis and they stay correct as CRM data moves:

• Attended and has an open opportunity. The acceleration list. Route to the account owner.
• Attended and net-new. The sourced list. Route to whoever works new logos.
• Registered but did not attend. The re-invite pool for the next event.
• Partner-sourced attendees. The co-sell list.

​

Related

• Event Platforms: connect Luma so a list has somewhere to send
• Partner Ecosystem Dashboard: account mapping and Coverage
• Event Attribution Funnel: what happened to the people you invited