I open-sourced the Notion Email rendering engine from my SaaS

강상권 — Sun, 05 Apr 2026 13:21:11 +0000

I've been running notionto.email, a service that
sends Notion pages as emails. The hardest part wasn't the Notion API or email
delivery. It was the rendering layer.

So I extracted it and open-sourced it: notion-to-email.

TL;DR

notion-to-email is a TypeScript library that turns any Notion page into
email-compatible HTML, ready to pass to SES, SendGrid, Resend, or Nodemailer.

import { renderFromNotion } from 'notion-to-email'

const { html, title } = await renderFromNotion({
  pageId: 'your-page-id',
  token: 'your-notion-token',
})
// Pass html to SES, SendGrid, Nodemailer, Resend, etc.

The rendering problem

Email HTML is notoriously finicky. No Flexbox. No Grid. Table-based layouts,
inline styles, and every client renders things slightly differently.

Notion's private images also use short-lived signed URLs, so you need to
re-host them before sending or they'll be broken by the time someone opens
the email.

Installation

npm install notion-to-email @notionhq/client

What's supported

20+ block types, all rendered to table-based email HTML:

Paragraphs, Headings H1–H4
Bulleted & Numbered Lists
To-Do, Toggle, Quote, Callout
Code blocks, Equations (image fallback)
Tables, Column layouts
Images, YouTube thumbnails, File links, Bookmarks
Synced blocks, Child pages/databases, Link to page, Table of Contents
Rich text: bold, italic, strikethrough, inline code, colors, links, mentions

Configuration

await renderFromNotion({
  pageId: 'your-page-id',
  token: 'your-token',
  options: {
    // Notion private images expire quickly. Re-host them before sending
    // so they're still visible when recipients open the email.
    // `context` contains { blockId, blockType, pageId, isPublicPage, usage }.
    // usage: 'image' | 'cover' | 'icon' | 'file'
    resolveImageUrl: (url, context) =>
      `https://your-cdn.com/proxy?url=${encodeURIComponent(url)}`,

    // Show a "View in Notion" button at the top of the email
    header: { showNotionButton: true },

    // Append a custom footer (raw HTML)
    footer: '<p>Sent via My App</p>',

    // 'placeholder' renders a visible fallback for unsupported blocks
    // instead of silently dropping them
    onUnsupportedBlock: 'placeholder',
  },
})

CLI

npx notion-to-email <page-id> --token secret_xxx
npx notion-to-email <page-id> -o email.html
npx notion-to-email https://notion.so/My-Page-abc123

GitHub: https://github.com/Sangkwun/notion-to-email
npm: https://www.npmjs.com/package/notion-to-email

MIT licensed. PRs and issues are always welcome.

I built a tool that turns RSS, YouTube, and Reddit into a single daily briefing

강상권 — Tue, 03 Mar 2026 08:44:08 +0000

Every morning I used to open the same 15 tabs. Tech blogs, YouTube channels, a couple of subreddits, some newsletters I'd subscribed to months ago and barely read.

It took about 40 minutes. Most of that time was spent skimming stuff I didn't need.

So I built Daigest.

What it does

You connect your sources (RSS feeds, YouTube channels, Reddit subs, whatever you follow) and Daigest generates a summarized briefing. Daily or weekly, your call.

The briefing is a single page, readable in about 3 minutes. Want to share it with your team? Send them the link.

That's pretty much it.

Why I built it

I tried RSS readers first, but my unread count just kept growing. Google Alerts sent me keyword matches with zero context. I subscribed to 30+ newsletters and actually read maybe 3. Tried just Googling stuff every morning, which works, but gets old fast.

None of these solved what I actually wanted: a short summary of what happened across my sources. Not another inbox.

How it works

Pick your sources (RSS, YouTube, Reddit, and more)
Daigest pulls new content and summarizes it with AI
You get a briefing, one page, readable in minutes
Share via link if your team needs it too

Tech stack

For anyone curious about what's under the hood:

Frontend: Next.js (App Router)
Backend: Supabase (Postgres + Auth + Edge Functions)
AI: Multiple LLMs for summarization
Hosting: Vercel

What I learned building this

Summarization quality was the hardest part. Early versions either missed important stuff or included too much noise. Took a lot of tweaking to get it right. Turns out prompt engineering matters way more than which model you pick.

The other surprise: people use this differently than I expected. I built it for myself (a developer who reads too many blogs), but most active users are actually sharing team briefings. PMs sending weekly industry updates, that kind of thing. Didn't see that coming.

Try it out

It's free to start: daige.st

If you try it, I'm curious what sources you'd connect first. Happy to hear what's missing too.

X (@daigestHQ) if you want to say hi.

DEV Community: 강상권