Docs/Lanes Link/Providers/Google Contacts

Google Contacts

Connect Google Contacts to your agents with Lanes Link. Look up an address, so 'email Bob' resolves. Read-only.

Look up a saved contact by name to find their address or phone number, including the addresses Gmail saved automatically. Read-only, via the People REST API.

Connect it

console
$ lanes link connect contacts --profile personal --workspace local

A browser opens and you approve. The OAuth client is operated by Lanes, so no client secret of theirs is stored on your machine. Pass --own-client to use an application you registered yourself instead, which the Google guide walks through.

What your agent can do

Capabilities are generated from an OpenAPI document vendored into Lanes Link, so the surface is reviewable in a diff and a change upstream cannot widen what your agents can reach without a commit here.

The scopes it asks for

Each provider asks for the narrowest set that makes its capabilities work, because a scope on a consent screen that no tool can spend is a grant asked for and never noticed.

ScopeWhat it allows
https://www.googleapis.com/auth/contacts.readonlyread your saved contacts
https://www.googleapis.com/auth/contacts.other.readonlyread the addresses Gmail saved automatically in "Other contacts"

How to narrow or widen any of this is on Scopes and permissions.

What is recorded

Every call is recorded, allowed or refused. The rule is to keep the shape and withhold the words: an audit log that reproduced the content would be a second copy of the thing it was meant to make accountable.

Identifiers such as pageSize, readMask, resourceNames, and personFields are kept. Everything that carries your words is withheld.

What an entry holds and how to read one is on the audit log.

Narrowing what it may do

Connecting grants the read bundle. Tightening it happens on your machine and takes effect at once:

console
$ lanes link policy deny 'contacts.*' --connection contacts.main --profile personal --workspace local

A deny always beats an allow, whatever the order in the file. See Scopes and permissions for widening, and for what can and cannot be set per connection.


Next: every provider, or Connections for what a connection is and the methods behind one.