One-Click Export: Send Designs to Any ESP Instantly

Sarah Chen

Email Strategy Lead at MiN8T

Published April 2026

1 Overview

One-click export is the bridge between designing an email and sending it. With MiN8T, you build your email once using the drag-and-drop editor, then push the finished design directly to any of 108+ email service providers, CRMs, transactional platforms, and e-commerce systems -- without copying HTML, without reformatting, without leaving the editor.

The traditional workflow for getting an email from a design tool into your sending platform involves exporting HTML, downloading a file, navigating to your ESP, creating a new campaign, pasting the HTML, fixing whatever broke during the paste, and testing again. That process takes 10-15 minutes per email and introduces errors at every step.

MiN8T eliminates all of that. When you click export, the platform handles HTML optimization, CSS inlining, platform-specific formatting adjustments, and delivery to your chosen ESP's API. Your email arrives in your sending platform ready to send, with all formatting intact.

2 How It Works

The export flow is three steps:

1. Connect your ESP once. Navigate to Settings → Integrations, find your platform in the grid, and authenticate. Most platforms use OAuth, so you click "Connect," authorize in a popup, and you are done. API key-based platforms ask you to paste a key.
2. Design your email. Use the drag-and-drop editor as usual. Add blocks, edit text, upload images, set responsive breakpoints -- the full editing experience.
3. Click export. Open the export panel, select your connected ESP from the dropdown, choose a destination (list, campaign, folder -- varies by platform), and click "Export." MiN8T compiles the HTML, applies platform-specific optimizations, and pushes the email via the ESP's API.

Behind the scenes, the export engine performs several optimizations before delivery:

• CSS inlining -- all styles are moved to inline attributes for maximum email client compatibility
• Image optimization -- images are served from a global CDN with responsive sizing hints
• Platform-specific adjustments -- certain ESPs have quirks (Outlook conditional comments, Gmail CSS stripping, Yahoo margin handling). MiN8T applies the right fixes for each target.
• HTML minification -- unnecessary whitespace and comments are stripped to reduce email weight
• Link tracking preparation -- links are structured so your ESP's tracking system can wrap them cleanly

3 Supported Platforms

MiN8T supports 108+ platforms across four categories. Here are the most popular in each:

Email Marketing

CRMs

Transactional

E-Commerce

4 Custom Export via Webhooks

If your sending platform is not in the built-in integration list -- or if you want to push email designs into your own internal systems, a custom CMS, or an automation platform like Make.com or Zapier -- you can set up a custom export webhook.

When configured, MiN8T sends the complete email package (HTML, JSON structure, metadata) to your specified URL whenever an export is triggered. This gives you the same one-click experience as the built-in integrations, but with your own endpoint receiving the data.

Setting up a custom export webhook

1. Navigate to Settings → Developer Tools → Webhooks
2. Click Create Webhook
3. Enter your endpoint URL (must accept POST requests and return a 2xx response)
4. Select the export.completed event
5. Save the webhook and copy the signing secret (displayed once)
6. Test with the Send Ping button to verify your endpoint receives data correctly

From that point on, every time you export an email, MiN8T sends a POST request to your URL with the full export payload. Your endpoint can then route the email to any system you need -- an internal email platform, a custom CMS, a staging environment for review, or a third-party service.

5 Export Data Format

When MiN8T sends an export to your webhook endpoint, the payload includes everything you need to recreate, store, or forward the email design:

{
  "event": "export.completed",
  "timestamp": "2026-04-03T14:22:00.000Z",
  "data": {
    "designId": "tpl_a1b2c3d4e5f6",
    "designName": "April Newsletter",
    "tags": ["newsletter", "monthly"],
    "status": "approved",
    "subject": "Your April roundup is here",
    "preheader": "New features, tips, and community highlights",
    "html": "<!DOCTYPE html><html>...full email HTML...</html>",
    "json": { "...MiN8T editor JSON structure..." },
    "editUrl": "https://app.min8t.com/editor/tpl_a1b2c3d4e5f6",
    "exportedBy": "designer@company.com",
    "exportTarget": "webhook"
  },
  "signature": "sha256=a1b2c3d4..."
}

6 Webhook Headers & Security

Every webhook request from MiN8T includes standard headers and a cryptographic signature so you can verify the request is authentic and has not been tampered with.

Request headers

HMAC-SHA256 signature verification

The X-MiN8T-Signature header contains a SHA-256 HMAC of the raw request body, computed using the signing secret that was displayed when you created the webhook. Always verify this signature before processing the payload to prevent spoofed requests.

const crypto = require('crypto');

function verifySignature(payload, signature, secret) {
  const expected = 'sha256=' + crypto
    .createHmac('sha256', secret)
    .update(payload, 'utf8')
    .digest('hex');

  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(expected)
  );
}

// In your Express route handler:
app.post('/webhooks/min8t', express.raw({ type: 'application/json' }), (req, res) => {
  const signature = req.headers['x-min8t-signature'];
  const isValid = verifySignature(req.body, signature, process.env.MIN8T_WEBHOOK_SECRET);

  if (!isValid) {
    return res.status(401).json({ error: 'Invalid signature' });
  }

  const event = JSON.parse(req.body);
  // Process the export...
  res.status(200).json({ received: true });
});

import hmac
import hashlib

def verify_signature(payload: bytes, signature: str, secret: str) -> bool:
    expected = 'sha256=' + hmac.new(
        secret.encode('utf-8'),
        payload,
        hashlib.sha256
    ).hexdigest()
    return hmac.compare_digest(signature, expected)

# In your Flask route:
@app.route('/webhooks/min8t', methods=['POST'])
def handle_webhook():
    signature = request.headers.get('X-MiN8T-Signature', '')
    if not verify_signature(request.data, signature, WEBHOOK_SECRET):
        return jsonify({'error': 'Invalid signature'}), 401

    event = request.get_json()
    # Process the export...
    return jsonify({'received': True}), 200

7 Step-by-Step Example

Let's walk through a practical example: exporting an email from MiN8T to Postmark via a Make.com webhook, so the email is automatically created as a Postmark template whenever you export from the editor.

Step 1: Create a Make.com scenario

In Make.com, create a new scenario and add a Custom Webhook trigger module. Copy the webhook URL that Make.com generates (it will look like https://hook.make.com/abc123...).

Step 2: Register the webhook in MiN8T

1. Go to Settings → Developer Tools → Webhooks
2. Click Create Webhook
3. Name it "Make.com → Postmark"
4. Paste the Make.com webhook URL
5. Select the export.completed event
6. Click Create

Step 3: Add Postmark module in Make.com

After the webhook trigger, add a Postmark → Create Template action module. Map the fields from the MiN8T webhook payload:

Step 4: Test the flow

1. In MiN8T, open any email design
2. Click Export in the top toolbar
3. Select your webhook from the export options
4. Click Export
5. Check Make.com -- the scenario should show a successful execution
6. Check Postmark -- the template should appear in your templates list

The entire flow takes about 2-3 seconds from the moment you click export. From here, you can extend the Make.com scenario to add Slack notifications, update a project management board, log to a spreadsheet, or trigger any other downstream action.