Skip to main content

Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets

Workflow preview

Workflow preview
100%
Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets preview
Open on n8n.io

1. Workflow Overview

How it works 1. User submits a form with a LinkedIn profile URL and number of posts to scrape 2. Apify's LinkedIn Post Scraper actor fetches posts (no cookies required, $1 per 1,000 posts) 3. Posts...

Best for

  • Content Creation automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.formtrigger, @apify/n8n-nodes-apify.apify, n8n-nodes-base.splitinbatches, @n8n/n8n-nodes-langchain.lmchatgroq, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.if, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.googlesheets

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Redowan Ahmed Farhan.

Original n8n.io source

1.1 Workflow description

Title
Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets
Workflow name
Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets

How it works

  1. User submits a form with a LinkedIn profile URL and number of posts to scrape
  2. Apify's LinkedIn Post Scraper actor fetches posts (no cookies required, ~$1 per 1,000 posts)
  3. Posts are looped one at a time for AI processing
  4. Groq AI verifies each post's authenticity and quality
  5. Authentic posts are rewritten by OpenAI in a fresh, engaging style
  6. Results (author, original post, rewritten post) are logged to Google Sheets

Set up steps

  • Estimated time: ~10 minutes
  • Connect Apify via OAuth2 (requires an Apify account)
  • Add your Groq API key in the Groq Chat Model node
  • Add your OpenAI API key in the OpenAI Chat Model node
  • Connect Google Sheets via OAuth2 and select your posts tracker spreadsheet
  • Use responsibly and in accordance with LinkedIn's Terms of Service

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - On form submission

Type / Role
n8n-nodes-base.formTrigger - formTrigger
Config choices
Version 2.5

Block 2 - Run an Actor and get dataset

Type / Role
@apify/n8n-nodes-apify.apify - apify
Config choices
Version 1

Block 3 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 4 - Groq Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatGroq - lmChatGroq
Config choices
Version 1

Block 5 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 6 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 7 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.3

Block 8 - Append row in sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 9 - Rewrite post

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3.1

Block 10 - Main Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Section: Scrape

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Section: Filter

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Section: Rewrite & Log

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Verify The authenticity

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3.1

Block 15 - Simple Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

3. Summary Table

Workflow Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets
Complexity advanced
Nodes 15
Categories Content Creation, AI Summarization
Author Redowan Ahmed Farhan
Published 03 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15453/15453.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Scrape and rewrite LinkedIn AI posts with Apify, Groq, OpenAI and Google Sheets do?

How it works 1. User submits a form with a LinkedIn profile URL and number of posts to scrape 2. Apify's LinkedIn Post Scraper actor fetches posts (no cookies required, $1 per 1,000 posts) 3. Posts...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, AI Summarization use case.