Actions18
- Company Actions
- Search Actions
- Google Actions
- Group Actions
- User Actions
- Email Actions
- Post Actions
Overview
This node integrates with the Horizon Data Wave LinkedIn API to retrieve LinkedIn user information based on an email address. Specifically, the "Get User by Email" operation allows you to find LinkedIn users by providing their email addresses. This is useful in scenarios such as enriching contact data, verifying user identities, or linking email contacts to their LinkedIn profiles.
Practical examples include:
- Enriching a CRM system by fetching LinkedIn profiles of contacts using their emails.
- Validating if an email corresponds to a LinkedIn user before outreach.
- Automating lead generation workflows by connecting email lists to LinkedIn profiles.
Properties
| Name | Meaning |
|---|---|
The email address to search for the LinkedIn user. Example: name@email.com |
|
| Count | Maximum number of results to return. Default is 5. |
| Timeout | Timeout duration in seconds for the API request. Default is 300 seconds (5 minutes). |
Output
The output contains JSON data representing the LinkedIn user(s) found by the provided email address. The structure depends on the API response but typically includes user profile details such as name, headline, location, and other LinkedIn profile attributes.
If multiple users are returned (up to the specified count), each user is output as a separate item in the node's output array.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Horizon Data Wave LinkedIn API.
- Requires configuration of an API authentication credential (an API key or token) within n8n to authenticate requests to the external service.
- The base URL used for API calls is
https://api.horizondatawave.ai.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid or malformed email address may result in no results or errors.
- Network timeouts or slow responses can occur; adjust the "Timeout" property accordingly.
- If no user is found for the given email, the output may be empty or contain an error message.
Error messages:
- Errors from the API are captured and included in the output JSON under an
errorfield with additional details if available. - To handle errors gracefully, enable the node’s "Continue On Fail" option to prevent workflow interruption.
- Errors from the API are captured and included in the output JSON under an
Links and References
- Horizon Data Wave LinkedIn API Documentation (general reference)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
This summary is based solely on static analysis of the provided source code and input properties.