Actions6
Overview
This node integrates with an external scraping API service to retrieve data from various web sources, including LinkedIn profiles. Specifically, for the LinkedIn Profile Search operation, it fetches detailed information about a LinkedIn profile or company page based on a provided LinkedIn URL.
Common scenarios where this node is beneficial include:
- Enriching contact or lead data by extracting public LinkedIn profile details.
- Automating recruitment workflows by gathering candidate profile information.
- Market research by scraping company LinkedIn pages for insights.
For example, given a LinkedIn profile URL, the node can return structured profile data such as name, job title, experience, and other publicly available information, which can then be used in downstream automation tasks.
Properties
| Name | Meaning |
|---|---|
| Profile URL | The full LinkedIn profile URL to scrape. |
| Private Profile | Boolean flag indicating if the profile is private (true) or public (false). |
| Type | The type of LinkedIn profile to scrape. Options: Profile (individual) or Company. |
Output
The node outputs JSON data containing the scraped LinkedIn profile information returned by the external scraping API. The structure depends on the API response but typically includes fields such as:
- Profile details (name, headline, location, etc.)
- Experience and education sections
- Company information if the type is set to "company"
- Metadata like request status and any error messages if applicable
If the profile is private or inaccessible, the output will contain an error object describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the external scraping service.
- The node makes HTTP GET requests to the scraping API endpoint configured via a base URL parameter (defaulting to
https://api.scrapingdog.com/). - Proper network access to the scraping API is necessary.
- No additional environment variables are required beyond the API key credential.
Troubleshooting
- Invalid or missing API key: The node will fail with an HTTP 401 or similar error. Ensure the API key credential is correctly configured.
- Incorrect LinkedIn URL format: The node extracts the last segment of the URL as the profile identifier. Providing malformed URLs may cause errors or unexpected results.
- Private profiles: If the profile is private and the
Private Profileflag is not set accordingly, the API may return limited or no data. - API rate limits or quota exceeded: The external service may reject requests if usage limits are reached; monitor your API usage.
- HTTP errors: The node surfaces HTTP status codes and messages from the API. Common issues include 404 (profile not found) or 500 (server error).
To resolve errors, verify input parameters, check API key validity, and consult the scraping service's documentation for rate limits and usage policies.
Links and References
- ScrapingDog API Documentation (for detailed API usage and parameters)
- LinkedIn Public Profiles (LinkedIn's official info on public profiles)
Note: This summary is based solely on static analysis of the provided source code and property definitions. Runtime behavior depends on the external scraping API responses.