Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
The "Search Profile" operation of the Linkup API node enables users to search LinkedIn profiles programmatically using a variety of filters and parameters. This node is useful for automating LinkedIn profile discovery, lead generation, recruitment sourcing, or market research by querying profiles based on keywords, locations, companies, schools, network levels, titles, and more.
Typical use cases include:
- Finding potential candidates with specific job titles in certain locations.
- Searching for professionals working at particular companies or industries.
- Filtering profiles by first name, last name, or business sector.
- Retrieving a list of profiles with invitation status included to manage networking outreach.
For example, a recruiter could automate searching for software engineers in New York who attended a specific university and work at target companies, retrieving up to 50 results per query.
Properties
| Name | Meaning |
|---|---|
| Keyword | Search keyword to filter profiles by relevant terms. |
| Location(s) | Geographic location(s) to narrow down the search (multiple separated by semicolons). |
| Company(ies) | LinkedIn company URL(s) to filter profiles currently working at these companies (multiple separated by semicolons). |
| School(s) | LinkedIn school URL(s) to filter profiles who attended these schools (multiple separated by semicolons). |
| Network | Connection level filter: F=1st degree, S=2nd degree, O=outside network. |
| Sector(s) | Business sector(s) to filter profiles by industry (multiple separated by semicolons). |
| Company Size | Filter profiles by company size range. |
| First Name | Filter profiles by first name. |
| Last Name | Filter profiles by last name. |
| Title/Position | Filter profiles by current title or position. |
| Show Invitation Status | Boolean flag to include invitation status information for each profile in the results. |
| Post Type | Type of post to search (used when searching posts; available but not applicable here). |
| Sort By | Criteria to sort posts (not applicable for profile search). |
| Post Date | Filter posts by date (not applicable for profile search). |
| LinkedIn URL (search) | LinkedIn URL used as a search parameter (rarely used in profile search). |
| Number of Results | Number of profile results to retrieve (default 10). |
| Start Page | Starting page number for paginated results (default 1). |
| End Page | Ending page number for paginated results (default 1). |
| Country Code | Country code for proxy selection and regional targeting (e.g., FR, US, UK, DE, ES, IT, CA, AU). |
Advanced Options
| Name | Meaning |
|---|---|
| Timeout | Request timeout in milliseconds (default 30000) |
| Retry Count | Number of retries on failure (default 3) |
Output
The node outputs JSON data containing the response from the Linkup API for the profile search request. The output includes:
- The main data returned by the API, typically an array of profile objects matching the search criteria.
- A
_debugfield containing:requestBody: The exact request payload sent to the API.requestHeaders: HTTP headers used in the request.endpoint: The API endpoint called.apiResponse: Raw API response.
- A
_metafield with metadata including:resource: The resource type ("profile").operation: The operation performed ("searchProfile").timestamp: ISO timestamp of execution.nodeVersion: Version of the node implementation.
Each output item is paired with its input item index for traceability.
The node does not output binary data.
Dependencies
- Requires an API key credential for the Linkup API service.
- The node uses the Linkup API base URL
https://api.linkupapi.com/v1. - Requires proper configuration of the API key credential in n8n credentials settings.
- Optionally uses country codes for proxy selection and regional targeting.
Troubleshooting
- Missing API Key: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Ensure the API key is set correctly in the node credentials.
- Timeouts: Requests may time out if the server is slow or network issues occur. Adjust the "Timeout" advanced option to a higher value if needed.
- Invalid Parameters: Providing incorrect or malformed parameters (e.g., invalid URLs or unsupported values) may cause API errors. Validate inputs before running.
- Rate Limits: The Linkup API may enforce rate limits. If you encounter errors related to too many requests, reduce the frequency or implement retry logic.
- Country Code Issues: Using unsupported or incorrect country codes may affect proxy routing and cause failures. Use valid ISO country codes as specified.
Links and References
- Linkup API Documentation — Official site to create accounts and get API keys.
- LinkedIn Profiles — For understanding profile URLs and structure.
- n8n Documentation on Credentials — How to configure API keys securely in n8n.