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
This node integrates with the Outscraper API to perform geocoding operations, specifically converting address queries into geographic coordinates and related location data. It is useful in scenarios where you need to transform human-readable addresses into latitude and longitude for mapping, spatial analysis, or location-based services.
For example, you can input an address like "321 California Ave, Palo Alto, CA 94306" and receive detailed geolocation information that can be used to plot points on a map, enrich datasets with location metadata, or validate address accuracy.
Properties
| Name | Meaning |
|---|---|
| Query | The address string specifying the location to geocode (e.g., "321 California Ave, Palo Alto, CA 94306"). This is a required input. |
Output
The node outputs JSON data containing the geocoded results corresponding to the input query. This typically includes geographic coordinates (latitude and longitude), formatted address details, and possibly additional metadata about the location.
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 by the user's credentials.
- Proper internet connectivity and valid API credentials are necessary for successful execution.
Troubleshooting
- Invalid or missing API key: Ensure that the API key credential is correctly set up in n8n and has the necessary permissions.
- Malformed address query: Verify that the input address string is complete and correctly formatted to improve geocoding accuracy.
- API rate limits or quota exceeded: Check your Outscraper account limits if requests start failing.
- Network issues: Confirm that the n8n instance has internet access to reach the Outscraper API.
Common error messages will generally relate to authentication failures, invalid parameters, or network timeouts. Resolving these involves checking credentials, input correctness, and network status.
Links and References
- Outscraper API Documentation – Official documentation for the Outscraper API including geocoding endpoints.
- Geocoding Concepts – General overview of geocoding principles (not specific to Outscraper).