Overview
The Reverse Contact node for n8n is designed to enrich contact information by finding LinkedIn profiles and related data based on an email address. Specifically, when using the Contact resource with the Enrich operation, the node queries the ReverseContact API to retrieve enriched details about a person associated with the provided email.
Common scenarios:
- Automatically augmenting CRM records with social and professional profile data.
- Verifying or supplementing lead information in marketing automation workflows.
- Enriching user databases with up-to-date LinkedIn and contact details.
Practical example:
You have a list of customer emails and want to automatically fetch their LinkedIn profiles and other public information to improve your sales outreach or personalize communications.
Properties
| Name | Type | Meaning |
|---|---|---|
| String | Email of the contact to be enriched. This is required and used to look up additional information via the API. |
Output
The node outputs a json object containing the enriched contact information returned by the ReverseContact API. The exact structure depends on the API response, but typically includes fields such as:
- Name
- LinkedIn profile URL
- Job title
- Company
- Location
- Other publicly available data associated with the email
Note: The node does not output binary data.
Dependencies
- External Service: Requires access to the ReverseContact API.
- API Key: You must provide a valid ReverseContact API key via n8n credentials (
reverseContactApi).
Troubleshooting
Common issues:
- Invalid or missing API key: If the API key is incorrect or not provided, the node will fail to authenticate with the ReverseContact API.
- Email not found: If the provided email does not correspond to any known contact, the API may return an empty result or a "not found" error.
- Rate limits: Exceeding the allowed number of API requests may result in rate limit errors from the service.
Error messages and resolutions:
"401 Unauthorized": Check that your API key is correct and has not expired."404 Not Found": The email address could not be enriched; verify the input or try another email."429 Too Many Requests": Wait before making more requests or upgrade your API plan.