Actions36
- Authentication Actions
- Profile Actions
- Company Actions
- Network Actions
- Message Actions
- Post Actions
- Recruiter Actions
- Data Actions
Overview
This node integrates with the Linkup API to automate LinkedIn activities. Specifically, the Profile - Get My Profile operation retrieves the authenticated user's LinkedIn profile information via the Linkup API.
Typical use cases include:
- Automatically fetching your own LinkedIn profile data for further processing or analysis.
- Integrating LinkedIn profile details into workflows such as CRM updates, reporting, or personalized messaging.
- Using the profile data as a basis for networking or recruitment automation.
Example: A user can trigger this node to get their LinkedIn profile details and then use that data to update a contact record in a database or send a customized message based on profile attributes.
Properties
| Name | Meaning |
|---|---|
| Advanced Options | Collection of optional settings: • Timeout: Request timeout in milliseconds (default 30000) • Retry Count: Number of retries on failure (default 3) |
Output
The node outputs JSON data containing the LinkedIn profile information of the authenticated user. The output structure includes:
- The full response from the Linkup API under the root JSON object.
- A
_debugfield providing diagnostic information including:requestBody: The exact request payload sent.requestHeaders: HTTP headers used.endpoint: The API endpoint called.apiResponse: Raw API response.
- A
_metafield with metadata:resource: The resource name ("profile").operation: The operation name ("getMyProfile").timestamp: ISO timestamp of execution.nodeVersion: Version of the node implementation.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for the Linkup API to authenticate requests.
- The node uses the Linkup API base URL:
https://api.linkupapi.com/v1. - Network connectivity to the Linkup API service.
- Optional configuration of timeout and retry count through advanced options.
Troubleshooting
- Missing API Key Error: If the API key credential is not configured or invalid, the node will throw an error indicating the missing API key. Solution: Configure the required API key credential in the node settings.
- Request Timeout: If the request takes longer than the specified timeout (default 30 seconds), it may fail. Adjust the timeout in advanced options if needed.
- API Errors: Any errors returned by the Linkup API will be included in the output JSON under an
errorfield. Check the error message for details. - Network Issues: Ensure stable internet connection and that the Linkup API endpoint is reachable.
- Invalid Credentials: If authentication fails due to incorrect email/password or token, verify credentials are correct and up to date.
Links and References
- Linkup API Documentation — Official site to create account and obtain API keys.
- LinkedIn Developer Resources — For understanding LinkedIn data and API usage concepts.