Actions8
Overview
The node provides integration with the LINKUP API, enabling LinkedIn automation tasks. It supports multiple operations such as logging into a LinkedIn account via LINKUP, verifying security codes, retrieving LinkedIn profiles, extracting public profile information, searching for LinkedIn profiles and companies, obtaining company details, and sending connection requests.
This node is beneficial in scenarios where users want to automate LinkedIn-related workflows, such as bulk profile extraction, lead generation, or managing connection requests programmatically without manual intervention.
For example, a user can automate the login process to LinkedIn through LINKUP, then extract detailed profile information of potential leads, or search companies by specific criteria and gather their data for marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Utiliser des credentials personnalisées (useCustomCredentials) | Whether to use custom credentials instead of saved ones (fallback option). |
| LINKUP API Key (customApiKey) | Your LINKUP API key from the linkupapi.com dashboard (required if using custom credentials). |
| Email LinkedIn (customLinkedinEmail) | LinkedIn account email address (required for login operation when using custom credentials). |
| Mot de passe LinkedIn (customLinkedinPassword) | LinkedIn account password (required for login operation when using custom credentials). |
| Login Token (optionnel) (customLoginToken) | Optional LinkedIn authentication token if available (used during login with custom credentials). |
| Pays (customCountry) | Country code for proxy selection; options: France (FR), United States (US), United Kingdom (UK). |
| Options avancées (additionalFields) | Advanced options including: - Timeout: Request timeout in milliseconds (default 30000). - Nombre de tentatives: Number of retry attempts on failure (default 3). |
Output
The node outputs JSON data containing the response from the LINKUP API corresponding to the selected operation. The output includes:
- The main API response fields relevant to the operation performed.
- A
_metafield with metadata such as:operation: The operation name executed.timestamp: ISO timestamp of execution.nodeVersion: Version of the node implementation.
- For some operations like profile or company searches, a
_debugfield may be included showing request body and headers for troubleshooting.
No binary data output is produced by this node.
Dependencies
- Requires an active LINKUP API key credential for authentication.
- Optionally requires LinkedIn account credentials (email and password) or a LinkedIn login token depending on the operation.
- Network access to
https://api.linkupapi.com/v1endpoint. - n8n HTTP Request helper is used internally to perform API calls.
- Proxy country selection is supported via the "Pays" property for regional routing.
Troubleshooting
Common Issues
- Invalid Credentials: If the API key or LinkedIn credentials are incorrect or incomplete, the node will throw an error indicating corrupted or incomplete credentials.
- Rate Limiting: Exceeding the allowed number of API requests results in a rate limit error.
- Invalid Requests: Sending malformed or incomplete data to the API causes invalid request errors.
- Timeouts: Network delays or slow responses might cause timeouts; adjustable via the "Timeout" advanced option.
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 credentials are invalid. Verify and re-enter your credentials or use the custom credentials option."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 sent to the API was invalid. Check the input parameters and ensure all required fields are correctly set."Erreur inconnue"
An unknown error occurred. Check network connectivity and API status.
Links and References
- LINKUP API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling in n8n)
This summary covers the "Default" resource and "Login" operation specifically, focusing on the properties and logic related to authenticating a LinkedIn account via the LINKUP API.