Overview
This node interacts with the Encharge platform to manage contacts (referred to as "people"). Specifically, the Get Contact operation retrieves detailed information about a contact using their unique email address. This is useful in scenarios where you want to fetch existing contact data for further processing, such as personalization, segmentation, or synchronization with other systems.
Practical examples include:
- Retrieving a contact's profile before updating it.
- Fetching contact details to trigger conditional workflows.
- Integrating contact data into reports or dashboards.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests; currently supports "API Key" authentication. |
| People EMail | The unique email address identifying the contact to retrieve. |
| Options | Additional optional fields to customize the request; allows specifying custom field filters. |
The Options property supports adding multiple custom fields as key-value pairs to refine or extend the query parameters sent to the API.
Output
The output JSON contains the full contact data returned by the Encharge API for the specified email. This includes all standard and custom fields associated with the contact.
If the operation succeeds, the output will be an array with one or more objects representing the contact(s) matching the email query.
No binary data output is produced by this node.
Dependencies
- Requires an active Encharge account with API access.
- Needs an API key credential configured in n8n for authentication.
- Relies on the Encharge REST API endpoint
/peoplefor contact retrieval.
Troubleshooting
Common issues:
- Providing an incorrect or non-existent email will result in no contact found or empty results.
- Missing or invalid API key will cause authentication errors.
- Network connectivity problems can lead to request timeouts or failures.
Error messages:
"Unauthorized"or similar indicates invalid API credentials; verify and update the API key."Contact not found"or empty response means the email does not exist in Encharge.- Other HTTP errors should be checked against Encharge API documentation for resolution.