Actions49
- Airbnb Actions
- AppStore Actions
- Booking Actions
- Company Insight Actions
- Emails & Contact Actions
- Expedia Actions
- G2 Review Actions
- Geocoding Actions
- GetApp Review Actions
- Google Map Actions
- Google Search Actions
- Indeed Actions
- Phone Identity Finder Actions
- Phones Owner Actions
- Product Hunt Actions
- Target Review Actions
- TikTok Profile Actions
- TripAdvisor Actions
- Trustpilot Actions
- Twitter Profile Actions
- Universal AI Scraper Actions
- Walmart Review Actions
- WebPage Screenshoter Actions
- Whitepages Addresses Scraper Actions
- Yellow Pages Search Actions
- Yelp Actions
- YouTube Actions
- Zillow Actions
Overview
The Google Map Search operation in this node allows users to perform location-based searches using the Outscraper API. It enables querying places or locations by a search string or place ID, returning relevant geographic results. This is useful for applications that need to find places, addresses, or points of interest programmatically.
Common scenarios include:
- Finding businesses or landmarks near a location.
- Retrieving details about a specific place by its name or ID.
- Integrating location search functionality into workflows for marketing, logistics, or travel planning.
For example, you could use this node to search for "coffee shops in New York" and get a list of matching places with their details.
Properties
| Name | Meaning |
|---|---|
| Query | The search query or place ID to look up. |
| Limit | Maximum number of results to return (minimum 1). |
| Language | Language code for the results (e.g., "en" for English, "fr" for French, "es" for Spanish). |
| Async Request | Whether to make the request asynchronously (true/false). |
| Webhook | URL to which Outscraper will send a POST callback once the asynchronous task finishes. |
Output
The output JSON contains the search results returned by the Outscraper API for the given query. This typically includes an array of place objects with details such as names, addresses, coordinates, and other metadata depending on the API response.
If the asynchronous option is enabled, the node may not immediately return results but instead rely on the webhook callback to receive data once the search completes.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- The node sends requests to the Outscraper API endpoint specified in the credentials.
- For asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks.
Troubleshooting
- Empty or no results: Check that the query string is valid and specific enough. Also verify the language code if used.
- API authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Webhook failures: If using async mode, confirm the webhook URL is reachable and correctly configured to accept POST requests.
- Limit value issues: The limit must be at least 1; setting it lower may cause errors.
- Network or timeout errors: Verify network connectivity and Outscraper service status.
Links and References
- Outscraper API Documentation
- Google Maps Platform (for understanding place data concepts)