Actions16
Overview
The HighLevel node for n8n allows you to interact with the HighLevel API, specifically to look up contact information based on email and/or phone number. The "Contact: Lookup" operation is useful in scenarios where you need to retrieve details about a contact already present in your HighLevel CRM system, such as verifying if a lead exists before creating a new one or enriching workflow data with contact details.
Practical examples:
- Checking if a contact exists before sending a marketing email.
- Retrieving contact details to personalize follow-up messages.
- Validating user input against existing contacts in automated workflows.
Properties
| Name | Type | Meaning |
|---|---|---|
| String | Lookup Contact by Email and/or Phone. Used to find a contact by email. | |
| Phone | String | Lookup Contact by Phone and/or Email. Used to find a contact by phone. |
Both fields can be used independently or together to perform the lookup.
Output
The node returns a json object containing the contact details retrieved from the HighLevel API. The exact structure of the output will match the response format provided by the HighLevel API for contact lookups, typically including fields like name, email, phone, and other contact metadata.
Note: This node does not output binary data.
Dependencies
- External Service: Requires access to the HighLevel API (https://rest.gohighlevel.com/v1).
- API Key: You must configure valid HighLevel API credentials in n8n under the credential type
highLevelApi. - n8n Configuration: No additional configuration required beyond setting up credentials.
Troubleshooting
Common Issues:
- Missing or Invalid Credentials: If the API key is missing or incorrect, the node will fail to authenticate. Ensure that the
highLevelApicredentials are set up correctly in n8n. - No Contact Found: If no contact matches the provided email or phone, the output may be empty or contain an error message indicating "Contact not found."
- Rate Limiting: Excessive requests may trigger rate limits on the HighLevel API, resulting in errors like "429 Too Many Requests."
Error Messages and Resolutions:
"401 Unauthorized": Check your API credentials."404 Not Found": Verify the email/phone values; ensure the contact exists."429 Too Many Requests": Reduce request frequency or check your API plan limits.