HumationHuman + Automation
Back to Catalog

Create LinkedIn content with Perplexity research, GPT-4 & Google Sheets

Guilherme CamposGuilherme Campos
775 views
2/3/2026
google-aiemailautomationgoogle-driveattachments
Official Page

This n8n workflow automates the process of creating high-quality, scroll-stopping LinkedIn posts based on live research, AI insight generation, and Google Sheets storage.

Instead of relying on recycled AI tips or boring summaries, this system combines real-time trend discovery via Perplexity, structured idea shaping with GPT-4, and content generation tailored to a bold, human LinkedIn voice. The workflow saves each post idea (with image prompt, tone, and summary) to a Google Sheet, sends you a Telegram alert, and even formats your content for direct publishing.

Perfect for solopreneurs, startup marketers, or anyone who posts regularly on LinkedIn and wants to sound original, not robotic.

Who’s it for

  • Content creators and solopreneurs building an audience on LinkedIn
  • Startup teams, PMs, and tech marketers looking to scale thought leadership
  • Anyone tired of generic AI-generated posts and craving structured, edgy output

How it works

  • Daily trigger at 6 AM starts the workflow.
  • Pulls recent post history from Google Sheets to avoid repeated ideas.
  • Perplexity AI scans the web
  • Generates 3 structured post ideas (including tone, hook, visual prompt, and summary).
  • GPT-4 refines each into a bold, human-style LinkedIn post, following detailed brand voice rules.
  • Saves everything to Google Sheets (idea, content, image prompt, post status).
  • Sends a Telegram notification to alert you new ideas are ready.

How to set up

  • Connect your Perplexity, OpenAI, Google Sheets, and Telegram credentials.
  • Point to your preferred Google Sheet and sheet tab for storing post data.
  • Adjust the schedule trigger if you want more or fewer ideas per week.
  • (Optional) Tweak the content style prompt to match your personal tone or niche.

Requirements

  • Perplexity API account
  • OpenAI API access (GPT-4 or GPT-4-mini)
  • Telegram bot connected to your account
  • Google Sheets document with appropriate column headers

How to customize the workflow

  • Change the research sources or prompt tone (e.g., more tactical, more spicy, more philosophical)
  • Add an image generation tool to turn prompts into visuals for each post
  • Filter or tag ideas based on type (trend, tip, story, etc.)
  • Post automatically via LinkedIn API or Buffer integration

Create LinkedIn Content with Perplexity Research & GPT-4

This n8n workflow automates the process of generating engaging LinkedIn content based on research from Perplexity AI and refining it with a GPT-4 powered OpenAI Chat Model. It then allows for review and approval via Telegram before posting to Google Sheets.

What it does

This workflow streamlines content creation by:

  1. Scheduling Content Generation: Triggers at a set interval (e.g., daily, weekly) to initiate the content creation process.
  2. Fetching Research from Perplexity AI: Uses Perplexity AI to gather information based on a predefined prompt.
  3. Generating LinkedIn Post Drafts with GPT-4: Processes the Perplexity AI research using an OpenAI Chat Model (GPT-4) to create a structured LinkedIn post draft.
  4. Parsing Structured Output: Extracts the structured content (e.g., title, body, hashtags) from the GPT-4 output.
  5. Human-in-the-Loop Approval via Telegram: Sends the generated content to a Telegram chat for review and approval.
  6. Storing Approved Content in Google Sheets: Once approved, the content is saved to a Google Sheet, ready for manual posting or further automation.
  7. Limiting Output (Optional): Includes a "Limit" node, which suggests the ability to control the number of items processed, perhaps to prevent overwhelming the Telegram approval step or Google Sheet.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Perplexity AI Account & API Key: For fetching research.
  • OpenAI Account & API Key: For using the GPT-4 chat model.
  • Telegram Bot Token & Chat ID: For sending approval messages.
  • Google Account: With access to Google Sheets for storing content.
  • Google Sheets Credential: Configured in n8n to access your desired spreadsheet.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Perplexity AI credential with your API key.
    • Set up your OpenAI credential with your API key.
    • Set up your Telegram credential with your bot token. You will also need to specify the Chat ID in the Telegram node where approval messages should be sent.
    • Set up your Google Sheets credential.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency for content generation.
    • Perplexity: Update the "Query" field with the type of research you want Perplexity to perform for your LinkedIn content.
    • OpenAI Chat Model: Fine-tune the prompt to guide GPT-4 in generating LinkedIn-specific content (e.g., tone, length, inclusion of hashtags).
    • Structured Output Parser: Ensure the schema matches the expected output structure from your OpenAI prompt.
    • Telegram: Customize the message sent for approval.
    • Google Sheets: Specify the Spreadsheet Name, Sheet Name, and the columns where the content should be written.
    • Code Node: Review and adjust the JavaScript code if you need to transform or format the data in a specific way before sending it to Telegram or Google Sheets.
    • Limit Node: If active, configure the limit to control the number of items processed in a single run.
  4. Activate the Workflow: Once configured, activate the workflow to start automating your LinkedIn content creation.

This workflow provides a powerful foundation for generating and managing LinkedIn content with AI, incorporating a crucial human review step to maintain quality and relevance.

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