Prepare a MailPoet newsletter
Create a newsletter draft and check its content and audience in MailPoet.

Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro, a connected practice site and the supported plugin active.
- Permission to edit the plugin and fictional practice records.
- MailPoet 5.x and a sender/test inbox you control.
Let’s do this, step by step.
Step 01
Enable and inspect the integration
Open EMCP Tools → Tools → Plugins → MailPoet. Check dependencies and Read/Write switches, enable needed actions and Save changes. Reconnect and request get-setup.
Open EMCP Tools, Tools, then Plugins. Find MailPoet, check its requirements and enable the actions needed here. Choose Save changes and reconnect. Ask the AI to read the setup before changing anything.
Step 02
Check setup and audience
Read sender, sending method, double opt-in and lists. Preserve consent and synced WordPress identities.
Check the sender, sending method and confirmation settings. Choose a practice list. Adding someone must not override an unsubscribe or confirmation requirement. Synced profiles keep their identity from WordPress.
Step 03
Create a standard draft
Create a standard newsletter with internal name, subject, audience and native block content. Keep run_automations false for related subscriber edits.
Create a standard newsletter draft with a useful name and subject. Use MailPoet’s email blocks. Keep automations off when preparing test subscribers or tags.
Step 04
Preview in MailPoet
Inspect the native editor, responsive layout, images, buttons and footer. Read the newsletter version and recipient count.
Open the draft in MailPoet’s editor. Check images, text, buttons and footer, including the small-screen preview. Read the recipient count before any send.
Step 05
Request a controlled test
An explicitly approved send-test-email requires confirmation and goes to the connected user’s own address; leave the newsletter draft.
If you want a test, explicitly request and confirm one to your own address. Check it in the inbox. Leave the main newsletter in draft while you finish reviewing.
Step 06
Understand later scheduling
Production sends need confirm and matching expected_recipients from get-recipient-count. Use site-local time; uncountable dynamic audiences use MailPoet. Near sending time pause rather than unschedule.
Before a production send, confirm the audience again. Some dynamic audiences cannot be counted by this tool; use MailPoet for those. An imminent send may need pausing instead of unscheduling. Messages already sent cannot be undone.
You’re done when…
The newsletter is editable in MailPoet, its audience is checked and it remains a draft without a separate send approval.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.
A brief becomes a real page.