Mailgroup

Interact with a mailgroup instance

Actions15

List Actions
Setting Actions
- Update Settings
- Test Smtp Settings
Subscriber Actions

Overview

The "Modify a Subscriber" operation in the Mailgroup node allows users to update details of an existing subscriber within a mailgroup system. This includes changing the subscriber's email, status, list memberships, and custom attributes. It is useful for maintaining accurate subscriber data, managing subscription preferences, and ensuring that mailing lists are up-to-date.

Practical examples:

Updating a subscriber’s email address after they notify you of a change.
Changing a subscriber’s status to "disabled" if they opt out.
Adding or removing subscribers from specific mailing lists.
Modifying subscriber attributes such as name, preferences, or other metadata.

Properties

Name	Meaning
Name	The display name for the operation context; used internally to identify the action (required).
Subscriber ID	The unique numeric identifier of the subscriber to modify (required).
Email	The subscriber's email address to update.
Status	The subscriber's status; options are: "Enabled", "Disabled", or "Blocklisted".
Lists	JSON array specifying the mailing lists to which the subscriber should be added.
Attributes	JSON object containing key-value pairs of subscriber attributes to update or add.
Preconfirm Subscriptions	Boolean flag indicating whether subscriptions should be marked as confirmed immediately, bypassing double opt-in emails.

Output

The node outputs JSON data representing the updated subscriber information after modification. This typically includes fields such as subscriber ID, email, status, lists, and attributes reflecting the new state of the subscriber record.

If binary data output is supported by the node (not indicated here), it would represent attachments or related files, but this operation focuses on JSON subscriber data only.

Dependencies

Requires connection to a Mailgroup API instance.
Needs credentials including domain URL, username, and password for authentication.
The base URL for API requests is constructed from the provided domain credential.
The node expects the API to support JSON-formatted requests and responses.

Troubleshooting

Invalid Subscriber ID: If the subscriber ID does not exist, the API may return an error indicating the subscriber was not found. Verify the ID before attempting modification.
Authentication Errors: Incorrect or missing credentials will cause authentication failures. Ensure the API credentials are correctly configured.
Malformed JSON: The Lists and Attributes properties require valid JSON input. Invalid JSON syntax will cause request failures.
Status Value Errors: Only the specified status options ("Enabled", "Disabled", "Blocklisted") are accepted. Using unsupported values will result in errors.
Preconfirm Flag Misuse: Setting Preconfirm Subscriptions incorrectly might lead to unexpected subscription confirmation behavior. Use carefully according to your subscription workflow.

Links and References

Mailgroup API documentation (generic reference): Consult your Mailgroup service provider's API docs for detailed endpoint and payload specifications.
JSON formatting guides: Useful for preparing valid JSON inputs for lists and attributes fields.
n8n documentation on credential setup and HTTP request nodes for configuring API connections.