Actions30
- Campaign Actions
- List Actions
- Template Actions
- Subscriber Actions
- List Segment Actions
- Transactional Email Actions
Campaign → Create
AI-generatedOverview
This node operation creates a new email campaign in MailWizz, a marketing automation platform. It allows users to define campaign details such as name, type, sender information, subject, sending schedule, and email template. The node supports integration with WordPress data for dynamic content and subject lines, URL tracking, and category-based list and segment mapping. It is useful for automating email marketing campaigns, especially when combining WordPress content with MailWizz mailing lists and templates.
Use Case Examples
- Creating a regular email campaign with a saved MailWizz template and scheduling it to send at a specific date and time.
- Creating an autoresponder campaign that uses WordPress post titles as email subjects and passes WordPress post data to the email template.
- Mapping WordPress categories to MailWizz lists and segments to target specific subscriber groups automatically.
Properties
| Name | Meaning |
|---|---|
| Campaign Name | The display name of the campaign, used to identify it in MailWizz. |
| Campaign Type | Type of campaign, either 'Regular' or 'Autoresponder'. |
| From Name | The sender's name displayed in the email. |
| From Email | The sender's email address. |
| Reply To | The email address where replies will be sent. |
| Send At | The scheduled date and time when the campaign will be sent. |
| Use WordPress Title for Subject | Whether to use the WordPress post title as the email subject. |
| Subject | The email subject line, used if not using WordPress title. |
| WordPress Subject Field | The WordPress field to use for the subject if enabled. |
| Track URLs | Whether to enable URL tracking in the campaign emails. |
| Pass WordPress Data to Template | Whether to pass WordPress post data fields to the email template for dynamic content. |
| WordPress Fields | Collection of WordPress post fields to map to the email template content. |
| Use Category Mapping | Whether to map WordPress categories to MailWizz mailing lists and segments. |
| Category Mapping | Mappings between WordPress categories and MailWizz lists and segments. |
| Default List | Default MailWizz list to use if no category mapping matches. |
| Default Segment | Default MailWizz segment to use if no category mapping matches. |
| WordPress Categories Field | The field in WordPress data containing categories. |
| List Selection Mode | How to select the MailWizz list: from dropdown or manual input. |
| List | MailWizz list selected from dropdown. |
| List Identifier | Manually provided MailWizz list UID or name. |
| Segment | MailWizz segment within the selected list. |
| Template Source | Source of the email template: saved template or custom HTML content. |
| Template | Selected saved MailWizz template ID. |
| Template HTML | Custom HTML content for the campaign email template. |
Output
JSON
json- The response data from MailWizz API representing the created campaign or operation result.
Dependencies
- MailWizz API with authentication credentials
Troubleshooting
- Ensure required fields like campaign name, from email, and list ID are provided to avoid errors.
- If using WordPress subject field, verify the field exists in the input data to prevent missing field errors.
- When using custom HTML content, ensure it includes required tags [UNSUBSCRIBE_URL] and [COMPANY_FULL_ADDRESS] to pass validation.
- If category mapping is enabled, ensure WordPress categories match the mapping entries to correctly assign lists and segments.
- API errors such as 404 indicate missing resources like lists or templates; verify identifiers are correct.
Links
- MailWizz API Documentation - Official API documentation for MailWizz used by this node.