🔓 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

Gmail + Google Drive: approve, then publish everywhere

Gmail + Google Drive: approve, then publish everywhere - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Gmail + Google Drive: approve, then publish everywhere - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Creating “one post” somehow turns into six different drafts, three image sizes, and a bunch of tab-hopping. Then you still have to chase approvals, find the latest version, and manually publish everywhere.

Social media managers feel this weekly. A marketing lead trying to keep brand voice consistent feels it too. So does the business owner who just wants Gmail Drive publishing automation that doesn’t become another project.

This workflow turns one topic into platform-ready posts, sends them to Gmail for approval, archives everything to Google Drive, then publishes to the channels you choose. You’ll see what it automates, what results to expect, and where teams usually get tripped up.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Gmail + Google Drive: approve, then publish everywhere

The Problem: Approvals and multi-platform posting are a time sink

You start with a solid idea. Then reality hits. X needs one format, LinkedIn needs another, Instagram needs media handling, and Facebook wants its own version too. Even if you’re “reusing” the message, you still rewrite, resize, paste, fix line breaks, and second-guess the tone for each channel. Add an approval loop on top and it gets messy fast: people approve old drafts, images get lost in DMs, and the final post you publish isn’t the one anyone reviewed. Honestly, it’s exhausting.

The friction compounds. Here’s where it breaks down most often.

  • One topic becomes four to six mini copywriting tasks, and that can quietly eat about 2 hours per campaign.
  • Approvals happen in the wrong place (chat threads, comments, “final_v7” docs), so the version history turns into a guessing game.
  • Publishing is repetitive and error-prone, especially when you’re switching between platform tabs and scheduling windows.
  • When you can’t find past creatives and captions quickly, you end up recreating assets you already paid for.

The Solution: One idea in, approved posts out, published everywhere

This n8n workflow acts like a “content publishing factory” that starts with a single topic and ends with approved, platform-specific posts ready to publish across your channels. You submit the idea through a chat trigger (a simple message), and the workflow uses AI to generate tailored copy for each platform using your saved brand prompts and formatting rules. It also generates an image through an image API, stores the creative safely, and packages the whole thing into a clean approval email in Gmail. Once approved, the workflow pulls the final content from Google Drive (so it’s always the right version) and publishes to the platforms you’ve enabled, including LinkedIn, X, Instagram, and Facebook. At the end, you get a summary email and a success message in Telegram so you’re not left wondering what happened.

The workflow starts with an incoming chat message, then builds a “prompt package” from your Google Docs system prompt and schema. After content and image generation, it archives the final assets to Google Drive, requests approval via Gmail, and only then routes publishing actions to each platform.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you publish the same announcement to four channels: X, LinkedIn, Instagram, and Facebook. Manually, you might spend about 15 minutes rewriting and formatting per platform, plus another 20 minutes dealing with the image and uploads, which lands around 1.5 to 2 hours total. With this workflow, you drop the topic into chat in about 5 minutes, wait for AI + image generation (roughly 10–20 minutes), approve via Gmail, and it publishes. You’re mostly out of the loop, and you still get an archived “source of truth” in Google Drive.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Gmail for approvals and summary emails.
  • Google Drive to archive posts and images.
  • Google Docs to store your prompts and schemas.
  • Telegram for quick success/error notifications.
  • OpenAI API key (create it in your OpenAI dashboard).
  • Pollinations.ai (or another image API) for AI image generation.
  • LinkedIn + X + Meta credentials to publish to your social accounts.

Skill level: Intermediate. You’ll connect accounts, paste API keys, and edit a couple of prompt documents to match your brand voice.

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

How It Works

A chat message kicks it off. You submit a topic through the workflow’s chat trigger, and the workflow immediately decides which platform outputs to prepare using a router agent.

Your “rules of the road” get pulled in. The workflow loads your system prompt and social schema from Google Docs, parses them, then assembles a structured prompt package so the AI outputs stay consistent (and predictable).

Content and images are generated, then archived. The AI generates platform-specific post JSON, an image is generated via an HTTP API, and everything is saved into Google Drive with useful metadata. This is what makes approvals clean later.

