Data and research
Google Places
A Google Places integration connects Google Places to Mobius so loops can search businesses, search nearby places, and read place details.
Use Google Places when a run needs location-aware research before outreach, routing, verification, or enrichment.
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 Govern > Integrations, choose Google Places, and paste a Google Places API key when the project 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/projects/{project}/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 a project-local key.
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 loop will use.
Events
Google Places does not register source events.
Next
- Store enrichment results in tables.
- Inspect action schemas from actions.
- Keep API keys in integrations.