Actions30
- Campaign Actions
- List Actions
- Template Actions
- Subscriber Actions
- List Segment Actions
- Transactional Email Actions
Subscriber → Create Bulk
AI-generatedOverview
This node operation allows bulk creation of subscribers in a specified MailWizz list. It accepts a JSON array of subscriber objects and supports setting a default subscriber status if not provided in the payload. Additionally, it can automatically confirm subscribers after creation if the status is set to confirmed. Metadata such as confirmation IP, opt-in IP, registration IP, timestamp, and source can also be applied to each subscriber. This operation is useful for efficiently adding multiple subscribers to a mailing list in one request, such as importing contacts from another system or batch processing new sign-ups.
Use Case Examples
- Importing a list of new subscribers from a CRM system into a MailWizz mailing list.
- Batch adding event attendees as subscribers to a newsletter list with a default confirmed status.
- Automatically confirming subscribers after bulk creation to bypass double opt-in when appropriate.
Properties
| Name | Meaning |
|---|---|
| List ID | Identifier of the list that the subscribers will be added to. |
| Subscribers | JSON array of subscriber objects to create in MailWizz. |
| Subscriber Status | Status to apply to subscribers if not explicitly provided in the payload. |
| Force Confirm | Confirm each subscriber after bulk creation when status is set to confirmed. |
| Metadata | Additional metadata to apply to each subscriber such as confirmation IP, opt-in IP, registration IP, timestamp, and source. |
Output
JSON
json- Response data from MailWizz API after bulk subscriber creation, including details of created subscribers and operation status.
Dependencies
- MailWizz API with appropriate credentials for authentication.
Troubleshooting
- Ensure the List ID is valid and exists in MailWizz; otherwise, the operation will fail with a 'List not found' error.
- Subscribers JSON must be a valid JSON array of subscriber objects; invalid JSON will cause parsing errors.
- If 'Force Confirm' is enabled, the node attempts to confirm each subscriber after creation; network or API errors during confirmation may cause partial failures.
- The subscriber status must be one of the supported values; unsupported statuses may cause API errors.
- Check that metadata fields, if provided, are correctly formatted (e.g., valid IP addresses and timestamps).