Gmail handles approvals, then publishing routes automatically. A Gmail approval email is sent, an If check confirms approval, then the workflow downloads the approved post from Drive, merges it with the image, and routes publishing to LinkedIn, X, Instagram, and Facebook (with placeholders for Threads and YouTube Shorts).

You can easily modify the approval logic to include more reviewers based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Chat Trigger

This workflow starts from a chat message and routes the request into the platform selection agent.

  1. Add and open Incoming Chat Trigger.
  2. Keep the default options or configure chat settings as needed for your channel.
  3. Confirm Incoming Chat Trigger is connected to 🤖 Platform Router Agent.

Step 2: Connect Google Docs for Prompt and Schema Inputs

The prompt system and content schema are loaded from Google Docs and parsed for downstream use.

  1. Open Social Schema Doc and set Document URL to =[YOUR_ID].
  2. Credential Required: Connect your googleDocsOAuth2Api credentials.
  3. Open System Prompt Doc and set Document URL to =[YOUR_ID].
  4. Credential Required: Connect your googleDocsOAuth2Api credentials.
  5. Confirm Subworkflow Input Trigger outputs to System Prompt Doc, Social Schema Doc, and Combine Prompt Inputs in parallel.
⚠️ Common Pitfall: Replace all [YOUR_ID] placeholders with real Google Doc IDs, or parsing will fail in Assign Schema Data and Assign System Prompt.

Step 3: Set Up the AI Router and Tools

The router agent decides which platform tool to use based on the chat input and calls the correct subworkflow.

  1. Open 🤖 Platform Router Agent and keep the Text prompt as =You are a helpful assistant that uses the provided tools. Respond with a valid JSON object. with the user prompt expression.
  2. Confirm GPT Omni Router is connected as the language model for 🤖 Platform Router Agent.
  3. Credential Required: Connect your openAiApi credentials to GPT Omni Router.
  4. Ensure the tool nodes X Post Tool, Instagram Post Tool, Facebook Post Tool, LinkedIn Post Tool, Threads Post Tool, and YouTube Short Tool remain connected as tools to 🤖 Platform Router Agent.
  5. Keep each tool’s route field as configured (for example, =xtwitter, =instagram, =facebook, =linkedin, =threads, =youtube_short).
AI tools are sub-nodes of 🤖 Platform Router Agent. If you later add credentials to any tool workflow, do it through the parent agent configuration.

Step 4: Set Up Prompt Parsing and Content Generation

Schema and system prompt XML are parsed, assembled, and sent to the content generator agent.

  1. In Assign Schema Data, verify schema is set to {{$json.content}} and platform to {{$('Subworkflow Input Trigger').item.json.route}}.
  2. In Assign System Prompt, ensure system_prompt is set to {{$json.content}}.
  3. Leave Extract Schema XML and Parse Prompt XML code as provided to parse XML into JSON objects.
  4. In Assemble Prompt Package, confirm all fields reference the combined prompt data (for example, {{$json.system_config.system}} and {{$json.common_schema}}).
  5. Open Social Content Generator and confirm the Text prompt uses Social Media Platform: {{ $json.route }} and User Prompt: {{ $json.user_prompt }}.
  6. Ensure GPT Mini JSON is connected as the language model for Social Content Generator.
  7. Credential Required: Connect your openAiApi credentials to GPT Mini JSON.
  8. Confirm Serp Search Tool is connected as a tool to Social Content Generator.
  9. Credential Required: Connect your serpApi credentials (add them through the Social Content Generator tool configuration).

Step 5: Configure Image Generation and Storage

