Googlecontacts integration: operations for AI agents
Googlecontacts connects to Type.com as an integration. This page lists the 24 operations documented for Claude and Codex in Type.com: 11 read, 9 write, 4 destructive.
About Googlecontacts
Access and manage Google Contacts data via the Google People API
Categories: Productivity & Project Management
How to connect Googlecontacts to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
24 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
24 operations listed.
People
- Read
List Directory People people
Provides a list of domain profiles and domain contacts in the authenticated user's domain directory. When the synctoken is specified, resources deleted since the last sync will be returned as a person with PersonMetadata.deleted set to true.
- Read
Get people
Provides information about a person by specifying a resource name. Use people/me to indicate the authenticated user. The request returns a 400 error if 'personFields' is not specified.
- Read
Search Directory People people
Provides a list of domain profiles and domain contacts in the authenticated user's domain directory that match the search query.
- Read
Get Batch Get people
Provides information about a list of specific people by specifying a list of requested resource names. Use people/me to indicate the authenticated user. The request returns a 400 error if 'personFields' is not specified.
- Read
Search Contacts people
Provides a list of contacts in the authenticated user's grouped contacts that matches the search query. The query matches on a contact's names, nickNames, emailAddresses, phoneNumbers, and organizations fields that are from the CONTACT source.
- Write
Create Contact people
Create a new contact and return the person resource for that contact.
- Write
Batch Delete Contacts people
Delete a batch of contacts. Any non-contact data will not be deleted. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
- Write
Update Contact people
Update contact data for an existing contact person. Any non-contact data will not be modified. Any non-contact data in the person to update will be ignored. All fields specified in the updatemask will be replaced.
- Write
Batch Update Contacts people
Update a batch of contacts and return a map of resource names to PersonResponses for the updated contacts. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
- Write
Update Contact Photo people
Update a contact's photo. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
- Write
Batch Create Contacts people
Create a batch of new contacts and return the PersonResponses for the newly Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
- Destructive
Delete Contact Photo people
Delete a contact's photo. Mutate requests for the same user should be done sequentially to avoid // lock contention.
- Destructive
Delete Contact people
Delete a contact person. Any non-contact data will not be deleted. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
People connections
- Read
List connections
Provides a list of the authenticated user's contacts. Sync tokens expire 7 days after the full sync. A request with an expired sync token will get an error with an google.rpc.ErrorInfo with reason "EXPIREDSYNCTOKEN".
Other Contacts
- Read
List other Contacts
List all "Other contacts", that is contacts that are not in a contact group. "Other contacts" are typically auto created contacts from interactions. Sync tokens expire 7 days after the full sync.
- Read
Search other Contacts
Provides a list of contacts in the authenticated user's other contacts that matches the search query. The query matches on a contact's names, emailAddresses, and phoneNumbers fields that are from the OTHERCONTACT source.
- Write
Copy Other Contact To My Contacts Group other Contacts
Copies an "Other contact" to a new contact in the user's "myContacts" group Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
Contact Groups
- Read
Batch Get contact Groups
Get a list of contact groups owned by the authenticated user by specifying a list of contact group resource names.
- Read
Get contact Groups
Get a specific contact group owned by the authenticated user by specifying a contact group resource name.
- Read
List contact Groups
List all contact groups owned by the authenticated user. Members of the contact groups are not populated.
- Write
Create contact Groups
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.
- Destructive
Delete contact Groups
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.
- Destructive
Update contact Groups
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.
Contact Groups members
- Write
Modify members
Modify the members of a contact group owned by the authenticated user. The only system contact groups that can have members added are contactGroups/myContacts and contactGroups/starred. Other system contact groups are deprecated and can only have contacts removed.
No operations match.
See How connections work for access and permissions, or browse all integrations.