n8n Scheduled Social Content Packages w/ Forms & Google Drive

Turn scheduled social ideas into a ready-to-publish Google Drive package—automatically

This n8n workflow takes details submitted through an n8n Form Trigger, validates the inputs, and then creates a Google Drive folder containing a tweet.txt plus 1–4 numbered image files for your scheduled social content.

What this workflow does

• Receives form submissions with a scheduled date/time, post text, an optional label, and uploaded PNG/JPG images (1–4 total).
• Validates inputs: checks date/time format, ensures the post text is not empty, verifies the image count, and confirms file types are supported.
• Generates a canonical package folder name based on the submission details.
• If the submission is invalid, returns a form completion message listing exactly what needs correction—no folder is created.
• Prevents duplicates by checking Google Drive in your configured parent folder to see if a folder with the same package name already exists; if it does, it returns a completion message and creates nothing.
• If valid and unique, creates a new Google Drive folder, writes the post content to tweet.txt, and renames images to 01–04 while preserving the original extensions.
• Handles failures safely: if any upload fails, it deletes the newly created folder and returns an error message; otherwise it confirms success.

Use cases

• SaaS teams routing scheduled tweet/campaign assets from a form into a standardized Google Drive deliverable.
• Automation engineers needing validation + deduplication logic before writing files to Google Drive.
• Ops workflows where incomplete or invalid submissions should never produce partial Drive uploads.

Technical details

• Integrations: n8n Form Trigger and Google Drive (OAuth credential required).
• Node/logic components: if, set, code, form, sticky note, and form trigger (for validation, messaging, and file handling).
• Google Drive destination: configure the destination parent folder by replacing PASTE_GOOGLE_DRIVE_PARENT_FOLDER_ID_HERE in the workflow.