Google Places
Google Places gives Mobius local search actions.
A Google Places integration connects Google Places to Mobius. Assistants can use it to search businesses, search nearby places, and read place details.
Use Google Places when an assistant needs location-aware research before outreach, routing, verification, or enrichment.
For the shared Google credential model, see Google integrations.
Capability map
| Capability | Value |
|---|---|
| Provider ID | google_places |
| Auth kind | api_key |
| Connect flow | Inline API key or platform credential |
| Actions | Yes |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | No |
Connect Google Places
| Surface | Support |
|---|---|
| App | Open Build > Integrations, choose Google Places, and paste a Google Places API key when the organization should use its own quota. |
| CLI | The mobius CLI does not connect Google Places integrations yet. Use the app or API. |
| API | Call POST /v1/integrations/providers/google_places/connect through the generic provider connect endpoint. |
If the catalog marks Google Places ready through a platform credential, actions can run without an organization-local key.
When Mobius supplies the platform credential, there is no connected account to grant. Add the Places tools to the assistant and stay within the access and funding shown in the catalog. For your own key, use Account manager to choose You or Your team, then grant the exact connection under Assistant access. If several Places keys are eligible, save an account preference so Mobius does not guess which quota to use.
Credentials and quota
Organization-owned Google Places keys use your Google Maps Platform project, billing account, quotas, and field configuration. Built-in Mobius credentials are useful for quick evaluation, but production work should use an organization key when you need your own Google quota, Maps Platform billing visibility, or stricter key restrictions.
Restrict the API key in Google Cloud to the Places API endpoints Mobius uses. Rotate the key from the integration page when you change restrictions or move the integration to a different Google Cloud project.
Actions
google_places.get_details
google_places.search_nearby
google_places.search_textUse search actions to find candidate place IDs, then call
google_places.get_details for the exact place the assistant will use.
Request only the fields the assistant needs. Places field selection affects response shape and Google Maps Platform billing.
Events
Google Places does not register source events.
Troubleshooting
Actions fail with permission or API-key errors
Check that the Google Cloud project has Places API enabled, billing active, and API-key restrictions that allow server-side calls from Mobius.
Search returns too much data
Use included_type, included_types, location filters, and explicit detail
fields. Store only the fields you need in Mobius tables.
Next
- Store enrichment results in tables.
- Inspect action schemas from actions.
- Manage connected keys in Connect accounts.