Gmail and Google Cloud Storage integration

This n8n workflow automates the process of creating and sending high-quality newsletters with images generated by a GPT image generator. It is triggered on a schedule. What is included? 1 n8n workflow (json) 1 Setup tutorial doc 1 video guidance on how to connect n8n with all Google products 1 video guidance on how to connect n8n with Google Cloud Storage Who is this for? This template is ideal for: Content creators looking to automate their newsletter process. Marketers seeking to efficiently produce engaging newsletters with AI-generated content and imagery. Anyone wanting to create and send personalized newsletters on a schedule. What problem is this workflow solving? Manually creating and sending newsletters can be time-consuming, especially when including relevant and engaging content and imagery. This workflow automates the content generation (using AI and web search), image creation, and sending process, freeing up time and ensuring consistent communication with clients. What this workflow does: This workflow automates the following steps: Scheduled Trigger: The workflow is triggered automatically on a predefined schedule. Get Newsletter Topic: Retrieves the first unpublished newsletter topic from a Google Sheet titled "Newsletter Topics". It then updates the status of this topic and records the publication date to avoid duplication in future runs. AI Newsletter & Image Generator: This is the core content creation step. It uses an AI agent (configured with OpenAI and Perplexity APIs) to generate an engaging newsletter and a detailed, ultra-realistic image prompt based on the selected topic and real-time web research. GPT Image Generation: Uses the OpenAI API to generate an image based on the detailed image prompt created in the previous step. Get Client List: Retrieves client names and email addresses from a Google Sheet titled "Clients". Send Newsletter: Sends the personalized newsletter via Gmail to each client on the list, including the AI-generated title, content, and the uploaded image. The email body HTML is customizable. Setup: Configure the workflow's run frequency within the "Schedule Trigger" node. Create a Google Sheet named "Newsletter Topics" and "Clients" in your Google Drive. Enter your OpenAI and Perplexity API key in the 'Input' node. Connect your Gmail account to the "SendNewsletter" node. How to customize this workflow: Adjust the prompt for your newsletter style in the "AI Agent" node. Adjust the Email Body HTML for your newsletter style in the "SendNewsletter" node. Optionally, enable the "Tavily WebSearch" node and configure it if you prefer to use Tavily instead of Perplexity for web search. Category: Marketing, Content Creation, Automation

Reliable Backup & Sync Execution Validation (Log-Driven) This workflow monitors filesystem sync and backup jobs by validating their execution logs, not by running or inspecting the jobs themselves. After purchase, you will receive a complete package including: workflow.json** – ready to be imported into n8n Shell script templates (.sh)** – reference sync job templates designed to generate structured logs fully compatible with the workflow Complete setup documentation** – step-by-step guide covering configuration, deployment, and operational requirements How it works (high level) Sync jobs are executed externally using standardized shell templates: rsync_job-Template.sh rclone_job-Template.sh Each job produces one deterministic log file per run Logs are uploaded daily to Google Cloud Storage This workflow runs on a schedule and: Verifies that all expected logs exist for the day (UTC) Optionally inspects their contents Sends alerts if logs are missing or report failures Key design principles Log-driven monitoring** (evidence-based, not assumption-based) One job = one log = one source of truth** No SSH, no server access, no execution coupling** Safe to run in untrusted or restricted environments Logging contract (required) Each log file must contain the following lifecycle events, in order: event=START event=RSYNC_END or event=RCLONE_END event=SUMMARY event=END If the END event is missing, the job is considered failed or interrupted. Configuration Expected jobs and log filenames are defined in sync-jobs.json. This workflow only validates presence and state of logs — it never assumes job success.