# Create Ghost email format via API

**URL:** <https://forum.ghost.org/t/create-ghost-email-format-via-api/60906>\
**Category:** Developer help\
**Created:** [November 15, 2025, 11:24pm UTC](https://forum.ghost.org/t/create-ghost-email-format-via-api/60906 "2025-11-15T23:24:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![timbenz](https://avatars.discourse-cdn.com/v4/letter/t/bbce88/32.png) [@timbenz](https://forum.ghost.org/u/timbenz)\
**Post date:** [November 15, 2025, 11:24pm UTC](https://forum.ghost.org/t/create-ghost-email-format-via-api/60906/1 "2025-11-15T23:24:44Z")

</div>

I’m trying to create emails based on Ghost posts, but not send them via Mailgun, so I want the email format, as produced by the Ghost renderer from posts. I can’t see how this is possible to do via API endpoints, so is the only way via installing various npm packages locally and rendering it the proper format locally from the post HTML/lexical via a custom node script?

---

<div class="post-metadata">

**Author:** ![KBExit](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kbexit/32/38359_2.png) [@KBExit](https://forum.ghost.org/u/KBExit)\
**Post date:** [November 16, 2025, 3:36am UTC](https://forum.ghost.org/t/create-ghost-email-format-via-api/60906/2 "2025-11-16T03:36:19Z")

</div>

Have you looked into selfhosting n8n?  
They have SMTP Nodes available where you just put connection details in and you’re done. You can set a webhook or RSS event from Ghost to then output in an email to distribute to a list. You can even pull user information from Ghost webhooks.

Other solution is using Zapier but that can get costly in comparison to running your own n8n instance.

---

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [November 16, 2025, 8:22am UTC](https://forum.ghost.org/t/create-ghost-email-format-via-api/60906/3 "2025-11-16T08:22:01Z")

</div>

Ghost doesn’t save or expose the HTML for the emails anywhere, no. If the only use case is avoid sending via Mailgun you could look into some proxies that are floating around. For example:

> **[GitHub - tilak999/mailgun-ses-proxy: Proxy server to use AWS SES instead of mailgun in...](https://github.com/tilak999/mailgun-ses-proxy)**
>
> Proxy server to use AWS SES instead of mailgun in ghost CMS

It’s specific to SES, but could be a good starting point to customise this.

> [@KBExit](#):
>
> Have you looked into selfhosting n8n?

Since it seems like OP wants the Ghost email format, that won’t achieve that goal though. If the format is irrelevant that’s an option, of course.