Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Subscriber → Manage Subscriber List
AI-generatedOverview
The node integrates with a list management and email marketing system, allowing users to manage subscribers within mailing lists. Specifically, the "Manage Subscriber List" operation enables adding, removing, or unsubscribing subscribers from one or more lists. This is useful for maintaining targeted mailing lists, updating subscriber statuses, and managing subscription preferences efficiently.
Practical examples include:
- Adding new subscribers to specific mailing lists after they sign up on a website.
- Removing subscribers who have requested to be deleted from certain campaigns.
- Marking subscribers as unsubscribed when they opt out of receiving emails.
Properties
| Name | Meaning |
|---|---|
| Subscriber IDs | A JSON array of subscriber identifiers to be managed (added, removed, or unsubscribed). |
| Action | The action to perform on the subscribers: Add them to lists, Remove them from lists, or Unsubscribe them. Options: Add, Remove, Unsubscribe. |
| List IDs | A JSON array of list identifiers where the subscribers will be added or removed. |
| Subscription Status | The status to assign to the subscriber(s) when managing their subscription. Options: Confirmed, Unconfirmed, Unsubscribed. |
Output
The node outputs JSON data representing the result of the subscriber list management operation. This typically includes confirmation of the performed action, such as successful addition, removal, or unsubscription of subscribers, along with any relevant metadata returned by the API.
If binary data is output (not indicated in this case), it would generally represent attachments or media related to campaigns or subscribers, but this operation focuses on JSON responses.
Dependencies
- Requires connection to a list management and email marketing service via its API.
- Needs an API authentication credential consisting of a domain URL, username, and password.
- The base URL for API requests is constructed from the provided domain credential.
- Proper permissions on the API to manage subscribers and lists are necessary.
Troubleshooting
- Invalid Subscriber or List IDs: Ensure that the subscriber and list IDs provided are valid and exist in the system; otherwise, the API may return errors or fail silently.
- Authentication Errors: Incorrect credentials will prevent the node from connecting to the API. Verify the API key or username/password combination.
- Action Not Allowed: Some actions might require specific permissions; if unauthorized, check user roles and API access rights.
- Empty Arrays: Providing empty arrays for subscriber or list IDs may result in no operation being performed; ensure these fields contain valid data.
- Subscription Status Mismatch: Using an inappropriate subscription status for the action might cause unexpected behavior; use the status options as intended.
Links and References
- Refer to the official documentation of the list management and email marketing API you are integrating with for detailed information on subscriber and list management endpoints.
- n8n documentation on creating and using custom nodes for API integrations.