Skip to content

Try “workflows”, “templates”, “SOQL” or “create a record”.

Lists

Dynamic lists that update themselves and frozen snapshots — for broadcasts, follow-ups and reports.

A list is a saved set of records from one object. Lists are how you say "these people" once and reuse it — as a broadcast audience, a call sheet or a segment to report on. Find them under Inbox → Lists.

Dynamic and frozen lists#

KindHow it behavesExample
DynamicA live query. Every time you use it, it re-runs and returns whoever matches now.Health policies expiring in 30 days, Active SIP investors, Leads from digital marketing
FrozenA snapshot. It keeps the members it had when you froze it.Diwali greetings 2026 (40 people), Claims Saathi clients (24 people)

Use a dynamic list when the audience should change as your data changes — renewals coming up, investors who are active this month. Use a frozen list when you need a fixed record of exactly who received something, such as a festival greeting you don't want to send twice.

The lists table shows each list's object, type, member count and when it last updated.

Lists in practice#

  • Broadcasts. Every broadcast goes to a list. A dynamic Motor renewals due list means next month's reminder reaches next month's customers without anyone rebuilding it.
  • Call sheets. Share a list with a telecalling team, or feed it into a flow.
  • Reporting. Count, chart and compare segments over time.

Through the API#

Lists live under /docs/api/lists. Create one with a name, the object it draws from, a mode — dynamic or static (the console calls static lists frozen) — and, for dynamic lists, the query that defines it:

http
POST /api/v1/lists
json
{  "name": "Leads from digital marketing",  "object": "lead",  "mode": "dynamic",  "queryText": "SELECT Id FROM lead WHERE lead_source = 'Digital Marketing'"}

Then:

  • GET /lists/{id}/records returns the members, paged with limit and cursor;
  • POST /lists/{id}/refresh re-evaluates a dynamic list;
  • POST /lists/{id}/freeze snapshots its current members.

Reading lists needs objects:view; creating, refreshing and freezing need objects:use.