Weekly MySQL Database Backup to Google Sheets
Overview
This workflow automatically exports data from a MySQL database table into a Google Sheet on a weekly schedule. It's perfect for creating regular backups of critical database tables, generating weekly reports for stakeholders, or maintaining an audit trail of database changes without manual intervention.
The workflow runs every week at 5:00 AM (server time), queries a MySQL database using a custom SQL statement, and appends the results to a specified Google Sheet. This eliminates the need for manual exports and ensures your data is consistently backed up in an accessible format.
Workflow Steps
-
Cron — Schedule Trigger (No auth)
- Runs the workflow every week at 5:00 AM (hour: 5, mode: everyWeek)
- No authentication required as it's a built-in trigger
-
MySQL - select — MySQL Database Node (Database credentials required)
- Executes the query:
SELECT * FROM books; - Operation: executeQuery — runs a raw SQL query against your MySQL database
- Requires MySQL connection credentials (host, port, database name, username, password)
- Executes the query:
-
Google Sheets - write — Google Sheets Node (OAuth2 authentication)
- Operation: append — adds new rows to the end of the specified sheet
- Sheet ID:
qwertz(you must replace this with your actual Google Sheet ID) - Uses OAuth2 authentication to connect to Google Sheets
- No additional options configured
Setup Instructions
Prerequisites
- MySQL Database — You need access to a MySQL database with the
bookstable (or modify the query for your table) - Google Account — A Google account with access to Google Sheets
- n8n Instance — Running n8n (self-hosted or cloud)
Configuration Steps
-
MySQL Credentials
- In n8n, create a new MySQL credential
- Enter your database host, port (default 3306), database name, username, and password
- Test the connection to ensure it works
-
Google Sheets Credentials
- Create a Google Sheets OAuth2 credential in n8n
- Follow the OAuth2 setup flow to authorize n8n to access your Google Sheets
- Ensure the credential has access to the sheet you want to use
-
Update Node Parameters
- Replace
qwertzin the Google Sheets node with your actual Sheet ID (found in the sheet URL:https://docs.google.com/spreadsheets/d/YOUR_SHEET_ID/edit) - Modify the SQL query in the MySQL node if you want to select different columns or tables
- Optionally, add a sheet name in the options if you want to write to a specific tab
- Replace
Use Cases & Variations
Common Use Cases
- Weekly sales reports — Export orders or transactions from MySQL to a shared Google Sheet
- Inventory backups — Regularly backup product inventory data
- User activity logs — Archive user actions or login records
- Financial audits — Maintain an append-only log of financial transactions
Possible Adaptations
- Change schedule — Modify the Cron node to run daily, monthly, or at a specific time
- Filter data — Update the SQL query to select only recent records (e.g.,
WHERE created_at > NOW() - INTERVAL 7 DAY) - Multiple tables — Add more MySQL nodes to export different tables in sequence
- Data transformation — Insert a Function or Set node between MySQL and Google Sheets to transform data before writing
- Error handling — Add an Error Trigger to send notifications if the workflow fails
- Notifications — Add a Slack or Email node to alert when the backup completes
Workflow JSON
{
"nodes": [
{
"name": "Cron",
"type": "n8n-nodes-base.cron",
"position": [
100,
420
],
"parameters": {
"triggerTimes": {
"item": [
{
"hour": 5,
"mode": "everyWeek"
}
]
}
},
"typeVersion": 1
},
{
"name": "MySQL - select",
"type": "n8n-nodes-base.mySql",
"position": [
300,
420
],
"parameters": {
"query": "SELECT * FROM books;",
"operation": "executeQuery"
},
"credentials": {
"mySql": {
"id": "82",
"name": "MySQL account"
}
},
"typeVersion": 1
},
{
"name": "Google Sheets - write",
"type": "n8n-nodes-base.googleSheets",
"position": [
500,
420
],
"parameters": {
"options": {},
"sheetId": "qwertz",
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
AI-Powered CV Scanner with Google Sheets & Gemini
Overview This workflow automates the initial screening of job applicants by combining a web form, AI-powered CV analysis, and Google Sheets. When a candidate submits their application (name, email, and CV PDF), the workflow instantly extracts the text from the PDF using Mistral OCR, then sends it to Google Gemini for evaluation against a predefined job description. The AI returns a qualification score (0.0 to 1.0) and a detailed explanation, which are then logged alongside the candidate's details in a Google Sheet. This eliminates manual CV review, speeds up your hiring pipeline, and ensures every applicant is evaluated consistently. Workflow Steps Application Form (Form Trigger) — No auth required. This node presents a custom-branded web form to collect the candidate's Full Name, Email, and CV (PDF upload). The form is styled with a dark, glassmorphism theme and includes animated backgrounds. Once submitted, the workflow triggers automatically. Log Candidate Submission (Google Sheets) — OAuth2. Immediately after form submission, this node appends the candidate's name and email to the 'CVs' Google Sheet. This ensures the application is recorded even if the subsequent analysis steps fail. Extract CV Text (Mistral AI) — API Key auth. This node takes the uploaded PDF file from the form and uses Mistral's OCR API to extract all text content from the CV. It dynamically selects the binary file uploaded in the previous step. AI Qualification (LLM Chain) — This is the core analysis node. It uses a detailed prompt that includes: - A system message defining the AI as a professional, objective hiring assistant. - The full job description for a "Senior Frontend Developer" with core requirements and preferred qualifications. - Clear evaluation logic: candidates missing core requirements cannot score above 0.6; meeting all core requirements yields at least 0.75; preferred qualifications add bonuses up to 1.0. - The extracted CV text as context. - An instruction to output raw JSON only. Gemini 2.5 Flash Lite (Language Model) — API Key auth (Google AI Studio). This node provides the actual AI model (Google Gemini 2.5 Flash Lite) with a temperature of 0.4 for balanced, deterministic outputs. It powers the LLM Chain above. JSON Output Parser (Output Parser) — This node ensures the AI's response is valid JSON with the exact schema: (number) and (string). It prevents malformed responses from breaking downstream nodes. Add CV Analysis (Google Sheets) — OAuth2. After analysis, this node updates the candidate's row in the 'CVs' sheet by matching on the Email column. It writes the and from the AI's output into the corresponding columns. Create 'CVs' Spreadsheet (Google Sheets) — OAuth2. This node runs once when the workflow is first triggered manually. It creates a new Google Sheet named 'CVs' with columns: FullName, Email, QualificationRate, QualificationDescription. Setup Instructions Prerequisites A Google account (for Google Sheets) A Mistral AI account (free tier available) — Get your API key here A Google AI Studio account — Create an API key here Step-by-Step Google Sheets Credentials: In the three Google Sheets nodes, create or select an OAuth2 credential for Google Sheets. Grant access to create and edit spreadsheets. Mistral AI Credential: In the "Extract CV Text" node, create a new credential and paste your Mistral API key. Gemini Credential: In the "Gemini 2.5 Flash Lite" node, create a new credential and paste your Google AI Studio API key. Customize Job Description: Open the "AI Qualification" node and edit the section in the prompt to match your actual job posting. Activate the Workflow: Toggle the workflow to "Active" status. The "Application Form" node will generate a public URL you can share with candidates. Test: Use the "Start Here" manual trigger to initialize the Google Sheet, then submit a test application via the form URL. Use Cases & Variations Custom Job Roles: Replace the Senior Frontend Developer description with any role (e.g., Marketing Manager, Data Scientist, Sales Rep) by editing the prompt in the AI Qualification node. Different Storage: Replace Google Sheets with Airtable, Notion, or a database like PostgreSQL for storing applications and results. Multi-Round Screening: Add a Slack or email notification node to alert the hiring team when a candidate scores above a certain threshold (e.g., >0.8). Interview Scheduling: Connect the output to a Calendly or Google Calendar node to automatically invite high-scoring candidates for an interview. Batch Processing: Modify the trigger to accept a CSV upload of multiple CVs for bulk analysis. Enhanced Analysis: Add more output fields like "years of experience", "top skills", or "red flags" by updating the JSON schema in the Output Parser and the prompt.
Talk to Your Google Sheets Data Using OpenAI Chat Agent
This workflow transforms a Google Sheet into a live, conversational database. Using an AI agent powered by OpenAI's GPT-4.1-nano model, you can ask natural language questions about your spreadsheet data and receive accurate, context-aware answers — without writing any SQL or formulas. The agent can handle queries like total campaign spend, per-channel breakdowns, month-over-month trends, and cost-per-lead calculations. Workflow Steps Node-by-Node Breakdown Chat with Your Data (Chat Trigger) — This is the entry point of the workflow. It provides a chat interface (webhook) where users type their questions. No authentication is required to trigger the webhook; access can be secured at the workflow level. Memory (Buffer Window Memory) — Stores recent conversation history so the AI can reference previous exchanges. The buffer window keeps the last few messages to maintain context without excessive token use. No authentication required. OpenAI Chat Model (OpenAI GPT-4.1-nano) — The language model that processes user questions and generates answers. Uses API Key auth (you must provide an OpenAI API key). Parameters: model = , no additional options configured. Talk to Your Data (AI Agent) — The core agent that orchestrates the conversation. It receives user input, decides which tool to call (only the Google Sheets tool is available), and returns answers. Uses API Key auth (uses the same OpenAI credential as the model). Parameters include a system message: "Google Sheets Ask-… You are Ask-… Answer questions using Google Sheets ONLY via the tool below. Be precise and conservative. There is only one dataset. Don't ask what dataset it is. Use the data tool to answer the question." Analyze Data (Google Sheets Tool) — The tool the agent calls to read spreadsheet data. Uses OAuth2 authentication (Google Sheets). Parameters: document ID = ("Sample Marketing Data - n8n"), sheet name = "Data" (gid: 365710158). No additional options set. Sticky Notes (Information Only) — Provide setup instructions and tips. Not executable nodes. Setup Instructions Before using this workflow, you need: OpenAI Account — Visit OpenAI API Keys to generate an API key. Make sure you have billing set up at OpenAI Billing and have credits available. Google Account — You need access to a Google Sheet. The sample uses a specific sheet, but you can point it to any sheet with a similar structure: first row = column headers, rows 2–100 = data. To configure: In the OpenAI Chat Model node, create an OpenAI credential with your API key. In the Analyze Data node, create a Google Sheets OAuth2 credential (select your Google account and authorize access). Update the Document ID and Sheet Name to match your own Google Sheet. Optionally update the system message in the Talk to Your Data agent if you want to change the assistant's personality or instructions. Use Cases and Variations This workflow is perfect for: Marketing teams wanting instant answers about campaign performance, spend, and ROI. Sales operations analyzing pipeline data, deal stages, or conversion metrics. Small business owners asking questions about inventory, sales, or customer data without learning SQL. Adaptations: Replace Google Sheets with another data source tool (e.g., Airtable, Notion, PostgreSQL, MySQL) by swapping the "Analyze Data" node. Add more tools to the agent (e.g., a web search tool, a calculator) to expand its capabilities. Change the model to GPT-4o or GPT-3.5-turbo for faster/cheaper responses. Add a Slack or Webhook trigger instead of the chat trigger for a different user interface.
Extract company website metadata via Apify Company Enrichment
This workflow takes a single company domain (e.g., ), validates it, runs it through Apify's Company Enrichment actor, and returns a verified metadata result with provenance. It is designed as a building block for CRM enrichment, lead generation, or data quality pipelines. Workflow Steps Run manually (Manual Trigger) – Starts the workflow on demand. No schedule is set; you can extend it with a cron trigger. Set company domain (Set node) – Hardcodes the domain into a field . Change this to your target domain. Validate domain (Code node, JavaScript) – Validates the domain format (length, allowed characters, no protocol or path). Throws an error if invalid. Also attaches an marker for downstream validation. Extract metadata on Apify (HTTP Request, Header Auth) – Sends a POST request to the Apify actor's sync endpoint with the domain payload. Uses Header Auth with a custom header . Parameters: , to cap cost. Timeout 150 seconds. Validate metadata result (Code node, JavaScript) – Checks the response: only one item, , domain matches, integration source matches, and provenance method is . Rejects any unexpected or empty results. Setup Instructions Get an Apify API token – Sign up or log in at apify.com. Create a token scoped to run actors (). Create an n8n Header Auth credential – In n8n, go to Credentials > New > Header Auth. Set the header name to and value to . Attach this credential to the Extract metadata on Apify node. Replace the default domain – In the Set company domain node, change to your target company domain (e.g., ). Review pricing – The actor charges per run. The workflow caps cost at $0.02 USD per call. Review actor pricing before scaling. Run manually – Click Execute Workflow to test. The output will be a single enriched company object. Use Cases & Adaptations CRM integration – Pipe the output into Salesforce or HubSpot via an HTTP Request or their respective n8n nodes. Bulk enrichment – Replace the manual trigger with a Schedule Trigger or a Spreadsheet File Trigger to process thousands of domains from a Google sheet or CSV. Data validation – Use the validated result to enrich lead lists, verify company websites, or update a database. Custom enrichment – Replace the Apify actor with another REST API (e.g, Clearbit, Zoominfo) by modifying the HTTP Request node and validation logic.