Validate Google Drive Scheduled Post Queue in n8n
Validate Google Drive Scheduled Post Queue in n8n
Regular price
£57.99
Regular price
£57.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Validate Google Drive Scheduled Post Queue in n8n
Regular price
£57.99
Regular price
£57.99
Sale price
Unit price
/
per
Quickly audit your Google Drive “scheduled post” queue before publishing
This n8n manual workflow scans your Google Drive scheduled-post folders, validates their folder names, scheduled times, and required contents (like tweet.txt and images), then produces a clear human-readable report plus structured JSON results—so you catch errors early and avoid broken or duplicate scheduled posts.
What this workflow does
- Runs as a manual validation pass to check the queue on demand.
- Loads validation settings including image minimum/maximum counts and supported file extensions.
- Lists all scheduled-post folders under a selected Google Drive root folder.
-
Validates folder naming format in
yyyy-MM-dd_HHmm__label:- Confirms the date/time is real and convertible
- Converts to UTC using your
utcOffsetMinutes - Checks whether the scheduled time is in the future
- Flags duplicate scheduled times
-
Checks folder contents by listing files in each scheduled-post folder and enforcing:
- Exactly one
tweet.txt - Configured number of images and valid extensions
- Failure if the folder contains nested folders or “already processed” marker files
- Exactly one
- Outputs results: a summary, a readable text report, and a JSON results array marking folders as valid, warning, or invalid.
Use cases
- Before an automation publishes queued items, validate that every scheduled post folder is correctly named and complete.
- Detect timezone mistakes by adjusting
utcOffsetMinutesand confirming future scheduled times. - Spot configuration issues—wrong image counts, unsupported extensions, missing
tweet.txt, or accidental duplicates.
Technical details
- Trigger: Manual Trigger
- Integrations: Google Drive
- Workflow logic: set, code, sticky note, split in batches
-
Inputs: Google Drive root folder selection + validation limits (
utcOffsetMinutes,minImages,maxImages,supportedExtensions)
