Data & Storage · Integration
Google People API
Add Google People API to your product for your customers, and give your AI agents governed access to it.
Embed a Google People API integration when your product needs to look up people and read directory profiles across a customer's Google Workspace domain, rather than manage one user's personal address book. Each customer grants access to their own domain, so only profiles the connected account can see are returned, and reads are paginated and throttled for you. fastn handles per-domain authorisation, token refresh, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers resolve an email address to a person's directory profile inside your product.
Search a customer's domain directory so user pickers in your product show real people.
Read profile fields such as name, email, phone, and organisation to populate records without manual entry.
Refresh profile data on a schedule so your product does not drift from the customer's directory.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent resolves a name or email to a directory profile before routing a request.
An agent reads organisation details from a profile to work out who should approve something.
An agent searches the directory within governed permissions, with each query logged.
Example prompt
Look up these email addresses in the directory and tell me each person's department and job title.
Set up Google People API in 4 steps
- 01Open the Google People API connector from your fastn dashboard.
- 02Have each customer authorise their own Google Workspace domain with least-privilege scopes.
- 03Map the profile fields your product reads, then enable the lookup and search actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Google People API integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Google People API integration without building it. Your customers connect their own Google People API account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Google People API update is not your on-call problem.
- One integration serves your product and your agents. The same governed Google People API connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
Google Contacts
Okta
Microsoft Entra IDOften used alongside
Tools the same teams tend to run next to Google People API, across other categories.
Anthropic Claude
OpenAI
Hugging FaceGoogle People API integration FAQ
How do I add a Google People API integration to my product?
Enable the Google People API connector in your fastn dashboard, then let each customer authenticate their own Google People API account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Google People API client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Google People API account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Google People API account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Google People API integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent resolves a name or email to a directory profile before routing a request.
Who maintains the Google People API integration?
fastn does. When Google People API changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Google People API integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Google People API reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Google People API integration?
A common starting point: resolve an email address to a person's directory profile inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Google People API integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Google People API does not change your per-connector cost. You can start free with 3 connected accounts.
Add Google People API to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.