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 perform a "Find Identity" operation specifically for the "Phone Identity Finder" resource. This operation allows users to query phone numbers and retrieve associated identity information. It is useful in scenarios such as verifying phone number ownership, enriching contact data, or performing background checks based on phone numbers.
Practical examples include:
- A marketing team validating phone leads by confirming the identity behind a phone number.
- Customer support teams enriching caller information automatically.
- Fraud detection systems verifying phone number authenticity.
Properties
| Name | Meaning |
|---|---|
| Query | The phone number to search for (e.g., +1 281 236 8208). This is a required input. |
| Async Request | Boolean flag indicating whether the request should be made asynchronously. |
| Webhook | URL to which Outscraper will send a POST callback once the asynchronous task is finished. |
| Additional Fields | Collection of optional parameters: - Fields: Comma-separated list of specific fields to return. - UI: Boolean flag to execute the request as a UI task. |
Output
The node outputs JSON data containing the identity information related to the queried phone number. The exact structure depends on the fields requested but generally includes details such as name, address, and other identity attributes linked to the phone number.
If the request is asynchronous, the output may initially contain task status or identifiers, with the final results 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 callbacks.
Troubleshooting
Common Issues:
- Invalid or improperly formatted phone number in the Query property can cause errors or empty results.
- Missing or incorrect API key credential will result in authentication failures.
- If asynchronous mode is enabled without providing a valid webhook URL, the callback will fail.
- Network connectivity issues to the Outscraper API endpoint.
Error Messages:
- Authentication errors typically indicate invalid or missing API credentials; verify and update the API key.
- Validation errors may point to malformed phone numbers; ensure the phone number follows international format.
- Timeout or webhook delivery failures suggest network or URL accessibility problems; confirm webhook URL is reachable.
Links and References
- Outscraper API Documentation (for detailed API usage and field descriptions)
- Phone Number Formatting Guidelines (recommended phone number format)