Use the management helper to retrieve people without opening the dashboard. You need people:read on BARUA_MANAGEMENT_KEY and the installed skill.
List people
node "$BARUA_SKILL/scripts/manage.mjs" people --limit 20
Success returns a bounded page of people and next_cursor when another page exists. Continue with --cursor; the helper does not fetch every page automatically. The maximum page size is 100.
Find one person
For exact email or external-ID lookup, use people-search --input-file with private JSON. Specify exactly one of email or external_id. Keep customer identifiers out of command history; the people contract gives the input schema.
Use a returned person UUID for detail:
node "$BARUA_SKILL/scripts/manage.mjs" person --id "$PERSON_ID"
The response separates facts from the profile data and suppression state. A section with state: "unavailable" is not empty data. If any section is unavailable, complete is false. Never infer permission to send from missing suppression data.
Inspect activity
Use person-activity for the activity timeline, with the same --id. Use person-events with both --id and a returned --session-id to read one pixel session's events. Follow each response's continuation cursor. The HTTP contract defines the projections and pagination.
For a rendered profile preview, use inspect.mjs profile-preview with a private input file as described in the inspection reference. Keep downloaded customer data private.
Next step
Segments and campaigns covers targeting these people. Read emails and previews explains the additional permission needed to see email content. If a section is unavailable, report the partial result and check workspace diagnostics.