HumationHuman + Automation
Back to Catalog

Export WordPress posts to CSV and upload to Google Drive

Codez & AICodez & AI
1758 views
2/3/2026
AirtableWebhookShopifyCustomer SyncCRM
Official Page

Overview

This n8n workflow automates the process of extracting published WordPress posts, converting them into a CSV file, and uploading it to Google Drive. It’s perfect for content backups, SEO audits, and data migration.

Features

  • Fetches all published posts from a WordPress website
  • Extracts key post details (ID, Title, Link)
  • Converts the extracted data into a CSV file
  • Uploads the CSV file to Google Drive for easy access and storage

Use Cases

  • SEO Optimization: Export post data for keyword analysis and performance tracking
  • Automated Content Backup: Store WordPress post details in Google Drive. You can add more fields to the Csv file if needed

Workflow Steps

1. Trigger Workflow Manually

The workflow starts when triggered manually in n8n.

2. Retrieve WordPress Posts

The workflow fetches all published posts using the WordPress API. It extracts:

  • Post ID
  • Title
  • Link
  • Rendered Content

3. Format Data

The retrieved data is structured to ensure correct CSV formatting.

4. Convert to CSV File

The formatted data is transformed into a downloadable CSV file.

5. Upload to Google Drive

The CSV file is automatically uploaded to a specified Google Drive folder for easy access and storage.

How to Use

  1. Connect your WordPress and Google Drive accounts to n8n.
  2. Run the workflow manually or set up a scheduled trigger.
  3. Access the CSV file from your Google Drive folder.

Export WordPress Posts to CSV and Upload to Google Drive

This n8n workflow automates the process of extracting data from your WordPress site, converting it into a CSV file, and then uploading that CSV file to your Google Drive. It provides a straightforward way to periodically back up or analyze your WordPress post data.

What it does

  1. Manual Trigger: Starts the workflow when manually executed.
  2. WordPress: Retrieves a list of posts from your configured WordPress site.
  3. Edit Fields (Set): This node is present in the workflow but currently has no configured operations. It can be used to transform, filter, or rename fields from the WordPress data before conversion.
  4. Convert to File: Takes the data received from WordPress (and potentially modified by "Edit Fields") and converts it into a CSV file.
  5. Google Drive: Uploads the generated CSV file to your Google Drive account.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • WordPress Account: Access to a WordPress site with an API enabled. You will need to configure a WordPress credential in n8n.
  • Google Drive Account: A Google account with Google Drive enabled. You will need to configure a Google Drive credential in n8n.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • WordPress Node: Click on the "WordPress" node and set up your WordPress API credentials. This typically involves providing your WordPress URL and API key or username/password.
    • Google Drive Node: Click on the "Google Drive" node and set up your Google Drive credentials. This usually involves an OAuth 2.0 authentication flow.
  3. Configure WordPress Node:
    • In the "WordPress" node, ensure the "Resource" is set to "Post" and the "Operation" is set to "Get All". You can adjust other settings like "Limit" or "Filters" if you only want to export specific posts.
  4. Configure Convert to File Node:
    • In the "Convert to File" node, ensure the "File Format" is set to "CSV". You can customize the "File Name" and other CSV options as needed.
  5. Configure Google Drive Node:
    • In the "Google Drive" node, ensure the "Operation" is set to "Upload".
    • Specify the "Folder ID" where you want the CSV file to be uploaded in your Google Drive.
    • You can also adjust the "File Name" if you want to override the name generated by the "Convert to File" node.
  6. Activate the Workflow: Toggle the workflow to "Active" in the top right corner.
  7. Execute Manually: Click "Execute Workflow" to run the workflow and export your WordPress posts. You can also set up a schedule using a "Cron" or "Schedule" trigger if you want this to run automatically at regular intervals.

Related Templates

Auto-create TikTok videos with VEED.io AI avatars, ElevenLabs & GPT-4

💥 Viral TikTok Video Machine: Auto-Create Videos with Your AI Avatar --- 🎯 Who is this for? This workflow is for content creators, marketers, and agencies who want to use Veed.io’s AI avatar technology to produce short, engaging TikTok videos automatically. It’s ideal for creators who want to appear on camera without recording themselves, and for teams managing multiple brands who need to generate videos at scale. --- ⚙️ What problem this workflow solves Manually creating videos for TikTok can take hours — finding trends, writing scripts, recording, and editing. By combining Veed.io, ElevenLabs, and GPT-4, this workflow transforms a simple Telegram input into a ready-to-post TikTok video featuring your AI avatar powered by Veed.io — speaking naturally with your cloned voice. --- 🚀 What this workflow does This automation links Veed.io’s video-generation API with multiple AI tools: Analyzes TikTok trends via Perplexity AI Writes a 10-second viral script using GPT-4 Generates your voiceover via ElevenLabs Uses Veed.io (Fabric 1.0 via FAL.ai) to animate your avatar and sync the lips to the voice Creates an engaging caption + hashtags for TikTok virality Publishes the video automatically via Blotato TikTok API Logs all results to Google Sheets for tracking --- 🧩 Setup Telegram Bot Create your bot via @BotFather Configure it as the trigger for sending your photo and theme Connect Veed.io Create an account on Veed.io Get your FAL.ai API key (Veed Fabric 1.0 model) Use HTTPS image/audio URLs compatible with Veed Fabric Other APIs Add Perplexity, ElevenLabs, and Blotato TikTok keys Connect your Google Sheet for logging results --- 🛠️ How to customize this workflow Change your Avatar: Upload a new image through Telegram, and Veed.io will generate a new talking version automatically. Modify the Script Style: Adjust the GPT prompt for tone (educational, funny, storytelling). Adjust Voice Tone: Tweak ElevenLabs stability and similarity settings. Expand Platforms: Add Instagram, YouTube Shorts, or X (Twitter) posting nodes. Track Performance: Customize your Google Sheet to measure your most successful Veed.io-based videos. --- 🧠 Expected Outcome In just a few seconds after sending your photo and theme, this workflow — powered by Veed.io — creates a fully automated TikTok video featuring your AI avatar with natural lip-sync and voice. The result is a continuous stream of viral short videos, made without cameras, editing, or effort. --- ✅ Import the JSON file in n8n, add your API keys (including Veed.io via FAL.ai), and start generating viral TikTok videos starring your AI avatar today! 🎥 Watch This Tutorial --- 📄 Documentation: Notion Guide Need help customizing? Contact me for consulting and support : Linkedin / Youtube

Dr. FirasBy Dr. Firas
39510

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247