HumationHuman + Automation
Back to Catalog

Create & track LinkedIn posts with Google Sheets, GPT-5.1, Unsplash, and Sona

Sona LabsSona Labs
1334 views
2/3/2026
emailfile managementautomationattachmentsimap
Official Page

Automate LinkedIn content creation by managing ideas in Google Sheets, generating professional AI-written posts, intelligently selecting relevant Unsplash images, sending drafts for email approval, and publishing directly to LinkedIn.

How it works

Step 1: Scheduled Sheet Check

  • Workflow runs daily at midnight (customizable to hourly/weekly)
  • Fetches posts from Google Sheet marked with Status = "Ready"
  • Processes one post per run, updates status to "In Progress"

Step 2: AI Content Generation

  • GPT-5.1 creates engaging LinkedIn post based on your inputs
  • Generates content with proper hashtags, formatting, and tone
  • Follows your specified content type (tip, story, announcement, etc.)

Step 3: Quality Validation

  • Automatically checks character limits (3000 max)
  • Validates minimum hashtag requirements (3+)
  • Loops back to regenerate if quality checks fail

Step 4: Email Approval Workflow

  • Formats post as HTML email with professional styling
  • Sends preview to your Gmail for review
  • Waits for your approval response before proceeding
  • Nothing posts without explicit confirmation

Step 5: Smart Image Handling

  • If you provided image URL: Downloads from Google Drive, Dropbox, or direct links
  • If no URL is provided: Fetch 10 images from Unsplash and use AI to select the best one.
  • If "Include Image?" is "No": Posts text-only content
  • Automatically converts share links to downloadable formats

Step 6: LinkedIn Publishing & Tracking

  • Posts approved content directly to your LinkedIn profile
  • Uses appropriate API endpoint based on whether image is included
  • Updates Google Sheet status to "Posted" for successful posts
  • Marks "Rejected" posts in sheet for review and editing

What you'll get

  • Batch content planning: Queue multiple posts in advance via Google Sheets
  • Consistent posting schedule: Automated daily publishing without manual work
  • Professional AI content: GPT-5.1 generates engaging, platform-optimized posts
  • Full approval control: Review every post before it goes live
  • Flexible image options: Your images, AI-generated, or text-only
  • Quality assurance: Built-in checks prevent poorly formatted posts
  • Status tracking: Monitor what's ready, in progress, rejected, or posted
  • Smart link conversion: Automatically handles Google Drive and Dropbox share links

Requirements

Accounts & credentials:

  • OpenAI API key (requires paid plan for GPT-5.1)
  • Gmail account (for approval workflow)
  • Google account (for Sheets integration)
  • LinkedIn account (for publishing)
  • Unsplash API key (for getting images)

Google Sheet setup: Create a sheet with these columns:

  • Topic/Subject (required) - Main idea for the post
  • Content Type (required) - e.g., "Tip", "Story", "Announcement"
  • Tone (required) - e.g., "Professional", "Casual", "Inspirational"
  • Target Audience (optional) - Who you're writing for
  • Additional Notes (optional) - Specific points to include
  • Image link for your post (optional) - URL to your image
  • Include Image? (required) - "Yes" or "No"
  • Status (required) - "Ready" to trigger workflow

Setup steps

  1. Import workflow - Click "Use workflow" to add to your n8n instance

  2. Connect credentials:

    • Google Sheets: Authenticate and select your sheet from dropdown
    • OpenAI: Add your API key in both AI nodes
    • Gmail: Authenticate and update recipient email in approval node
    • LinkedIn: Authenticate (your profile auto-populates)

  3. Create your content sheet - Add the required columns and fill with post ideas

  4. Test the workflow:

    • Add one test row with Status = "Ready"
    • Run workflow manually
    • Check email for approval
    • Verify post appears on LinkedIn

  5. Configure schedule - Default is daily at midnight; adjust Schedule Trigger node for different frequency

  6. Start batching - Add multiple ideas to your sheet and let automation handle the rest

Tips for best results

  • Be specific in Topic/Subject: "5 ways to improve team productivity" beats "productivity tips"
  • Mix content types and tones to keep your feed engaging
  • Use Additional Notes for data points, statistics, or specific examples. You can also include links that the AI can use for the posts.
  • Start with text-only posts to validate content quality before adding images
  • Review rejected posts carefully and refine your inputs
  • Batch 10-20 ideas at once for weeks of automated content

n8n Workflow: Create and Track LinkedIn Posts with Google Sheets and AI

This n8n workflow automates the process of generating, approving, and publishing LinkedIn posts, then tracking them in a Google Sheet. It leverages AI to create post content and allows for human-in-the-loop approval via email before publishing.

What it does

This workflow streamlines your LinkedIn content creation and management by:

  1. Scheduling: Runs on a defined schedule (e.g., daily, weekly) to check for new post ideas.
  2. Generating Content: Uses an AI Agent (powered by an OpenAI Chat Model) to generate LinkedIn post content based on an unspecified input (likely from a Google Sheet or internal prompt).
  3. Structuring Output: Parses the AI-generated content into a structured format.
  4. Human Approval: Sends an email via Gmail for human review and approval of the generated post content.
  5. Conditional Publishing: If the post is approved, it proceeds to publish.
  6. Publishing to LinkedIn: Publishes the approved content as a new post on LinkedIn.
  7. Tracking: Adds or updates a record in a Google Sheet to track the published post.
  8. Limiting Output: Limits the number of items processed, likely to control the volume of posts or approvals.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Configured credentials for Google Sheets.
  • OpenAI API Key: Configured credentials for OpenAI (used by the AI Agent).
  • Gmail Account: Configured credentials for Gmail to send approval emails.
  • LinkedIn Account: Configured credentials for LinkedIn to publish posts.

Setup/Usage

  1. Import the Workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your OpenAI credentials for the "OpenAI Chat Model" node.
    • Set up your Gmail credentials for the "Gmail" node.
    • Set up your LinkedIn credentials for the "LinkedIn" node.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency (e.g., daily, weekly).
    • AI Agent / OpenAI Chat Model: Review and potentially modify the AI agent's prompt or model settings to guide content generation.
    • Gmail: Configure the recipient email address(es) for post approval.
    • Google Sheets: Specify the spreadsheet ID, sheet name, and column mappings for tracking posts.
    • LinkedIn: Configure the post content mapping to use the AI-generated and approved content.
    • Code: Review the JavaScript code for any custom logic.
    • If: Adjust the conditions for post approval if needed.
    • Limit: Adjust the limit if you need to process more or fewer items.
  4. Activate the Workflow: Once configured, activate the workflow to start automating your LinkedIn posts.

Related Templates

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

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31