Encharge icon

Encharge

Basic Encharge Node

Actions4

Overview

This node integrates with the Encharge platform to manage contacts (referred to as "people"). Specifically, the Delete Contact operation allows users to remove a contact from their Encharge account by specifying the contact's email address. This is useful in scenarios where you want to automate cleanup of your contact list, remove unsubscribed users, or synchronize contact data by deleting outdated entries.

For example, you might use this node in a workflow that processes bounced emails or unsubscribes and automatically deletes those contacts from Encharge to keep your marketing lists clean.

Properties

Name Meaning
Authentication Method of authentication; currently supports only "API Key" authentication.
Email The email address of the contact to delete. This uniquely identifies the contact.

Output

The node outputs a JSON object indicating the success of the deletion operation. The output structure is:

{
  "success": true
}

This confirms that the contact was successfully deleted. There is no additional data returned about the deleted contact.

The node does not output any binary data.

Dependencies

  • Requires an active Encharge account.
  • Requires an API key credential for authenticating requests to the Encharge API.
  • The node makes HTTP DELETE requests to the /people endpoint of the Encharge API, passing the contact's email as a query parameter.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent email will likely result in the contact not being found or deleted.
    • Missing or incorrect API key authentication will cause authorization errors.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Errors thrown by the API (e.g., unauthorized, not found) will be surfaced by the node.
    • If the node is set to continue on failure, error details will be included in the output JSON under an error property.

  • Resolutions:

    • Verify the email address is correct and exists in Encharge.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion