people (v1)

Google Contacts and profiles management via the People API.

- Manage contact groups with create, update, delete, and batch operations; contact group names must be unique per user

- Create, update, and batch-manage individual contacts with support for photos, metadata, and field-level control via update_mask

- Search contacts across grouped contacts, other contacts, and domain directory with warmup request requirement for cache optimization

- List and sync contacts incrementally using sync tokens (7-day expiration) and page tokens; domain directory listing includes deleted contact tracking

- Requires gws binary and Google Workspace authentication; use gws schema to inspect method parameters before execution

people (v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws people <resource> <method> [flags]

API Resources

contactGroups

- batchGet - Get a list of contact groups owned by the authenticated user by specifying a list of contact group resource names.

- create - Create a new contact group owned by the authenticated user. Created contact group names must be unique to the users contact groups. Attempting to create a group with a duplicate name will return a HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.

- delete - Delete an existing contact group owned by the authenticated user by specifying a contact group resource name. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.

- get - Get a specific contact group owned by the authenticated user by specifying a contact group resource name.

- list - List all contact groups owned by the authenticated user. Members of the contact groups are not populated.

- update - Update the name of an existing contact group owned by the authenticated user. Updated contact group names must be unique to the users contact groups. Attempting to create a group with a duplicate name will return a HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.

- members - Operations on the 'members' resource