Actions15
Overview
The node "Mailgroup" allows interaction with a mailgroup instance via its API. Specifically, the "Subscriber" resource with the "Get by Email" operation enables users to search for subscribers by their email address. Although the mailgroup system treats email addresses as unique identifiers internally, it does not provide a direct API endpoint to fetch a single subscriber by email. Instead, this operation returns a list of subscribers matching the given email, typically containing one element.
This node is useful in scenarios where you need to retrieve subscriber details based on their email address, such as verifying subscription status, fetching subscriber metadata, or integrating subscriber data into workflows that require email-based lookups.
Practical Example
- A marketing automation workflow that checks if an email address belongs to a subscriber before sending targeted campaigns.
- Customer support automation that retrieves subscriber information by email to assist with inquiries.
Properties
| Name | Meaning |
|---|---|
| Subscriber Email | The email address used to search for a subscriber. Although the system treats emails as unique, this operation returns a list of subscribers found. |
Output
The output contains a JSON field with a list of subscriber objects matching the provided email address. Typically, this list will contain a single subscriber object due to the uniqueness of email addresses in the mailgroup system.
If the node supports binary data output (not explicitly shown in the provided code), it would represent any associated binary content related to the subscriber, but this is not indicated here.
Dependencies
- Requires an API key credential for authenticating with the mailgroup API.
- The node configuration must include credentials specifying the domain URL, username, and password for basic authentication.
- The base URL for API requests is constructed from the provided domain credential, ensuring no trailing slash, appended with
/api.
Troubleshooting
- No subscribers returned: Ensure the email address is correct and exists in the mailgroup system.
- Authentication errors: Verify that the API credentials (domain, username, password) are correctly configured and have sufficient permissions.
- Empty list despite valid email: This might indicate synchronization issues or delays in the mailgroup backend; retry after some time.
- API connection failures: Check network connectivity and that the domain URL is reachable.
Links and References
- Mailgroup API documentation (not provided in source, but typically available from the service provider)
- n8n documentation on creating and using custom nodes with API credentials