Encharge icon

Encharge

Basic Encharge Node

Actions4

Overview

This node integrates with the Encharge platform to manage contact records. Specifically, the "Update Contact" operation allows users to update details of an existing contact identified by their email address. This is useful in scenarios where you want to keep your contact data synchronized or enriched with new information such as name, IP address, tags, or custom fields.

Practical examples include:

  • Updating a contact's name and IP address after they submit a form.
  • Adding or modifying tags on a contact based on their behavior or status.
  • Changing user identifiers or UTM source parameters for marketing attribution.

Properties

Name Meaning
Authentication Method of authentication; currently supports "API Key".
Email The unique email address identifying the contact to update (required).
Update Fields Collection of fields to update on the contact:
- IP Address: Contact's IP address (IPv4 or IPv6).
- Name: Full name of the contact.
- userId: User identifier string.
- firstName: Contact's first name.
- lastName: Contact's last name.
- utm_source: UTM source parameter (default "ABCD").
- first_utm_source: First UTM source parameter (default "n8n").
- Tag Names or IDs: Tags to assign to the contact; can be selected from a list or specified via expression.

Output

The node outputs JSON data indicating the success of the update operation. The output JSON has the structure:

{
  "success": true
}

This confirms that the contact was updated successfully. No detailed contact data is returned by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Encharge API.
  • Uses the Encharge REST API endpoint /people with POST method to perform updates.
  • The node dynamically loads available tags from the /tags-management endpoint to assist tag selection.

Troubleshooting

  • Common issues:

    • Providing an incorrect or missing email will cause the update to fail because the email uniquely identifies the contact.
    • Invalid or expired API key will result in authentication errors.
    • Attempting to update with invalid field formats (e.g., malformed IP address) may cause API rejection.

  • Error messages:

    • Errors returned from the Encharge API are propagated. For example, "Unauthorized" indicates an issue with the API key.
    • "Contact not found" or similar messages indicate the email does not exist in Encharge.

  • Resolutions:

    • Verify the email is correct and exists in Encharge.
    • Ensure the API key is valid and has necessary permissions.
    • Validate input fields conform to expected formats before updating.

Links and References

Discussion