jq or save the result as JSON. The dashboard channel-detail page shows the same people.
Synopsis
Arguments
| Argument | Type | Description |
|---|---|---|
<channelId> | integer | Channel ID. Use channel list to find one. |
Options
| Flag | Type | Description |
|---|---|---|
--keyword <keyword> | string | Free-text match against name, email, phone, company, and job title. |
--event-id <id> | integer (repeatable) | Limit to people also registered for the given event. Repeat to OR multiple. |
--company-id <id> | integer | Limit by company ID. |
--company-name <name> | string | Limit by company display name. |
--job-title <title> | string | Limit by job title. |
--page <n> | integer | Page number (zero-indexed). Defaults to 0. |
--page-size <n> | integer | Page size. Defaults to the server default. |
--sort <value> | string (repeatable) | Sort expression field,direction (for example, joinedAt,desc). Repeat for secondary sorts. |
Examples
1. Browse the latest people on a channel
7 as a table: ID, name, email, phone, company, job title, joined-at.
2. Filter by event and pipe to jq
7 who also registered for event 18, projected to three fields. The --json envelope also carries .pagination.
3. Walk every page in a script
Response
pagination appears only in --json. joinedAt for a channel is when the person was first attributed to it, not when they last engaged.
See also
channel get. Confirm channel metadata before paging.path person list. The workspace-wide people query with the same filter grammar.- Recipe: Channel analysis.
--event-idfiltering paired with attribution metrics. - Channels. The dashboard surface this command mirrors.
