Turn your blog posts into a newsletter
Pick the posts. Get the issue back in three formats, with each blurb taken from the post's own summary. Send it from the list you already have.
Three steps.
-
01
Pick the posts
Your recent drafts, in a list. Tick them in the order you want them to read.
-
02
Add a title and an intro
Both optional. Left empty, the title names the lead story rather than the date.
-
03
Copy the format you need
Email HTML for a sender that takes it, Markdown for one that prefers it, plain text for the version that always works.
The hard part of a newsletter is never the writing — the posts exist. It is the twenty minutes of copying titles, writing a line about each one, finding the links and wrestling the whole thing into an email template that does not fall apart in Outlook. Which is why the newsletter is the thing that slips.
This does the assembling. Every blurb is the summary already written for that post when it was drafted, so nothing is invented and nothing needs re-checking. You get the issue as email HTML, as Markdown, or as plain text, and you send it from wherever your list already lives.
Turn your blog posts into a newsletter, answered.
No, and that is deliberate. Your list lives in Mailchimp, Kit, Ghost, beehiiv or whatever you already pay for, along with the subscribers, the deliverability and the unsubscribe handling. Recast builds the issue and hands it over.
Each post's own meta description — the one-sentence version written when the draft was made. Nothing is generated fresh, so there is nothing new to fact-check.
Nothing. Composing an issue is assembly rather than generation, so no credits are spent on it.
It is still included, and flagged, with the title shown as plain text instead of a link — because a link to nowhere in an email cannot be recalled. Publish it, or paste the address in yourself.
The HTML is table-based with inline styles, and the two Outlook dark-mode traps are handled: backgrounds are pinned as gradients and text colours are pinned with a text-fill, because Outlook rewrites the plain versions of both.
Not yet. beehiiv and Mailchimp both offer RSS-to-send on a schedule, and this is the manual version: you pick what goes in. That is the right order — an automation that mails the wrong post is worse than twenty minutes of picking.
Other things it turns into articles.
One recording is never one post.
The article is the start. The same source gives you the headline card, the social captions and a publishing slot, on your brand kit, without moving anything between tools.