Overview
This node integrates with the Encharge platform to manage contacts (referred to as "people" in the code). Specifically, the Create Contact operation allows users to add new contacts by providing an email and optional additional information such as name, IP address, tags, and custom fields. This is useful for marketing automation workflows where you want to programmatically add leads or subscribers into your Encharge account.
Practical examples include:
- Adding a new subscriber from a web form submission.
- Importing contacts from another system into Encharge.
- Automatically tagging contacts based on campaign source or user behavior.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "API Key". |
| The email address of the contact to create. | |
| Additional Fields | Optional extra data about the contact: |
| - IP Address | The contact's IP address (IPv4 or IPv6). |
| - Name | Full name of the contact. |
| - userId | An identifier for the user (custom field). |
| - firstName | Contact's first name. |
| - lastName | Contact's last name. |
| - utm_source | UTM source tag for tracking (default "ABCD"). |
| - first_utm_source | First UTM source tag (default "n8n"). |
| - Tag Names or IDs | Tags to assign to the contact; can be selected from a list or specified via expressions. |
Output
The node outputs JSON data indicating the success of the operation. For the Create Contact operation, the output JSON will be:
{
"success": true
}
This confirms that the contact was successfully created in Encharge.
No binary data output is produced by this node.
Dependencies
- Requires an active Encharge account.
- Requires an API key credential for authentication with Encharge.
- The node uses the Encharge REST API endpoints
/peoplefor creating contacts and/tags-managementto load available tags. - No additional environment variables are needed beyond the API key credential.
Troubleshooting
- Common issues:
- Invalid or missing API key: The node will fail to authenticate with Encharge.
- Missing required email property: The node requires an email to create a contact.
- Incorrect tag names or IDs: If tags do not exist or are misspecified, the API may reject the request.
- Error messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- Validation errors from the API may indicate malformed input data; ensure email format and other fields are correct.
- To resolve errors, check the API key validity, confirm required fields are provided, and verify tag selections.