Overview
This node, "GeoScraper Google Map Scraper," provides unified access to various Google Maps scraping operations via an external GeoScraper API. Specifically for the Single Place operation, it retrieves detailed information about a single place on Google Maps using either a unique internal data ID or the official Google Maps place ID.
Common scenarios where this node is beneficial include:
- Fetching detailed place information (address, contact info, ratings, etc.) for a known location.
- Enriching datasets with verified Google Maps place details.
- Integrating place details into workflows that require up-to-date location metadata.
Practical example:
- You have a list of place IDs from Google Maps and want to retrieve detailed information about each place to display in your application or perform further analysis.
Properties
| Name | Meaning |
|---|---|
| ID Type | Choose whether to identify the place by "Data ID" (internal unique identifier) or "Place ID" (Google Maps official place_id). |
| Data ID | The unique internal identifier for the place (used if ID Type is "Data ID"). |
| Place ID | The Google Maps place_id string identifying the place (used if ID Type is "Place ID"). |
| Language | Language code (e.g., "en") to specify the language of the response data. |
| Use Cached | Boolean flag indicating whether to use cached data if available (true/false). |
Output
The output JSON contains detailed information about the requested place. The exact structure depends on the GeoScraper API response but typically includes fields such as:
- Place name
- Address components
- Contact information (phone, website)
- Ratings and reviews summary
- Opening hours
- Geographic coordinates
If multiple results are returned (rare for single place), each will be output as a separate item.
No binary data output is produced by this operation.
Dependencies
- Requires an active API token credential for the GeoScraper service.
- The node makes HTTP POST requests to the GeoScraper API endpoints.
- No additional environment variables are required beyond the configured API token.
Troubleshooting
- Missing ID value error: If neither Data ID nor Place ID is provided when required, the node throws an error: "You must provide a value for the selected ID type." Ensure you supply the correct identifier matching the chosen ID Type.
- 404 No data found: If the place cannot be found, the node returns a message indicating no more results. This usually means the ID is invalid or the place does not exist.
- API authentication errors: If the API token is missing or invalid, requests will fail. Verify the API token credential is correctly set up.
- Network or API errors: General HTTP errors will cause the node to fail unless "Continue On Fail" is enabled, in which case errors are returned as part of the output JSON.