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 Whitepages Addresses Scraper node allows users to scrape detailed address information from the Whitepages database via the Outscraper API. This node is useful for scenarios where you need to enrich or verify address data, perform lead generation, validate customer addresses, or gather location-based insights.
For example, a marketing team could input a list of partial or full addresses to retrieve standardized and verified address details. Similarly, real estate professionals might use it to gather comprehensive address data for property listings.
Properties
| Name | Meaning |
|---|---|
| Query | The address query string to search for (e.g., "321 California Ave, Palo Alto, CA 94306"). |
| Async Request | Whether to make the request asynchronously (true/false). |
| Webhook | A callback URL where Outscraper will send a POST request once the scraping task is finished. |
| Additional Fields | Collection of optional parameters: |
| - Fields | Comma-separated list of specific fields to return in the response. |
| - UI | Whether to execute the request as a UI task (true/false). |
Output
The node outputs JSON data containing the scraped address information returned by the Outscraper API. The structure typically includes detailed address components and related metadata depending on the requested fields.
If the asynchronous mode is enabled with a webhook URL, the output may initially contain task status information, and the final results will be sent to the specified webhook.
No binary data output is expected from this node.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- The node sends requests to the Outscraper API endpoint defined by the user's credentials.
- If using asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks.
Troubleshooting
- Missing or invalid API key: Ensure that the Outscraper API key credential is correctly set up and valid.
- Invalid query format: The "Query" property must be a properly formatted address string; otherwise, the API may return errors or no results.
- Webhook issues: When using async mode, ensure the webhook URL is reachable and can accept POST requests; otherwise, results will not be delivered.
- Field selection errors: Specifying invalid or unsupported fields in the "Fields" parameter may cause incomplete or failed responses.
- Network or API downtime: Temporary network issues or Outscraper service outages can cause request failures; retry after some time.
Links and References
- Outscraper API Documentation
- Whitepages Address Data Overview (for general understanding of address data)