How to Automate Notion to Slides: From One-Click Import to a Fully Hands-Off Pipeline

Quick Answer (≤60 words): You can automate Notion-to-slides at three levels. Level 1: connect Notion to 2Slides and generate a deck in one click. Level 2: trigger deck generation from Zapier, Make, or n8n when a Notion page changes. Level 3: a full API pipeline where every new Notion database entry calls the 2Slides API and returns a finished

.pptx

automatically - no human in the loop.

If you produce the same kind of deck over and over - weekly updates, per-client one-pagers, release notes, a deck per new database row - the manual version is a tax you pay forever. This guide shows how to automate it, from the simplest one-click flow to a pipeline that runs while you sleep.

If you're new to pulling slides from Notion at all, start with the basics in how to generate presentations from Notion. This article is about removing the clicks.

---

Key takeaways

• Level 1 - one-click import: the built-in Notion integration turns "copy-paste and rebuild" into "pick a page, generate." Enough for most people.
• Level 2 - trigger from an automation tool: Zapier, Make, or n8n watch Notion for a change and call 2Slides to generate the deck. No code, semi-hands-off.
• Level 3 - full API pipeline: a new Notion database entry fires a webhook that hits the 2Slides V1 API, which returns a rendered deck. Fully hands-off, built once.
• Pick the highest level you actually need - most teams are well served by Level 1 or 2; Level 3 pays off at volume.

---

Level 1: One-click import (no automation tools needed)

The fastest automation is the one you don't have to build. 2Slides connects to Notion with an official read-only OAuth integration, so the loop is:

1. Connect Notion once (private pages stay private).
2. In the 2Slides Workspace, search and pick the page.
3. Generate - the page's structure becomes a designed deck, optionally with narration and MP4 export in 21 languages.

For a "once a week I turn this page into a deck" cadence, this is already 90% of the value with none of the setup. When the trigger itself needs to be automatic, go to Level 2.

Level 2: Trigger generation from Zapier, Make, or n8n

Here the automation tool watches Notion and kicks off the deck. The shape is the same across platforms:

• Trigger: New database item or Updated page in Notion (native Notion connector in Zapier/Make/n8n).
• Action: an HTTP/Webhook step that calls the 2Slides API with the page's content.
• Optional: post the resulting deck link back to Slack, email, or a Notion property.

Example - a Make/n8n HTTP node calling 2Slides:

curl -X POST https://2slides.com/api/v1/slides/generate \
  -H "Authorization: Bearer $TWOSLIDES_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "userInput": "{{ notion.page.content }}",
    "responseLanguage": "Auto",
    "aspectRatio": "16:9",
    "mode": "async"
  }'

You get back a

; poll until it's done, then read the . No code beyond wiring the nodes.

Level 3: A fully hands-off API pipeline

At volume - a deck per new client, per release, per research entry - build it once with the API and let it run. The pattern:

1. Source of truth: a Notion database (one row = one deck to make).
2. Trigger: Notion's API/webhook (or a scheduled poll) detects a new row.
3. Fetch: your backend reads the row/page content via the Notion API.
4. Generate: call the 2Slides API. Use
   POST /api/v1/slides/generate
   for prompt/outline content, or
   POST /api/v1/slides/create-pdf-slides
   if you're feeding a longer document body.
5. Deliver: poll
   GET /api/v1/jobs/{id}
   , grab the
   downloadUrl
   , and write it back to the Notion row (or push to Drive/Slack).

Relevant 2Slides V1 endpoints for a pipeline:

Because the jobs are async, the whole thing slots cleanly into webhook-driven backends. For a full code walkthrough, see the AI Presentation API comparison with code examples, and for agent-driven variants, the MCP server ecosystem.

Which level is right for you?

Don't over-build. Most teams never need past Level 2. Level 3 earns its keep when the deck count is high enough that even a two-click flow adds up.

---

Frequently Asked Questions

Can I automatically generate a presentation when I add a Notion database entry?

Yes - at Level 3. Use Notion's API/webhook to detect the new entry, then call the 2Slides API (

or ) to render the deck and write the download link back to the row. Zapier, Make, or n8n can do the same with no code (Level 2).

Do I need to write code to automate Notion to slides?

No. The built-in Notion integration (Level 1) needs none, and Zapier/Make/n8n (Level 2) wire Notion to the 2Slides API visually. Code is only needed for a fully custom Level 3 pipeline.

What's the difference between the one-click integration and the API?

The integration is for a person generating a deck in the Workspace. The API is for programs - triggered by a Notion change or your backend - to generate decks without anyone clicking. Same generation engine, different entry point.

Can the automated deck include narration or video?

Yes. After generating, call

for Workspace jobs to add per-page voiceover, then export MP4. Narration applies to file/create-like-this jobs, not the template-driven Fast PPT path.

Is the Notion connection safe to leave running?

Yes - the integration is read-only and scoped to the pages you authorize. For API pipelines, your Notion API token controls what the backend can read; scope it to the specific database.

---

The bottom line

Automating Notion-to-slides isn't one thing - it's a ladder. Start at one-click import, add a Zapier/Make/n8n trigger when the timing should be automatic, and graduate to a full API pipeline only when volume demands it. The generation engine is the same at every level; you're just choosing how many clicks to remove.

Start simple: connect Notion. Build the pipeline: AI Presentation API with code examples · PowerPoint MCP server ecosystem · How to generate presentations from Notion

Last reviewed: 2026-07-08 by the 2Slides team.