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 "Phones Owner" resource with the "Get Owners" operation allows users to retrieve ownership information about a given phone number. This node interacts with the Outscraper API to query details related to the owner of a specified phone number.
Common scenarios where this node is beneficial include:
- Verifying the identity behind a phone number for fraud prevention.
- Enriching contact data in CRM systems.
- Investigating unknown callers or leads by obtaining ownership details.
- Automating phone number lookups in customer support workflows.
For example, a user can input a phone number like "+1 281 236 8208" and receive detailed information about the owner, such as name, address, or other available fields depending on the API response.
Properties
| Name | Meaning |
|---|---|
| Query | The phone number to look up (e.g., "+1 281 236 8208"). Required. |
| 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 list of 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 ownership information of the queried phone number. The exact structure depends on the fields requested and the API response but generally includes details such as owner name, address, and other metadata related to the phone number.
If the request is made asynchronously, the output may initially contain task status information, and the final results will be sent to the provided webhook URL.
This node does not output binary data.
Dependencies
- Requires an active Outscraper API key credential configured in n8n.
- The base URL and API key are set via node credentials.
- For asynchronous requests, a publicly accessible webhook URL must be provided to receive callback data.
Troubleshooting
- Missing or invalid phone number: Ensure the "Query" property contains a valid phone number string; otherwise, the API will reject the request.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Webhook failures: If using async mode, ensure the webhook URL is reachable and properly handles incoming POST requests.
- Empty or incomplete responses: Check if the requested fields are supported and that the phone number exists in the data source.
- Rate limiting or quota exceeded: Outscraper API may limit requests; monitor usage and upgrade your plan if necessary.
Links and References
- Outscraper API Documentation
- Phone Number Lookup Use Cases
- n8n Documentation - HTTP Request Node (for webhook handling)