← All Workflows

Generate OG images for every post in your Notion blog database

New or updated posts get a fresh open graph image, with the URL written back to the page for your site to use.

See all workflows
Trigger1New/updated page in NotionRun when a page is added or edited in a database.
Render2How to Build — Dev Tutorial Blog OG ImageExample template. Swap in your own design.
Destination3Write to NotionWrite results (like the render URL) back to the source page.

OG images straight from your Notion posts

If your blog runs on a Notion database, its Open Graph images should come from the same place. Rather than hand-making a social card per post, let this workflow render one from each post's own title and author, then write the image URL back onto the page so your site can read it.

How it works

  1. A post is added or edited in your Notion blog database. Publishing a new page or changing a title triggers the run, so nothing goes stale.
  2. An Open Graph image is rendered from the page's title and author, dropped into your 1200 x 630 template. Long titles auto-fit rather than overflowing, which is the usual failure of homegrown OG endpoints.
  3. The image URL is written back onto the post page. Your site already pulls posts from Notion, so it reads that field straight into the og:image tag when it builds.

Where it helps

Because the card is a visual template, redesigning it later means editing the template, not touching your site code. The next edit picks it up. A correct card matters wherever a link travels:

  • Search snippets, where a clean card lifts the result above a gray box.
  • Social shares, so a post on X or LinkedIn shows the title, not a broken preview.
  • Link previews in Slack, iMessage, and other chat apps that read og:image directly.

How it works, step by step

  1. Design your OG template

    Build one 1200 x 630 template in the studio with placeholders for the post title and author, plus any badge or cover art your cards show.

  2. Connect your Notion blog database

    Link the Notion database your posts live in. The workflow watches it and runs when a page is added or edited.

  3. Map post properties to the template

    Point the title and author placeholders at the matching properties on the post page so each render uses that post's own values.

  4. Write the image URL back

    The finished image URL is written onto the post page, ready for your site to read into the og:image tag when it builds.

Integrations in this workflow

Connect these apps once and the workflow moves your data through them automatically.

Frequently asked

How do I generate OG images for posts in Notion?

Keep your posts as pages in a Notion database and design one 1200 x 630 template. When a page is added or edited, Orshot renders an Open Graph image from its title and author and writes the image URL back onto the page. Your site reads that URL into its og:image tag.

Does it re-render when I edit a post?

Yes. The workflow runs on new and edited pages, so changing a title or author produces a fresh image and updates the URL on the page. Publish-only edits stay in sync without a manual re-run.

Where does the finished image go?

The image URL is written back to a property on the post page. Your site pulls posts from Notion already, so it reads that field into og:image with no extra service to call.

What size should the OG image be?

1200 x 630 pixels is the standard across X, LinkedIn, Facebook, and chat apps. Design the template at that size and every render comes out correct, with long titles auto-fitting instead of overflowing.

Do I need to write code?

Almost none. You map two properties and add one field to your Notion schema for the image URL. Your site already renders from Notion, so reading one more field into the head is a small change.