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 node integrates with the Outscraper API to retrieve photos related to a specified location or place. Specifically, for the Google Map resource and the "Get Photos" operation, it allows users to search for photos by providing a search query or a place ID. This is useful in scenarios where you want to enrich your workflows with visual content from Google Maps, such as gathering images of landmarks, businesses, or points of interest.
Practical examples include:
- Automatically fetching photos of a business location to display on a website or app.
- Collecting images for travel blogs or guides based on place names or IDs.
- Enhancing marketing materials with relevant location photos without manual searching.
Properties
| Name | Meaning |
|---|---|
| Query | Search query string or place ID to specify the location for which photos are requested. |
| Async Request | Boolean flag indicating whether the request should be made asynchronously (true/false). |
| Photos Limit | Maximum number of photos to retrieve from one place (numeric limit). |
| Language | Language code (e.g., "en", "fr", "es") to specify the language of the results. |
| Webhook | URL to which Outscraper will send a POST request once the photo retrieval task is finished. |
Output
The node outputs JSON data containing the retrieved photos related to the specified query or place ID. The structure typically includes metadata about each photo such as URLs, descriptions, and possibly other attributes provided by the Outscraper API.
If asynchronous mode is enabled, the output may initially contain task status information, and the final photo data will be sent to the specified webhook URL once processing completes.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- Needs network access to the Outscraper API endpoint.
- For asynchronous requests, a publicly accessible webhook URL must be provided to receive callback data.
Troubleshooting
Common issues:
- Invalid or missing API key: Ensure the Outscraper API key is correctly set up in n8n credentials.
- Incorrect query or place ID: Verify that the input query or place ID is valid and correctly formatted.
- Webhook not reachable: If using async mode, ensure the webhook URL is publicly accessible and can accept POST requests.
- Exceeding photo limits: The API may restrict the maximum number of photos; adjust the "Photos Limit" accordingly.
Error messages:
- Authentication errors usually indicate invalid API keys.
- Rate limit errors suggest too many requests in a short time; consider adding delays or upgrading the API plan.
- Network errors may occur if the API endpoint is unreachable; check internet connectivity and API status.
Links and References
- Outscraper API Documentation
- Google Maps Photos API Overview (for conceptual understanding)
- n8n Documentation on Using Webhooks