Generated content is turned into an image, uploaded to external storage, and archived in Google Drive.

  1. In Image Generator API, set URL to =https://image.pollinations.ai/prompt/{{ $json.output.common_schema.image_suggestion.replaceAll(' ','-').replaceAll(',','').replaceAll('.','').slice(0,100) }}.
  2. In Upload Image to ImgBB, keep URL as https://api.imgbb.com/1/upload and Content Type as multipart-form-data.
  3. Set the ImgBB query parameter key to {{$env.IMGBB_API_KEY}} in Upload Image to ImgBB.
  4. Open Archive Image to Drive and set Name to {{$json.output.root_schema.name.replaceAll(' ','-').replaceAll(',','').replaceAll('.','')}}.
  5. Credential Required: Connect your googleDriveOAuth2Api credentials to Archive Image to Drive.
  6. Confirm Image Generator API outputs to Telegram Success Notice, Upload Image to ImgBB, Archive Image to Drive, and Combine Image Data in parallel.
  7. Confirm Combine Image Data outputs to both Compose Summary Email and Drive Image Metadata in parallel.
⚠️ Common Pitfall: If $env.IMGBB_API_KEY is missing, Upload Image to ImgBB will fail and break Combine Image Data.

Step 6: Configure Approval and Routing Logic

Content is stored, archived, then sent for approval before publishing routes are activated.

  1. In Build Post JSON, keep the JSON assembly expression as configured to combine route, social_image, social_content, and google_drive_image.
  2. Open Archive Post to Drive and set Name to {{$json.response.google_drive_image.id}} and Content to {{$json.response.toJsonString()}}.
  3. Credential Required: Connect your googleDriveOAuth2Api credentials to Archive Post to Drive.
  4. Ensure Approval Email Request is configured with Operation set to sendAndWait and the Subject expression =🔥FOR APPROVAL🔥 {{$('Extract JSON Content').item.json.data.social_content.root_schema.name }}.
  5. Credential Required: Connect your gmailOAuth2 credentials to Approval Email Request.
  6. Confirm Extract JSON Content outputs to both Join Image and Post and Compose Approval Email in parallel.
  7. In Approval Check, keep the condition {{$json.data.approved}} set to true to allow publishing.
The Threads Placeholder and YouTube Shorts Placeholder nodes are noOp nodes and act as stubs for future publishing expansion.

Step 7: Configure Social Publishing Outputs

The approved content is routed to the correct social platform and published.

  1. In Route Social Publisher, keep each switch rule using {{$json.data.route}} with output keys for xtwitter, instagram, facebook, linkedin, threads, and youtube_short.
  2. Open Publish X Status and set Text to {{$json.data.social_content.schema.post}}.
  3. Credential Required: Connect your twitterOAuth2Api credentials to Publish X Status.
  4. Open Create Instagram Media and keep URL as https://graph.facebook.com/v20.0/[YOUR_ID]/media with query parameters image_url and caption.
  5. Credential Required: Connect your facebookGraphApi credentials to Create Instagram Media and Publish Instagram Media.
  6. Open Publish Facebook Photo and keep Edge as photos with Binary Property Name set to data.
  7. Credential Required: Connect your facebookGraphApi credentials to Publish Facebook Photo.
  8. Open Publish LinkedIn Update and keep Text as {{$json.data.social_content.schema.post}} {{$json.data.social_content.schema.call_to_action}} {{$json.data.social_content.common_schema.hashtags}}.
  9. Credential Required: Connect your linkedInOAuth2Api credentials to Publish LinkedIn Update.
⚠️ Common Pitfall: Replace all [YOUR_ID] placeholders in Facebook and Instagram nodes with the correct page or account IDs.

Step 8: Configure Email and Notification Outputs

Emails and Telegram notices provide status updates and summaries.

  1. Open Compose Summary Email and keep the HTML template prompt as configured.
  2. Confirm Compact GPT Model is connected as the language model for Compose Summary Email.
  3. Credential Required: Connect your openAiApi credentials to Compact GPT Model.
  4. Open Send Gmail Summary and set Send To to {{$env.TELEGRAM_CHAT_ID}}, Message to {{$json.output}}, and Subject to =Social Media Content - {{ $('Store Social Output').item.json.output.title }}.
  5. Credential Required: Connect your gmailOAuth2 credentials to Send Gmail Summary.
  6. Open Telegram Success Notice and Telegram Error Notice, and keep Chat ID set to {{$env.TELEGRAM_CHAT_ID}}.
  7. Credential Required: Connect your telegramApi credentials to both Telegram Success Notice and Telegram Error Notice.
