SnapSharp + Notion

Notion is the workspace tool of choice for thousands of product, growth, and ops teams — but its built-in URL preview is famously basic. SnapSharp closes that gap. Combine the official Notion API with SnapSharp's screenshot and metadata-extract endpoints to render a real visual preview for every URL in a database, generate branded OG cards for content calendars, attach PDF snapshots to meeting notes, and run scheduled visual diffs against pages your team owns. There is no Notion-side installation — you wire the two APIs together via Zapier, Make, n8n, or a small backend script. This page walks through the recommended pattern, the few quirks of Notion's `files` and `external` block types, and how this compares to standalone Notion enrichment apps.

How it works

A typical end-to-end flow takes 1–3 seconds.

1. 1

   New row added to Notion DB

   A teammate (or an upstream automation) creates a row containing a URL.

2. 2

   Webhook or poll fires

   A Notion-aware automation step (Zapier/Make/n8n/your backend) detects the new row.

3. 3

   SnapSharp renders the asset

   The automation calls `/v1/screenshot` (or `/v1/og-image`, `/v1/extract`) with the URL from the row.

4. 4

   Result writes back to Notion

   The image is uploaded to Notion via the `external` files API and the row is updated with the live preview.

Setup guide

Follow these steps in order. Each one stands alone, so you can copy code blocks directly without re-reading earlier ones.

1. 1Create a Notion internal integration

   In Notion, go to https://www.notion.so/my-integrations → "New integration". Choose "Internal" type, give it a name, and copy the secret. Share the target database with this integration so it can read/write rows.

2. 2Pick your automation layer

   Three good options — Zapier (cheapest in dev time, most expensive at scale), Make (cheap and fast), n8n (self-hosted, free at scale), or a small Node/Python script. The rest of this guide assumes Make because it offers the best price/effort balance.

3. 3Add a "Notion → Watch Database Items" trigger

   In Make, the Notion trigger polls a database and fires per new row. Map the row's URL property as the trigger output that downstream modules will consume.

4. 4Call SnapSharp to render the image

   Drop a SnapSharp "Take Screenshot" module after the Notion trigger. Map the URL property to SnapSharp's `url` input. Set width 1200, full_page false (Notion previews look best at viewport-only), format png.

   POST https://api.snapsharp.dev/v1/screenshot
   Authorization: Bearer ss_live_xxx
   Content-Type: application/json
   
   {
     "url":          "{{notion.url_property}}",
     "width":        1200,
     "format":       "png",
     "block_ads":    true,
     "upload_to_s3": true
   }
   

5. 5Update the Notion row with the preview

   Add a Notion "Update Database Item" module. Map the SnapSharp `image_url` into a Files & Media property using the "external URL" upload mode — Notion will fetch and host the file itself.

   // Notion API call (auto-generated by Make):
   PATCH /v1/pages/{{page_id}}
   {
     "properties": {
       "Preview": {
         "files": [{
           "type": "external",
           "name": "preview.png",
           "external": { "url": "{{snapsharp.image_url}}" }
         }]
       }
     }
   }
   

6. 6Schedule it and forget it

   Turn on the Make scenario. Every new row gets an auto-generated preview within seconds. Optional follow-up — schedule a daily "refresh" job that re-renders rows older than N days so screenshots stay current.

Trigger examples

Real-world patterns where Notion fires and SnapSharp produces the asset.

Action examples

Each card shows the operation and the inputs you'd typically map from upstream.

url: {{row.url}}
width: 1200
block_ads: true

template_id: editorial-card
variables.title: {{row.title}}
variables.author: {{row.author}}

url: {{row.url}}
format: pdf

url: {{row.url}}

Limitations to know

• •Notion has no native screenshot block — every preview must be uploaded as either an external file URL or a hosted Notion file. Both work, both have ~5MB practical limits.
• •The Notion API rate-limits at 3 requests/sec per integration. Bulk backfills should batch and back off accordingly.
• •Notion's "external file" preview occasionally re-fetches the source URL. If the SnapSharp CDN URL ever moves, regenerate via your automation.

How SnapSharp compares to other apps in Notion

Quick reference — every alternative listed below is also available in Notion.

FAQ