Skip to main content

Custom HTML export

This guide covers Better Email's custom export path for teams that want Better Email to render the final HTML, but will paste, upload, or send that HTML outside a built-in ESP integration.

When to use custom HTML export​

Custom HTML export is the right choice when:

  • your ESP or delivery tool is not one of Better Email's built-in integrations
  • you need final rendered HTML for a manual workflow
  • you want to test output without connecting a live ESP account yet

How it works​

The custom export integration does not require API credentials.

Instead, it gives you a Better Email integration that can be used for rendered output without any external authentication step.

Important to know:

  • Better Email still renders merge tags and integration-specific output based on the integration type you choose.
  • The custom integration itself does not push content into another platform.
  • This is best for manual copy-paste, manual upload, QA, or unsupported ESP workflows.

Set up the integration in Better Email​

In Better Email:

  1. Go to Integrations.
  2. Create a new integration.
  3. Enter a clear name for the integration.
  4. Choose Custom as the type.
  5. Optional: under Access, restrict the integration to specific users or groups.
  6. Enable the integration.
  7. Save the integration.

Because no credentials are required, the integration is active as soon as it is enabled.

A good custom-export workflow looks like this:

  1. Build and review the email in Better Email.
  2. Render the final HTML through the custom integration.
  3. Copy or upload that HTML into the external system you use.
  4. Run the downstream QA you normally use in that platform.