Actions8
Overview
This node integrates with the LINKUP API to perform LinkedIn profile searches and other LinkedIn-related automation tasks. Specifically, the Search Profile operation allows users to search for LinkedIn profiles based on various criteria such as company, location, school, network level, keywords, and personal name filters.
Typical use cases include:
- Recruiting professionals by filtering LinkedIn profiles according to specific companies, locations, or skills.
- Market research by identifying potential leads or contacts within certain industries or geographic areas.
- Automating LinkedIn data extraction workflows to enrich CRM or marketing databases.
For example, a recruiter could use this node to find all LinkedIn profiles in France working at "Google" or having studied at "Stanford," retrieving up to 10 profiles per execution.
Properties
| Name | Meaning |
|---|---|
| Utiliser des credentials personnalisées | Whether to use custom credentials (API key and LinkedIn login token) instead of saved credentials. |
| LINKUP API Key | Your LINKUP API key from the linkupapi.com dashboard (required if using custom credentials). |
| Login Token | LinkedIn authentication token obtained after login/verify (required if using custom credentials). |
| Pays | Country code for proxy selection; options: France (FR), United States (US), United Kingdom (UK). |
| Options avancées | Collection of advanced search filters: |
| Company URL(s) | LinkedIn company URLs or identifiers separated by semicolons (e.g., "google;microsoft;apple"). |
| Location(s) | Geographic locations separated by semicolons (e.g., "Paris;London;New York"). |
| School URL(s) | LinkedIn school URLs or identifiers separated by semicolons (e.g., "harvard;stanford;mit"). |
| Network | Connection level filter: F=1st degree, S=2nd degree, O=out of network; separated by semicolons (e.g., "F;S"). |
| Keyword | Search keyword to filter profiles. |
| Nombre de résultats | Number of profiles to retrieve (default 10). |
| Page de début | First page number to retrieve for pagination (default 1). |
| Page de fin | Last page number to retrieve for pagination (default 1). |
| Prénom | Filter by first name. |
| Nom | Filter by last name. |
| Titre | Filter by job title. |
| Afficher l'état d'invitation | Include invitation/connection status for each profile (boolean, default true). |
| Options avancées (additionalFields) | Additional request options: |
| Timeout | Request timeout in milliseconds (default 30000 ms). |
| Nombre de tentatives | Number of retry attempts on failure (default 3). |
Output
The node outputs an array of JSON objects representing the search results returned by the LINKUP API. Each output item includes:
- The full API response fields containing LinkedIn profile data matching the search criteria.
- A
_debugobject with details about the request body sent, request headers, and raw API response for troubleshooting. - A
_metaobject containing metadata such as the operation name (searchProfile), timestamp of execution, and node version.
Example structure snippet:
{
"json": {
"_debug": {
"requestBody": { /* search parameters sent */ },
"requestHeaders": { /* HTTP headers used */ },
"apiResponse": { /* raw API response data */ }
},
/* ... actual profile search results ... */
"_meta": {
"operation": "searchProfile",
"timestamp": "2024-06-xxTxx:xx:xx.xxxZ",
"nodeVersion": "1.1.0"
}
},
"pairedItem": {
"item": 0
}
}
No binary data is produced by this operation.
Dependencies
- Requires access to the LINKUP API at
https://api.linkupapi.com/v1. - Needs a valid LINKUP API key credential and a LinkedIn authentication token (login token).
- Optionally supports using either saved credentials or custom credentials provided directly in the node parameters.
- Network connectivity must allow outbound HTTPS requests to the LINKUP API endpoint.
- No additional external libraries beyond n8n core dependencies are required.
Troubleshooting
Common Issues
- Invalid or missing credentials: If the API key or LinkedIn login token is incorrect or missing, the node will fail authentication.
- Rate limiting: Exceeding the allowed number of API requests may result in rate limit errors.
- Invalid request parameters: Providing malformed or unsupported search filters can cause the API to reject the request.
- Timeouts: Slow network or large result sets might cause request timeouts.
Error Messages and Resolutions
"Clé API ou credentials invalides. Vérifiez votre clé API LINKUP et vos identifiants LinkedIn."
Means the API key or LinkedIn token is invalid or expired. Verify and update your credentials."Limite de requêtes atteinte. Veuillez réessayer plus tard."
Indicates that the API rate limit has been reached. Wait before retrying or reduce request frequency."Requête invalide : <message>"
The request was malformed. Check the search parameters and ensure they conform to expected formats.Generic
"Erreur inconnue"or other error messages suggest unexpected issues; check the_debugoutput for request and response details to diagnose.
Links and References
- LINKUP API Documentation (official API docs)
- LINKUP Dashboard (for managing API keys)
- LinkedIn Authentication Tokens (general info on LinkedIn auth tokens)
This summary covers the static analysis of the node's execute() method for the "Default" resource and "Search Profile" operation, including input properties, output format, dependencies, and common troubleshooting tips.