Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
This node is designed to manage contacts within a mailing or subscriber list system, specifically focusing on unsubscribing a contact by their email address. It is useful in scenarios where you want to programmatically remove or unsubscribe users from your mailing lists based on their email, such as when processing unsubscribe requests or cleaning up inactive subscribers.
A practical example would be integrating this node into a workflow that handles unsubscribe requests received via a web form or email, ensuring the contact is promptly removed from future mailings.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address of the contact to unsubscribe. This is a required string input where you enter the email of the subscriber to be unsubscribed. |
Output
The node outputs JSON data representing the result of the unsubscribe operation. Typically, this will include confirmation details such as success status and possibly information about the unsubscribed contact. If the node supports binary data output (e.g., logs or reports), it would relate to the unsubscribe action's metadata, but no explicit binary output is indicated here.
Dependencies
- Requires an API key or authentication token for the external mailing/subscriber service.
- Needs proper configuration of credentials within n8n to authenticate API calls.
- Depends on internal methods and routing logic defined in bundled dependencies (
./methods,./actions/node.description,./actions/router).
Troubleshooting
Common issues:
- Invalid or missing email address input will likely cause the unsubscribe operation to fail.
- Authentication errors if the API key or credentials are not set correctly.
- Network or API endpoint issues could prevent successful communication with the external service.
Error messages:
- Errors related to invalid email format should prompt checking the input value.
- Authorization errors indicate problems with the configured API credentials.
- Timeout or connection errors suggest network issues or incorrect API URLs.
Resolving these typically involves verifying the input email, ensuring valid and active API credentials, and confirming network connectivity.
Links and References
- Refer to the external mailing service’s API documentation for unsubscribe endpoints.
- n8n documentation on setting up API credentials and handling HTTP request nodes may be helpful.