# Googlecontacts AI integration on Definable > Access and manage Google Contacts data via the Google People API ## What this connects Access and manage Google Contacts data via the Google People API Vendor: https://contacts.google.com ## Tools available **24** tools available. First 12: - `GOOGLECONTACTS_BATCH_CREATE_CONTACTS` — Batch create contacts — Create a batch of new contacts in Google Contacts. This action creates up to 200 contacts in a single API call and returns the PersonResponses for the newly created contacts. Use this action when you need to create multiple contacts at once to reduce API calls and improve performance. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. Note: The contacts array accepts Person objects with any valid People API fields (names, emailAddresses, phoneNumbers, addresses, organizations, etc.). Each contact must be wrapped in a 'contactPerson' object. - `GOOGLECONTACTS_BATCH_GET_CONTACT_GROUPS` — Batch get contact groups — Get a list of contact groups owned by the authenticated user by specifying a list of contact group resource names. Use when you need to retrieve details for specific contact groups, such as getting group metadata, member counts, or group names for multiple groups in a single API call. - `GOOGLECONTACTS_BATCH_UPDATE_CONTACTS` — Batch Update Google Contacts — Update a batch of contacts in Google Contacts and return the updated contact data. Use this action when you need to modify multiple contacts at once, such as: - Updating names, phone numbers, or email addresses for several contacts - Making bulk changes to contact information - Syncing contact data from another source This action allows updating up to 200 contacts per request. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_COPY_OTHER_CONTACT_TO_MY_CONTACTS` — Copy Other Contact to My Contacts — Copies an Other contact to a new contact in the user's myContacts group. Use this action when you need to save an existing "Other contact" (from Google's contact suggestions) to your permanent contacts in the myContacts group. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_CREATE_CONTACT` — Create Contact — Create a new contact in Google Contacts and return the person resource for that contact. Use when you need to add a new person to the authenticated user's Google Contacts. The request returns a 400 error if more than one field is specified on a field that is a singleton for contact sources: biographies, birthdays, genders, or names. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. This action creates a single contact; for bulk creation of multiple contacts, use GOOGLECONTACTS_BATCH_CREATE_CONTACTS instead. Note: Only the primary entry for singleton fields (biographies, birthdays, genders, names) will be saved for contact sources. - `GOOGLECONTACTS_CREATE_CONTACT_GROUP` — Create Contact Group — Create a new contact group owned by the authenticated user. The group name must be unique among the user's contact groups. Use this action when you need to create a new contact group to organize the user's Google Contacts. Attempting to create a group with a duplicate name will return an HTTP 409 error. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_DELETE_CONTACT` — Delete Google Contact — Delete a contact person from Google Contacts. Any non-contact data will not be deleted. Use this action when you need to permanently remove a contact from the user's Google Contacts list. This action is irreversible — the contact cannot be recovered once deleted. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_DELETE_CONTACT_GROUP` — Delete contact group — Deletes an existing contact group owned by the authenticated user by specifying the contact group resource name. This action is irreversible — once deleted, the contact group cannot be recovered. Use this action when you need to remove a contact group that is no longer needed. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_DELETE_CONTACT_PHOTO` — Delete Contact Photo — Delete a contact's photo from Google Contacts. Use when you need to remove a profile picture from a specific contact. This action is irreversible — once the photo is deleted, it cannot be recovered. Mutate requests for the same user should be sent sequentially to avoid lock contention and failures. - `GOOGLECONTACTS_DELETE_CONTACTS_BATCH` — Batch Delete Google Contacts — Delete a batch of contacts from Google Contacts. Any non-contact data will not be deleted. Use this action when you need to permanently remove multiple contacts from the user's Google Contacts list at once. This action is irreversible — the contacts cannot be recovered once deleted. Mutate requests for the same user should be sent sequentially to avoid increased latency and failures. - `GOOGLECONTACTS_GET_BATCH_PEOPLE` — Batch get people — Batch retrieves information about multiple people from Google Contacts. Use this action when you need to fetch contact information for several people in a single API call rather than making individual requests per person. This improves efficiency when you need data from multiple contacts at once. Note: The personFields parameter is required and determines which contact information fields are returned in the response. If a person cannot be found, the corresponding response will contain a status but no person data. - `GOOGLECONTACTS_GET_CONTACT_GROUP` — Get Contact Group — Retrieves a specific contact group owned by the authenticated user by specifying the contact group resource name. Use when you need to get details about a specific contact group, including its name, member count, and metadata. This is a read-only operation that fetches an existing contact group when you already know its resource name. ## Auth Auth schemes: `OAUTH2`. ## How agents use Googlecontacts Inside a Definable workflow, Googlecontacts is one of the tools the **Distributor specialist** can call. Example coordination patterns: - **Researcher → Googlecontacts** — the Researcher (GPT-5.5) pulls context from Googlecontacts (records, threads, documents), synthesises findings, and briefs the rest of the team. - **Writer → Distributor → Googlecontacts** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Googlecontacts (create record, post message, draft email). - **Designer / Engineer → Distributor → Googlecontacts** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Googlecontacts (attach file, open PR comment, post status). The Verifier checks every Googlecontacts call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention. ## Categories - productivity — https://definable.ai/apps/category/productivity/ - crm — https://definable.ai/apps/category/crm/ ## Related - HTML page: https://definable.ai/apps/googlecontacts/ - Same category (productivity): https://definable.ai/apps/category/productivity/ - All integrations: https://definable.ai/apps/ - Workflow (multi-agent loop): https://definable.ai/workflow/ - Apps llms.txt index: https://definable.ai/llms-apps.txt