Overview
This node interacts with the Mailwizz API to create email campaigns. It is useful for automating email marketing workflows, such as sending newsletters or autoresponder campaigns based on WordPress post data. For example, it can create a campaign using a specified template, schedule it for sending, and optionally map WordPress categories to Mailwizz lists and segments for targeted email distribution.
Use Case Examples
- Create a regular email campaign with a custom subject and send it to a specific Mailwizz list and segment.
- Create an autoresponder campaign that uses WordPress post titles as the email subject and passes WordPress post data (like featured image, excerpt, and link) to the email template.
- Map WordPress categories to different Mailwizz lists and segments to send targeted campaigns based on post categories.
Properties
| Name | Meaning |
|---|---|
| Name | Name of the campaign (required) |
| Type | Type of the campaign, either Regular or Autoresponder |
| From Name | Sender's name for the campaign (required) |
| From Email | Sender's email address for the campaign (required) |
| Subject | Subject line of the campaign email (required, unless using WordPress post title as subject) |
| Reply To | Reply-to email address for the campaign (required) |
| Send At | Scheduled date and time to send the campaign (required) |
| Use Category Mapping | Whether to map WordPress categories to specific Mailwizz lists and segments |
| List | Mailwizz list to send the campaign to (required if category mapping is disabled) |
| Segment | Mailwizz segment to send the campaign to (optional, depends on selected list) |
| Category Mapping | Mappings from WordPress categories to Mailwizz lists and segments (required if category mapping is enabled) |
| Default List | Default Mailwizz list to use if no category mapping matches (required if category mapping is enabled) |
| Default Segment | Default Mailwizz segment to use if no category mapping matches (optional) |
| WordPress Categories Field | Field name in WordPress data containing categories (e.g., 'categories') |
| URL Tracking | Whether to track URLs in the campaign |
| Template | Template to use for the campaign (required) |
| Use WordPress Data for Subject | Whether to use WordPress post title as the campaign subject |
| WordPress Post Field for Subject | Field from WordPress post to use as subject (e.g., 'post_title') |
| Pass WordPress Data to Template | Whether to pass WordPress post data (featured image, excerpt, date, link) to the template |
| WordPress Post Fields | Field mappings for WordPress post data such as featured image, excerpt, date, link, and content |
Output
JSON
json- Response data from Mailwizz API for the created campaign or other requested resources
Dependencies
- Mailwizz API with API key credentials
Troubleshooting
- Ensure Mailwizz API credentials are correctly configured; missing credentials will cause errors.
- If using WordPress data for the subject, ensure the specified WordPress field exists in the input data to avoid errors.
- When using category mapping, verify that WordPress categories match the configured mappings to ensure correct list and segment selection.
- API errors from Mailwizz (e.g., invalid list or template IDs) will be returned in the node output; verify all IDs are correct.
Links
- Mailwizz API Documentation - Official documentation for Mailwizz API endpoints and usage.