🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Google Docs to Google Slides, decks built from transcripts

Google Docs to Google Slides, decks built from transcripts - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Google Docs to Google Slides, decks built from transcripts - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You finish a great call, you have a transcript, and then the real time-waster starts. Copying “the good parts” into slides, rewriting for clarity, hunting for the right layout, fixing spacing, re-fixing spacing. It is slow, and it is weirdly exhausting.

This Docs to Slides automation hits sales teams hard, but consultants building proposals and agency leads turning discovery calls into client decks feel it too. The outcome is simple: a client-ready Google Slides deck built from a Google Docs transcript using your own template, with text and images already in place.

Below you’ll see exactly what this n8n workflow system does, what you need to run it, and what to watch out for when you customize it.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Docs to Google Slides, decks built from transcripts

The Problem: Transcripts Don’t Turn Into Decks by Themselves

A transcript is a messy asset. It has repetition, tangents, half-sentences, and a lot of “context” that makes sense on a call but falls flat in a slide. So someone has to translate it into a storyline, shape it into a deck, then make it look like your brand. That “someone” is often you, late afternoon, trying to ship a follow-up before the prospect cools off. If you do this a few times a week, it becomes a quiet tax on your best work: selling, advising, or leading delivery.

It’s not one big task. It’s dozens of tiny ones, and they stack up fast.

  • You end up rewriting the same types of slides over and over (problem, impact, recommendation, next steps).
  • Deck formatting drifts, especially when multiple people touch the file across versions.
  • Important details get missed because you are scanning long transcripts under time pressure.
  • Even when you “template it,” you still spend about an hour per deck on assembly work.

The Solution: Build Slides From a Transcript Using Your Template

This automation is a connected 5-workflow system in n8n that turns a Google Docs meeting transcript into a polished Google Slides presentation. It starts with a simple intake (client name, transcript URL, submission time), clones your existing Slides template, and creates a tracking record in Google Sheets so every deck has a home. Then AI reads the transcript, pulls out pain points and goals, and writes a structured presentation plan you can quickly review in Google Docs. Once the plan looks right, the workflow generates custom illustrations (via an image model), stores them in Google Drive, and finally fills your Slides template with personalized text and the right images in the right places.

The flow begins with your form submission and a transcript link in Google Docs. From there, planning and content generation happen automatically, then the system updates Google Slides using Object IDs (unique identifiers inside your template) so it edits the correct text boxes and image placeholders. The result is a client-ready deck you can tweak and send without starting from a blank file.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you create 5 client follow-up decks a week. Manually, it’s usually about 2 hours each: 30 minutes pulling highlights from the transcript, about an hour building and formatting slides, then another 30 minutes finding or making visuals. That’s roughly 10 hours weekly. With this workflow, intake is about 5 minutes, AI planning and generation runs in the background, and you usually spend 20–30 minutes reviewing the plan and deck. You get most of that day back.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Google Workspace for Docs, Drive, Slides access.
  • Google Sheets to track decks and assets.
  • OpenAI API key (get it from the OpenAI API dashboard).
  • OpenRouter API key (get it from your OpenRouter account) for Flux image generation.
  • ImgBB API key (get it from ImgBB API settings) for reliable image URLs.

Skill level: Intermediate. You’ll connect accounts, copy a template, and paste a few IDs/keys, but you don’t need to write code unless you want deeper customization.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Intake triggers the process. A form submission captures the client name, the Google Docs transcript URL, and a timestamp. n8n uses that to kick off the system and keep everything tied to one “job.”

Your template becomes a new deck. The workflow clones a Google Slides presentation you already designed, then writes the new presentation ID into a Google Sheets database so you can track status and assets over time.

AI turns raw transcript into a plan. An AI agent reads the transcript and produces a structured presentation outline (pain points, goals, recommendations, proof, next steps). The plan is saved to Google Docs so it’s easy to review, comment on, and audit later.

Text and visuals get inserted automatically. Another AI agent generates slide-ready copy, while the image workflow generates illustrations and stores them in Drive. Because Google Drive image links can be finicky in API calls, the workflow uploads images to ImgBB so Slides can pull them reliably. Then n8n updates specific text boxes and image placeholders using Object IDs from your template.

You can easily modify the template structure to match your deck style based on your needs. See the full implementation guide below for customization options.

Common Gotchas

  • Google Workspace credentials can expire or need specific permissions. If things break, check the n8n credentials screen and your Google Cloud OAuth consent settings first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • ImgBB links are the difference between “works once” and “works every time.” If images are missing, verify the ImgBB API key and confirm the workflow is saving the returned hosted URL, not the original Google Drive link.

Related Workflows

If your team also needs a clean transcript and shareable notes before you build slides, Fathom to Google Docs, meeting notes you can share is a solid companion workflow for tightening up call outputs.

When your meetings live inside a recording tool and you want “follow-up deck ready fast” without extra handling, Claap to Google Slides, follow up decks ready fast fits neatly alongside transcript-to-deck automation.

For teams doing proposals and presentations together, Google Slides + Airtable, proposals ready to send helps you track opportunities and generate proposal decks from structured data, not just transcripts.

Need the transcript for more than a deck? Fathom to Google Docs, repurpose transcripts fast is useful when you want the same conversation turned into multiple assets (recaps, snippets, internal docs) after the slides are done.

Finally, if you want to squeeze more value out of the same meetings for personal branding, Google Calendar + Google Docs, LinkedIn drafts ready can turn scheduled calls into a steady stream of draft content.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Docs to Slides automation?

Plan on about 60–90 minutes the first time, mostly to prep your template and credentials.

Do I need coding skills to automate Docs to Slides?

No. You will connect tools and paste a few API keys. If you want to change the JSON parsing or add special logic, a little JavaScript helps, but it’s optional.

Is n8n free to use for this Docs to Slides workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI and OpenRouter usage (for many teams, it’s a few dollars per deck depending on length and images).

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Docs to Slides workflow for a different deck template?

Yes, but the template needs consistent Object IDs. Most teams duplicate their best deck, label text and image placeholders, then update the “clone template” step to point at the new Slides file. Common customizations include changing the slide order, swapping the AI model (OpenAI vs. Gemini), and adjusting the company profile so recommendations match your offer.

Why is my Google Workspace connection failing in this workflow?

Usually it’s expired OAuth access or missing scopes for Drive/Docs/Slides. Reconnect Google in n8n, confirm the Google Cloud project has the right APIs enabled, and double-check that the account you authorized actually has access to the transcript Doc and the Slides template. If it fails only on some clients, it’s often a permissions issue on the transcript file (shared to the wrong email). Rate limits can also show up when you generate a lot of decks back-to-back.

How many presentations can this Docs to Slides automation handle?

A lot.

Is this Docs to Slides automation better than using Zapier or Make?

Often, yes, if you care about control. This workflow has multiple stages, branching logic, and heavy API work (Slides object IDs, file handling, image hosting). n8n handles that kind of “real workflow” better, and self-hosting avoids per-task pricing that gets pricey once you generate decks every day. Zapier or Make can be fine for simple routing, but you’ll likely hit limits once you start updating Slides programmatically. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation.

Once this is running, decks stop being a “rebuild from scratch” chore and become a review step. Honestly, that’s the whole win.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.