Create daily multi-platform social posts with Gemini, NocoDB, Cloudinary and Telegram

Quick overview This workflow runs on a weekday evening schedule to generate tomorrow’s multi-platform social post using Google Gemini, stores the draft in NocoDB, generates a branded image, uploads it to Cloudinary, updates the NocoDB record with the image URL, and notifies a Telegram chat.

How it works Runs on a cron schedule (20:00 UTC, Sunday–Thursday) and checks NocoDB to skip generation if an Approved post is already scheduled for tomorrow. Fetches recent content entries and active content pillars from NocoDB, and also counts existing non-rejected posts to inform pillar selection. Optionally pulls the top Approved curated article from a NocoDB queue and assigns the next pillar based on target frequencies (substituting if curated content is unavailable). Builds a detailed prompt and calls Google Gemini to generate one post with platform-native variants (LinkedIn, X, Instagram, Facebook, Bluesky, Threads) in a strict JSON format. Parses the Gemini response, calculates tomorrow’s scheduled date/time slot based on day-of-week, and creates a new Approved row in the NocoDB content calendar. Builds a branded image prompt, generates an image with Google Gemini, uploads it to Cloudinary, and extracts the hosted image URL. Updates the NocoDB calendar entry with the generated media URL and sends a Telegram message summarizing the draft with an inline Reject button.

Setup Add NocoDB API token credentials and fill in your NocoDB base URL, workspace ID, project ID, and table IDs for the content calendar, pillars, and curated queue. Add a Google Gemini (PaLM) API credential for both text generation and image generation models. Add Cloudinary credentials and adjust the upload folder/tags if you want a different asset organization. Create a Telegram bot and chat, then set the bot token and target chat ID in the Telegram HTTP request node. Ensure your NocoDB content calendar table includes the fields the workflow writes/updates (for example Title, platform versions, Pillar, Status, Scheduled Datetime, Media Status, and Media URLs).

Requirements Requires n8n v1.30 or later.

Customization Third-party services (n8n, NocoDB, Google Gemini, Upload Post, Telegram) are subject to their own pricing and terms of service, which may change independently of this product.

Additional info Find out more about the full Zo.E Suite and the AI-driven, end-to-end content automation at https://www.nunlimited.com