Generate & distribute market reports with Google Docs, Sheets, and Gmail
How It Works βοΈ
This workflow is a powerful automation engine for your marketing efforts. On a set schedule, it automatically generates a professional market report and distributes it to your client list, positioning you as a market expert with zero manual effort.
- 0. Cron (Monthly Schedule): β° The workflow is triggered automatically on the first day of every month at a specified time (e.g., 8:00 AM).
- 1. HTTP Request (Get Market Data): π It connects to an external market data API to fetch the latest raw statistics and trends for your region.
- 2. Function (Process Data): π This node processes the raw API data, formats it, and calculates key metrics (e.g., total sales, average price) to be used in the final report.
- 3. Google Docs (Create Report): π Using a pre-designed Google Docs template, the workflow dynamically creates a new report document, filling in the placeholders with the data processed in the previous step.
- 4. Google Sheets (Get Client List): π It fetches your client mailing list from a Google Sheet, which acts as your central database for client contacts.
- 5. Split In Batches: π This node ensures that each client from the mailing list is processed individually, preventing any issues with bulk emailing.
- 6. Gmail (Send Report): π§ For each client, a personalized email is sent with the newly generated market report attached as a PDF, completing the distribution process.
How to Set Up π οΈ
Setting up this complex workflow requires careful configuration of each node and external services.
-
Import Workflow JSON:
- Open your n8n instance.
- Click on 'Workflows' in the left sidebar.
- Click the '+' button or 'New' to create a new workflow.
- Click the '...' (More Options) icon in the top right.
- Select 'Import from JSON' and paste the entire JSON code for this workflow.
-
Prepare Your Data & Tools:
- Market Data API: Obtain an API key or access for a market data service that provides the data you need. This could be a public service or an internal one.
- Google Docs Template: Create a Google Docs template for your market report. Use placeholders like
{{ averagePrice }},{{ totalSales }}, and{{ reportMonth }}for the data you want to insert. - Client Mailing List: Create a Google Sheet with a list of your clients. It must have columns like
Client NameandClient Email. - n8n Credentials: Ensure you have configured OAuth2 credentials for both Google Sheets and Google Docs.
-
Configure 0. Cron (Monthly Schedule):
- The node is pre-configured to run on the 1st of every month at 8 AM. You can adjust the
hourordayOfMonthif needed.
- The node is pre-configured to run on the 1st of every month at 8 AM. You can adjust the
-
Configure 1. HTTP Request (Get Market Data):
- Locate the '1. HTTP Request (Get Market Data)' node.
- URL: Replace
https://api.your-market-data-service.com/data/monthly?region=Jakartawith the actual URL of your market data API endpoint. - Authentication: Configure the authentication (e.g.,
Header Authfor an API key) according to your API provider's documentation.
-
Configure 2. Function (Process Data):
- Locate the '2. Function (Process Data)' node.
- Data Mapping: The code is an example. You MUST update the code inside this node to correctly parse the JSON data coming from your specific API call and extract the metrics you need.
- Expressions: Ensure the variable names (
totalSales,averagePrice, etc.) match the placeholders in your Google Docs template.
-
Configure 3. Google Docs (Create Report):
- Locate the '3. Google Docs (Create Report)' node.
- Credentials: Select your Google Docs OAuth2 credential.
- Document ID: Replace
YOUR_GOOGLE_DOCS_TEMPLATE_IDwith the ID of the template you created. - Template Variables: Ensure the
variablenames (averagePrice,totalSales, etc.) perfectly match the placeholders in your Google Docs template.
-
Configure 4. Google Sheets (Get Client List):
- Locate the '4. Google Sheets (Get Client List)' node.
- Credentials: Select your Google Sheets OAuth2 credential.
- Spreadsheet ID: Replace
YOUR_CLIENT_MAILING_LIST_SPREADSHEET_IDwith the ID of your client list sheet. - Sheet Name: Enter the exact name of the sheet (tab) containing your client data.
-
Configure 5. Split In Batches:
- This node requires no configuration. It will automatically process each client from the Google Sheets list one by one.
-
Configure 6. Gmail (Send Report):
- Locate the '6. Gmail (Send Report)' node.
- Credentials: Select your Gmail OAuth2 credential.
- From Email: Replace
your-agency-email@example.comwith the email address you want to send from. - To Email:
={{ $json['Client Email'] }}(This pulls the email from the current batch item). - Attachments: The node is set up to attach the file created by the Google Docs node. No changes are needed here unless you want to customize the file name.
-
Review and Activate:
- Thoroughly review all node configurations. This is a complex workflow, so be meticulous.
- Click 'Save' and then toggle the 'Inactive' switch to 'Active' to enable your workflow. π’ Your automated marketing engine is now live!
Automate Market Report Generation and Distribution with Google Docs, Sheets, and Gmail
This n8n workflow automates the process of generating market reports from a Google Sheet, creating them as Google Docs, and then distributing them via Gmail. It's designed for periodic execution, ensuring your stakeholders receive up-to-date reports without manual intervention.
What it does
This workflow streamlines your market report process through the following steps:
- Schedules Execution: The workflow is triggered on a predefined schedule (e.g., daily, weekly, monthly) using the Cron node.
- Prepares Data: A Function node is used to prepare and transform data, likely setting up parameters or processing initial inputs for subsequent operations.
- Fetches Report Data: It retrieves market report data from a specified Google Sheet. This data will be used to populate the report documents.
- Generates Google Docs: For each report entry fetched from Google Sheets, it likely generates a new Google Doc, populating it with the relevant data.
- Distributes Reports via Email: Finally, the workflow sends out the newly generated Google Docs as attachments or links via Gmail to a list of recipients.
- Iterates for Multiple Reports: The "Loop Over Items" (Split in Batches) node suggests that the workflow can process multiple market reports in a single run, handling each report individually after fetching the initial data.
- Provides Documentation: A Sticky Note node is included, likely containing important notes or instructions for the workflow's usage or configuration.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Account: A Google account with access to:
- Google Sheets: To store the raw market report data.
- Google Docs: To create and manage the generated reports.
- Gmail: To send out the reports.
- Google Credentials: Configured Google OAuth2 credentials within n8n for Google Sheets, Google Docs, and Gmail.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Set up your Google OAuth2 credentials in n8n for Google Sheets, Google Docs, and Gmail.
- Connect these credentials to the respective Google Sheets, Google Docs, and Gmail nodes in the workflow.
- Update Google Sheets Node:
- Specify the Spreadsheet ID and Sheet Name where your market report data is stored.
- Update Google Docs Node:
- Configure the Google Docs node to create new documents based on your report data. You might need to specify a template document or define how the data should be inserted.
- Update Gmail Node:
- Configure the Gmail node with the recipient email addresses, subject line, and email body. Ensure it's set to attach or link the generated Google Docs.
- Configure Cron Schedule: Adjust the "Cron" node to your desired reporting frequency (e.g., once a day, once a week).
- Review Function Node: Examine the "Function" node to understand any data transformations or custom logic applied. Adjust if necessary for your specific data format.
- Activate the Workflow: Once all configurations are complete, activate the workflow. It will now run automatically based on your defined schedule.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitorβs webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger β Manually start the workflow or schedule it to run periodically. Input Setup β Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) β Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring β Clean and convert GPT output into JSON format. Data Storage (Google Sheets) β Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the βSet Input Fieldsβ node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors β Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection β Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report β Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization β Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs β Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting Itβs a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive β Download PDF β OCR text β AI normalize to JSON β Upsert Buyer (Account) β Create Opportunity β Map Products β Create OLI via Composite API β Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content β the parsed JSON (ensure itβs an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id β build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total β per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger β Download File From Google Download File From Google β Extract from File β Update File to One Drive Extract from File β Message a model Message a model β Create or update an account Create or update an account β Create an opportunity Create an opportunity β Build SOQL Build SOQL β Query PricebookEntries Query PricebookEntries β Code in JavaScript Code in JavaScript β Create Opportunity Line Items --- Quick setup checklist π Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. π IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) π§ AI Prompt: Use the strict system prompt; jsonOutput = true. π§Ύ Field mappings: Buyer tax id/name β Account upsert fields Invoice code/date/amount β Opportunity fields Product name must equal your Product2.ProductCode in SF. β Test: Drop a sample PDF β verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep βReturn only a JSON arrayβ as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields donβt support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your orgβs domain or use the Salesforce nodeβs Bulk Upsert for simplicity.