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 find emails and contact information related to a specified domain or link. It is useful for scenarios such as lead generation, marketing research, or enriching contact databases by extracting publicly available email addresses and contacts associated with a company or website.
For example, a user can input a domain like "outscraper.com" and retrieve a list of emails and preferred contacts linked to that domain. The node supports asynchronous requests and webhook callbacks, enabling it to handle large or time-consuming queries efficiently.
Properties
| Name | Meaning |
|---|---|
| Query | Domain or link to search for emails and contacts (e.g., "outscraper.com"). |
| Preferred Contacts | Comma-separated list of preferred contacts to find within the results. |
| Async Request | Boolean flag indicating whether to make the request asynchronously. |
| Webhook | URL to which Outscraper will send a POST request once the asynchronous task is finished. |
| Additional Fields | Collection of optional parameters: |
| - Fields | Comma-separated specific fields to return in the response. |
| - UI | Boolean flag indicating whether to execute the request as a UI task. |
Output
The node outputs JSON data containing the found emails and contacts related to the queried domain or link. The structure typically includes details about each contact such as name, email address, position, and other relevant metadata depending on the requested fields.
If the asynchronous mode is enabled, the output may initially contain task status information, and the final results will be delivered via the specified webhook URL.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- Network access to the Outscraper API endpoint.
- If using asynchronous requests, a publicly accessible webhook URL must be provided to receive callback notifications.
Troubleshooting
Common Issues:
- Missing or invalid API key: Ensure the API key credential is correctly set up.
- Invalid query format: The "Query" property must be a valid domain or link.
- Webhook URL unreachable: For async requests, verify the webhook URL is publicly accessible and correctly configured to accept POST requests.
- Rate limits or quota exceeded: Outscraper API may limit the number of requests; check your plan and usage.
Error Messages:
- Authentication errors usually indicate issues with the API key.
- Validation errors may occur if required properties are missing or malformed.
- Timeout or network errors suggest connectivity problems or slow responses from the API.
Resolving these typically involves verifying credentials, input correctness, and network configurations.