Googlecontacts
for LuumenAI

Read, search, and maintain Google Contacts records and groups from the terminal

Connect Google Contacts and Luumen can look up the people behind an escalation without leaving the terminal. Search contacts and the domain directory, pull group membership, check what details are on record. Changes — new contacts, edits, group membership, deletions — are previewed and held for your approval before anything is written. Access uses OAuth2.

The Googlecontacts toolbox

24 tools: 11 read, 13 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadBatch get contact groupsGet a list of contact groups owned by the authenticated user by specifying a list of contact group resource names.
  • ReadBatch get peopleBatch retrieves information about multiple people from Google Contacts.
  • ReadGet Contact GroupRetrieves a specific contact group owned by the authenticated user by specifying the contact group resource name.
  • ReadGet PersonProvides information about a person by specifying a resource name.
  • ReadList ConnectionsLists the connections (contacts) for the authenticated user.
  • ReadList Contact GroupsList all contact groups owned by the authenticated user.
  • ReadList Directory PeopleLists domain profiles and domain contacts in the authenticated user's domain directory.
  • ReadList Other ContactsLists "Other contacts" from Google People API.
  • ReadSearch ContactsSearches the authenticated user's contacts for matches against the provided query.
  • ReadSearch Domain Directory PeopleSearch domain directory people in Google Contacts.
  • ReadSearch Other ContactsSearches other contacts from Google People API that match a query string.
  • WriteBatch create contactsCreate a batch of new contacts in Google Contacts. Approval by default
  • WriteBatch Update Google ContactsUpdate a batch of contacts in Google Contacts and return the updated contact data. Approval by default
  • WriteCopy Other Contact to My ContactsCopies an Other contact to a new contact in the user's myContacts group. Approval by default
  • WriteCreate ContactCreate a new contact in Google Contacts and return the person resource for that contact. Approval by default
  • WriteCreate Contact GroupCreate a new contact group owned by the authenticated user. Approval by default
  • WriteDelete Google ContactDelete a contact person from Google Contacts. Approval by default
  • WriteDelete contact groupDeletes an existing contact group owned by the authenticated user by specifying the contact group resource name. Approval by default
  • WriteDelete Contact PhotoDelete a contact's photo from Google Contacts. Approval by default
  • WriteBatch Delete Google ContactsDelete a batch of contacts from Google Contacts. Approval by default
  • WriteModify Contact Group MembersModifies the members of a contact group by adding or removing contact resource names. Approval by default
  • WriteUpdate Google ContactUpdate contact data for an existing contact person. Approval by default
  • WriteUpdate Contact GroupUpdate the name of an existing contact group owned by the authenticated user. Approval by default
  • WriteUpdate Contact PhotoUpdate a contact's photo. Approval by default

One prompt, start to finish

What a governed Googlecontacts run looks like inside Luumen.

Questions

How does LuumenAI connect to Googlecontacts?

Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Googlecontacts on its own?

Read actions answer immediately. Anything that writes — batch create contacts, batch update google contacts, copy other contact to my contacts, create contact, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Googlecontacts — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Googlecontacts to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.