Compact GPT Model 2 is connected as the language model for Compose Approval Email. Ensure openAiApi credentials are set on Compact GPT Model 2.

Step 9: Test and Activate Your Workflow

Run an end-to-end test to confirm content creation, approval, and publishing steps work as expected.

  1. Click Execute Workflow and send a sample message to Incoming Chat Trigger.
  2. Verify that 🤖 Platform Router Agent routes to the correct tool and that Social Content Generator outputs JSON in Store Social Output.
  3. Confirm the parallel branches run: Image Generator API should trigger Telegram Success Notice, Upload Image to ImgBB, Archive Image to Drive, and Combine Image Data.
  4. Approve the email from Approval Email Request and confirm Route Social Publisher triggers the correct publisher node.
  5. Once validated, toggle the workflow to Active to enable production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • Gmail credentials can expire or need specific permissions. If things break, check your n8n Credentials page and the connected Google account security 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.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Related Workflows

If your team also drafts content in Docs first, Google Docs to LinkedIn, approved posts ready to publish is a simpler companion workflow for polished LinkedIn-only publishing.

For teams doing planning and approvals in spreadsheets, Google Sheets + LinkedIn: approved posts, published fits nicely alongside this factory-style setup.

When you want a different AI model in the mix for drafting, Google Gemini + Google Sheets, posts ready to publish is useful for comparing output quality and tone.

Need the approval loop without the full multi-platform publishing layer? Telegram to Gmail, approvals and posts stay consistent keeps approvals tight and fast with fewer moving parts.

Finally, if you want to generate multiple variations for testing hooks, OpenAI + Google Sheets: 5 social posts from one idea pairs well with this workflow’s publishing backbone.


Quick reference:

Frequently Asked Questions

How long does it take to set up this Gmail Drive publishing automation?

About 45 minutes if your accounts and API keys are ready.

Do I need coding skills to automate Gmail Drive publishing?

No. You’ll mostly connect accounts and paste a few API keys. The only “technical” part is editing the Google Docs prompts in plain English so the outputs match your brand.

Is n8n free to use for this Gmail Drive publishing automation 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 API costs (often a few dollars a month at small volumes) and any image API costs if your provider charges.

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 Gmail Drive publishing automation workflow for multiple approvers?

Yes, but plan it before you go live. You can adjust the Gmail approval email step and the Approval Check logic so it waits for the right reply, or requires approval from more than one address. Common customizations include adding a second stakeholder, changing the approval keywords (like “APPROVE/REJECT”), and routing different brands to different Google Drive folders. You can also swap the image generator HTTP request to your preferred provider without changing the publishing side.

Why is my Gmail connection failing in this workflow?

Usually it’s an expired OAuth session or a Google account security change. Reconnect Gmail in n8n Credentials, then confirm the Gmail account still allows the scopes n8n requested. If the approval email sends but the workflow can’t read the reply, check that the workflow is looking at the correct mailbox and thread.

How many posts can this Gmail Drive publishing automation handle?

On n8n Cloud Starter you can run a healthy volume each month, and self-hosting removes execution limits (your server becomes the limiter). In practice, this workflow is usually gated by approvals and platform APIs, so most teams scale by batching topics and approving in chunks.

Is this Gmail Drive publishing automation better than using Zapier or Make?

For this use case, n8n is often the better fit because you can do more complex routing (multi-platform publishing plus approval logic) without paying extra for every branch. Self-hosting is a big deal if you publish frequently, and it’s easier to keep a clean “Drive as the source of truth” pattern. Zapier or Make can still work if you only want a simple “generate text, send email” flow. The moment you add AI outputs, archiving, approvals, and multi-channel publishing, costs and complexity pile up. If you want a second opinion, Talk to an automation expert and map it to your volume.

Once this is running, approvals stop being a bottleneck and publishing stops being a chore. Set it up, tune the prompts, and let Google Drive hold the “final” version every time.

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.