Run newsletters in WordPress and use EmailDesk only for delivery.

1. Prepare EmailDesk and WordPress

In EmailDesk, confirm the customer has API email sender access, a verified From address, the required sender DNS, and a normal API access token. The plugin does not require WordPress-specific marketing scopes and does not read or write the EmailDesk Marketing workspace.

The From email used by WordPress must belong to a domain allowed by that key, for example info@example.com. Use a form visitor's address in Reply-To, not as an unverified From address.

2. Download WP EmailDesk Sender

Download the latest plugin ZIP from EmailDesk:

https://app.emaildesk.bd/api/downloads/wordpress-plugin?v=2.3.0

Release 2.3.0, published 2026-08-22. SHA-256: BDD7D1DA07C18CF17D12E7CAE5F2A4C426ECE76F4C88D98EFB53C800EF4915A3

3. Install in WordPress

Open WordPress Admin, then go to Plugins > Add New > Upload Plugin. Upload wp-emaildesk-sender-2.3.0.zip, select Install Now, and activate WP EmailDesk Sender.

After activation, open EmailDesk > Configuration. Lists, subscribers, forms, templates, campaigns, and reports remain in this WordPress installation.

4. Configure the delivery connection

Use these values in the plugin settings page:

API endpoint: https://app.emaildesk.bd/api/v1/send
API access token: paste the one-time key created in EmailDesk
From email: info@example.com
From name: Your website or company name
Gateway profile name: optional, for example MailChannels
Timeout seconds: 20
Failure behavior: keep fallback enabled during first setup

Click Save configuration, run Check local storage, and then use Send transactional test to verify that EmailDesk accepts the token and sender.

5. Prepare subscribers and lists

Add or import consented subscribers, organize them into active local lists, and configure any local subscription forms or confirmation flow the site needs. Confirm that unsubscribe links and eligibility state work before preparing a campaign.

These records do not appear in EmailDesk Marketing. Back up the WordPress database using the site's normal operating procedure because WordPress is authoritative for the plugin's marketing data.

6. Build and check a campaign

Create a campaign from a local template or blank email, choose one or more active lists, set the sender, and run the plugin's content and link checks. Send a test to an address you control before queueing.

The plugin deduplicates subscribers shared by selected lists and rechecks consent, subscription state, and local eligibility before delivery.

7. Queue now or schedule

Queue the campaign immediately or choose a scheduled time. WordPress cron owns the campaign queue and sends paced batches; EmailDesk receives one generic delivery request at a time. A site that disables normal WordPress cron triggering needs a reliable server cron for wp-cron.php.

8. Review results and troubleshoot failures

A test or campaign delivery can fail because the access token is wrong, disabled, or belongs to another customer; the From domain is not allowed; sender DNS is incomplete; the account is suspended; a quota or rate limit applies; or the selected gateway refuses the message.

Use the WordPress campaign report and local delivery queue first. For a delivery request that reached EmailDesk, use Outbound History to inspect sender, policy, quota, queue, and provider evidence. Enable the plugin debug log only while investigating and never publish the access token.

A successful EmailDesk queue or provider handoff is evidence of that stage, not a guarantee of final delivery or inbox placement. WordPress remains authoritative for the plugin's subscriber, campaign, unsubscribe, and local delivery records.