ApivomApivom
Get Demo

Google Places API (New) Connector

Google's Places API (New) — text and nearby search, place details, autocomplete and photos — connected to Apivom Iris and Apivom Halo with your own Maps Platform key: link CRM companies to their Google place, let the assistant answer with live place data, and back-fill locations on a schedule.

What you can do

  • Text search, nearby search, place details, autocomplete and photo media — the full Places (New) surface, all read-only
  • Iris links a company to its Google place from suggestions you confirm; Apivom Staff pre-computes those suggestions on a schedule
  • Halo answers place, opening-hours and address questions with live Places data through Atlas
  • Field masks keep each call to the fields you need, which is also what Google bills on
  • Your key, your Google Cloud project, your quotas; every call logged in your tenant

Use cases

  • Every company on the map — Back-fill Google places for your customer base on a schedule and confirm the matches in bulk, so territory and route planning in Iris start from verified coordinates.
  • Assistant answers with live place data — Let Halo look up a branch, its address and today's opening hours on request instead of hard-coding them in the persona.
  • Clean address capture — Use autocomplete and place details to turn a typed fragment into a structured address when creating a company or contact.

Places API (New) is Google's current place-data service on places.googleapis.com: search by free text or around a point, fetch a place's details — address, location, opening hours, ratings, business status — complete a partial query, and retrieve photo media. Apivom Atlas registers its five routes, all read-only, and two Apivom products use them with the tenant's own Maps Platform key. In Apivom Iris, the Maps tab of a company proposes Google places that match the company's name and address; Apivom Staff runs that text search on a schedule for companies that have no linked place yet and stores up to five candidates, and a user confirms the right one — nothing is bound automatically. The confirmed place feeds the map views and prospecting features in Iris. Apivom Halo, the conversational assistant, calls search and details through Atlas when a visitor asks about a location, so answers about addresses and opening hours come from Google rather than from the model's memory. Field masks are set on every call so Google bills only the SKU you actually need, and each request is logged in your tenant.

Authentication

Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.

Frequently asked questions

Does Iris change my company records automatically?

No. The scheduled back-fill only stores candidate places (at most five) for companies without a linked place; a user confirms the match in the company's Maps tab. An empty result is stored too, so the company is not re-queried until you ask for an overwrite.

Can I keep Google place data in my CRM?

Google's Maps Platform terms govern caching and display of Places data — place ids may be stored indefinitely, most other fields only briefly, and attribution rules apply. Iris stores the place id and the fields needed for display; review the terms for anything beyond that.

Which Google Cloud project pays for the calls?

The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.